Error question

2013-03-14 Thread Charlie Jones
I am trying to upgrade to 9.1-RELEASE uname -a FreeBSD havoc.innerlightcorp.com 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #0: Mon May 30 12:58:18 MDT 2011 r...@havoc.innerlightcorp.com:/usr/obj/usr/src/sys/CUSTOM amd64 I received these messages at the end of the make buildworld process. Is it

Re: Error question

2013-03-14 Thread Daniel Nebdal
How does your make.conf and src.conf look? On Thu, Mar 14, 2013 at 3:49 PM, Charlie Jones cjo...@innerlightcorp.com wrote: I am trying to upgrade to 9.1-RELEASE uname -a FreeBSD havoc.innerlightcorp.com 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #0: Mon May 30 12:58:18 MDT 2011

Re: libc error question answered (partly)

2002-09-22 Thread Tim Robbins
On Sat, Sep 21, 2002 at 08:21:15PM -0700, walt wrote: walt wrote: My guess is that the syntax of 'sort' has changed since lorder was modified in March of 2001(?) David Wolfskill just pointed out to me that the behavior of 'sort' is completely different in -STABLE, which I've just

Re: libc error question answered (partly)

2002-09-22 Thread walt
Tim Robbins wrote: On Sat, Sep 21, 2002 at 08:21:15PM -0700, walt wrote: walt wrote: My guess is that the syntax of 'sort' has changed since lorder was modified in March of 2001(?) David Wolfskill just pointed out to me that the behavior of 'sort' is completely different in -STABLE, which

libc error question answered (partly)

2002-09-21 Thread walt
The source of the sort: open failed: +1: No such file or directory message during compilation of libc is the shellscript /usr/bin/lorder. /usr/bin/lorder contains these lines: # sort symbols and references on the first field (the symbol) sort +1 $R -o $R sort +1 $S -o $S My guess is that the

Re: libc error question answered (partly)

2002-09-21 Thread walt
walt wrote: My guess is that the syntax of 'sort' has changed since lorder was modified in March of 2001(?) David Wolfskill just pointed out to me that the behavior of 'sort' is completely different in -STABLE, which I've just confirmed. Does anyone else see this behavior in -CURRENT? What