hi martin, > > <output.gz> > > > checking whether we are using the GNU C Library 2.1 or newer... yes > > This is suspicious: I always get "no" there. Do you have a file > "features.h" lying around in /usr/local/include, /sw/include, or > /usr/include, that defines __GLIBC__?
yes indeed. i've got features.h in /usr/include and it has: #define __GLIBC__ 2 i've imported it (along with values.h, gnu/lib-names.h gnu/libc-version.h and gnu/stubs.h) a while ago because they seemed to be needed to install the graphics library pgplot. i've renamed features.h for the moment to check if this was the problem and indeed it now compiles without any problem. is there any other cleaner fix than renaming the file during the install? is there any other potential problem in having this 'features.h' lying in /usr/include?? thanks for your help! cheers jeanfrancois ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ Fink-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-users
