From: Stefan v. d. W. <st...@su...> - 2005-04-13 21:14:12
|
Attached is a much simpler patch that should resolve the situation, irrespective of any shuffling done by distros. I think it is safe to assume that pcre.h is present if pcre-config is? Otherwise we can explicitly check, using the output from `pcre-config --cflags` Regards Stefan On Wed, Apr 13, 2005 at 10:52:06PM +0200, Stefan van der Walt wrote: > On Wed, Apr 13, 2005 at 08:33:22AM -0600, Dmitri A. Sergatskov wrote: > > On 4/13/05, Stefan van der Walt <st...@su...> wrote: > > > How about the following patch, as well as renaming pcregexp.cc to > > > pcregexp.cc.in and doing a variable substitution: > > > > > ... > > > > At this moment I am not even sure that this is not a bug with the pcre-devel > > package. Perhaps, they should have made a symlink > > pcre.h -> pcre/pcre.h ? > > I think that Debian (and some other distros) modify the path to > pcre.h. I notice now that there is a `pcre-config' available. Maybe > we should rather use that to determine compiler flags. > > Regards > Stefan > > > ------------------------------------------------------- > SF email is sponsored by - The IT Product Guide > Read honest & candid reviews on hundreds of IT Products from real users. > Discover which products truly live up to the hype. Start reading now. > http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click > _______________________________________________ > Octave-dev mailing list > Oct...@li... > https://lists.sourceforge.net/lists/listinfo/octave-dev |