Randy McMurchy wrote: > Anyway, there is an include of glob.h that crashes that > build on my platform. > > I can modify the /usr/include/glob.h and have the package build okay, > but that is certainly not an avenue we can pursue.
I assume that by 'we' you mean BLFS. If the issue is fixed in current libc CVS, then it was fixed for a reason and should probably be backported to 2.3.5 in LFS. This same issue will affect mplayer as well as mentioned on blfs-support in the yet unanswered thread titled "undefined reference to `rk_globfree'/`rk_glob'". Would it be as simple as creating a local glob.h for glob/globfree? That said, I've not seen the issue yet, or even glob.h yet. > I have built a > patch that excludes building these non-needed programs if we need to > put this in the current BLFS SVN book. Yes, thank you for that. I'll be needing it in about 2 hours. > > Understand, this issue will not manifest itself if you are using > Glibc prior to 2.3.5 or a recent snapshot. As best as I can tell only > the 2.3.5 version of Glibc has put in defines for rk_glob and > rk_globfree that seem to be causing the trouble. So what changed and then changed back? :-) I browsed through libc-alpha with no good on finding anything on the problem. Do you by chance have a link to a discussion or a patch that put this back the way it was for current cvs? Maybe seeing the developers' reasons for the change will shed a bit of light on how (B)LFS should handle it. Actually, is it even the same before and after glibc-2.3.5? I'm probably jumping the gun a bit, but rather be proactive as opposed to patching up each package that we run across. -- DJ Lucas -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
