Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!spool.mu.edu!howland.reston.ans.net!gatech!concert!sas!mozart.unx.sas.com!torpid.unx.sas.com!sastdr
From: sastdr@torpid.unx.sas.com (Thomas David Rivers)
Subject: Re: Building profiled libc library gets SIGSEGV?
Sender: news@unx.sas.com (Noter of Newsworthy Events)
Message-ID: <C5J4I6.4no@unx.sas.com>
Date: Thu, 15 Apr 1993 14:34:53 GMT
References: <C5FHqr.L8t@unx.sas.com> <9304150227.ac08704@gate.demon.co.uk> <C5I7Iq.9F4@kithrup.com>
Nntp-Posting-Host: torpid.unx.sas.com
Organization: SAS Institute Inc.
Lines: 26
In article <C5I7Iq.9F4@kithrup.com> sef@kithrup.com (Sean Eric Fagan) writes:
>In article <9304150227.ac08704@gate.demon.co.uk> damian@centrix.demon.co.uk (damian) writes:
>>In article <C5FHqr.L8t@unx.sas.com> sastdr@torpid.unx.sas.com (Thomas David Rivers) writes:
>>>I noticed that the build got a signal 11 while building the profiled
>>>C library (libc_p.a).
>>You are not alone :-)
>
>Uninstall bash as /bin/sh. Or fix bash, your choice. Hopefully, patches
>for /bin/sh will be available soon.
>
Yes, that's the trick....
Bash has a bug when is tickled when the command line is greater than
5K; which it is when building libc_p.a.
Simply returning (if only temporarily) to ash lets the build complete
with no problems.
- Thanks -
- Dave Rivers -
(sastdr@unx.sas.com (Work))
(rivers@ponds.uucp (Home))
--
UPDATE ALL INFORMATION AND POD INTO COSMOS - Federal Express