On Sat, Jul 28, 2007 at 01:07:56PM -0400, Joe Ciccone wrote: > Well, I managed to recreate this and I almost have this figured out... > Sort of. I went through all the dependencies of the commands that were > seg faulting and found that bash was the offending package. If bash was > compiled natively Glibc would work, but cross-compiled the make would > seg fault. Looked into the config.cache differences for a native and a > cross-compiled build. Here were the differences worth looking at. > (Original file was the broken version). [...] > > So, I put this in config.cache and now it works. > > ac_cv_func_mmap_fixed_mapped=yes > ac_cv_func_strcoll_works=yes > ac_cv_func_working_mktime=yes > bash_cv_func_sigsetjmp=present > bash_cv_getcwd_malloc=yes > bash_cv_job_control_missing=present > bash_cv_printf_a_format=yes > bash_cv_sys_named_pipes=present > bash_cv_ulimit_maxfds=yes > bash_cv_under_sys_siglist=yes > bash_cv_unusable_rtsigs=no > gt_cv_int_divbyzero_sigfpe=yes > > I'd still like to find out which one of those is the offending entry. > But for now, it's atleast narrowed down quite a bit. > Wow, thanks for that insight, Joe. Unfortunately, it will probably be some time before I can get back to the pure64 build.
ĸen -- das eine Mal als Tragödie, das andere Mal als Farce _______________________________________________ Clfs-dev mailing list [email protected] http://lists.cross-lfs.org/cgi-bin/mailman/listinfo/clfs-dev
