[Hackage] #262: Check for required C libraries during configure

[Hackage]

#262: Check for required C libraries during configure
----------------------------+-----------------------------------------------
  Reporter:  guest          |        Owner:                     
      Type:  enhancement    |       Status:  new                
  Priority:  high           |    Milestone:  Cabal-1.6          
 Component:  Cabal library  |      Version:  1.2.3.0            
  Severity:  normal         |   Resolution:                     
  Keywords:                 |   Difficulty:  very easy (<1 hour)
Ghcversion:  6.8.2          |     Platform:                     
----------------------------+-----------------------------------------------
Changes (by duncan):

  * difficulty:  easy (<4 hours) => very easy (<1 hour)

Comment:

 Thanks! Works great.

 For example:
 {{{
 $ setup configure -O0
 Configuring foo-1.0...
 Warning: Required C header not found: foo.h
 Warning: Required C library not found: bar
 Warning: Required C library not found: baz
 }}}

 And adding `--extra-include-dirs=./test/ --extra-lib-dirs=./test/` makes
 it work fine (with the test headers and lib files in `./test/` obviously).

 {{{
 Mon Jan 26 18:58:32 GMT 2009  gleb.alexeev at gmail.com
   * Warn if C dependencies not found (kind of fixes #262)

   This is just a basic check - generate a sample program and check if it
 compiles and links with relevant flags. Error messages (warning messages,
   actually) could use some improvement.

 Fri Jan 30 12:02:28 GMT 2009  Gleb Alexeyev <gleb.alexeev at gmail.com>
   * #262 iterative tests for foreign dependencies
   Optimize for succesful case. First try all libs and includes in one
 command,
   proceed with further tests only if the first test fails. The same goes
 for lib
 s
   and headers: look for an offending one only when overall test fails.
 }}}

 The last thing I need to fix before we can make these errors rather than
 just warnings is doing the check in the right place for packages that use
 configure scripts. We can also make some improvements to the error
 messages but it's already a lot more informative than it used to be when
 it'd just fail half way through building.

-- 
Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/262#comment:13>
Hackage <http://haskell.org/cabal/>
Hackage: Cabal and related projects