Dan Nicholson wrote:
On 1/24/06, Justin <[EMAIL PROTECTED]> wrote:
  
After searching the internet and some helpful advice on here I
was told -D_GNU_SOURCE should fix the problem but only if it was
included in the flags when perl was built.
    

Why does it have to be included in the flags when perl was built?  It
would seem to me that adding -D_GNU_SOURCE to CPPFLAGS or similar for
rpm would do the trick.  Not that I'm doubting you, but this is
important if that's the case.

--
Dan
  
I used this as a reference http://www.swig.org/Doc1.3/Perl5.html#Perl5_nn9 but I may not have explained it correctly. When building perl it asks several questions, and one of these is which perl cflags to use when gcc or whatever compiler (the example uses g++) is called to compile a perl wrapper. This is what i needed to enter, as when I simply added -D_GNU_SOURCE as a CFLAG in rpm it got completely ignored (did not get used in the command) when the line for the perl sections got compiled. When I added it into the perl cflags and re-compiled perl the -D_GNU_SOURCE appeared in the gcc line and the program compiled successfully.
The rpm configure had obviously read the perl cflags and only used them when it was working on sections that would deal with perl, therefore when it needed to compile these parts the normal cflags where removed and the perl cflags inserted.

I expect the perl cflags could have been edited a different way to add -D_GNU_SOURCE but I wanted to ensure there were no little problems which would be harder to identify at a later date.

If you need any tests running or info sending to help with this I would be more than happy to fo this. Excellent work with both the blfs and clfs books btw ;)

Thanks again

Justin
-- 
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to