Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 11 Jan 1996 09:37:37 +0100 (MET)
From:      J Wunsch <j@uriah.heep.sax.de>
To:        freebsd-current@FreeBSD.org (FreeBSD-current users)
Subject:   Re: make world
Message-ID:  <199601110837.JAA10671@uriah.heep.sax.de>
In-Reply-To: <199601110236.SAA01847@austin.polstra.com> from "John Polstra" at Jan 10, 96 06:36:22 pm

next in thread | previous in thread | raw e-mail | index | archive | help
As John Polstra wrote:
> 
> J"org wrote:
> 
> > This seems to be the same problem i'm experiencing when trying to
> > ``make release'', except i'm only getting it in the chroot'ed tree,
> > with the make binary running from there.  At least for me, it's `make'

> To me, this looks very much like something that might happen if you had
> just trashed your dynamic linker.  Hey!  What do you know?!  He had _just_
> installed a new dynamic linker.  What a coincidence!

Hmm, so this seems to explain one problem.  But now, my problem looks
different:

As part of ``make release'', the world is being rebuilt:

...
--------------------------------------------------------------
 Rebuilding /usr/lib
--------------------------------------------------------------

...
===> csu/i386
cc -O -pipe -DLIBC_SCCS -fno-omit-frame-pointer   -c -DCRT0 -DDYNAMIC /usr/src/lib/csu/i386/crt0.c -o crt0.o
ld -x -r crt0.o
mv a.out crt0.o
...
===> libc
creating accept.o
creating access.o
creating acct.o
creating adjtime.o
creating bind.o
...

Everything works fine, but suddenly (and at least two or three times
i've seen it happen, it's always been when building libc):

-I/usr/src/lib/libc/locale -DYP -c /usr/src/lib/libc/db/btree/bt_put.c -o bt_put.po
cc -p -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE 
-I/usr/src/lib/libc/locale -DYP -c /usr/src/lib/libc/db/btree/bt_search.c -o bt_search.po
Memory fault - core dumped
===> csu/i386
...

The parent `make' doesn't even seem to notice that its child died, it
doesn't announce any sort of an error for it.  It continues with the
next directory as if nothing happened, and the problem only becomes
very apparent when it's time to install the newly-built libs later.

ld.so hasn't been rebuilt yet at this stage.

-- 
cheers, J"org

joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601110837.JAA10671>