On Sat, Jul 28, 2007 at 06:45:56PM +0100, Ken Moffat wrote:
> On Sat, Jul 28, 2007 at 01:07:56PM -0400, Joe Ciccone wrote:
> [...]
> > 
> > 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.
> 
 Just for the record, I'm on a multilib x86_64 build (from
clfs-1.0.0).  Again, I build coreutils for 'df' at the start of the
test tools, and again it crapped out (on an 'echo' to create a
header).  Rebuilding bash with all of the above fixed it.

ĸ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

Reply via email to