Re: AC_CHECK_HEADER question

[Jan van Dijk]

On Monday 18 Mar 2013 00:39:34 Peter Johansson wrote:
> Hi Jan,
> 
> On 03/18/2013 07:35 AM, Jan van Dijk wrote:
> >   It will also make the scripts less
> > 
> > robust.
> > 
> > Am I overlooking something? Is there a technical reason why that
> > information cannot be.communicated to the user?
> 
> It is not known where the header file is. The configure script tests if
> code which contains "#include <header.h>" compiles. If it compiles it
> proves that 'header.h' exist but not *where*.
> 
> 
> I have a similar situation in one my projects in which we use a header
> file "bam.h" which is either installed in '<prefix>/include/', in
> '<prefix>/include/bam/' or in '<prefix>/include/samtools'. We solve it
> by having
> 

Dear Peter,

Thank you for your comments and suggestions. The problem is that the header is 
included indirectly (by a third-party header) not by ourselves. So 
unfortunately, this patterns does not work (without changing that third-party 
code)

With kind regards,

Jan van Dijk