On Wed, 28 Jun 2000 19:54:17 -0400, Donn Miller wrote:
Again, this is after re-making buildworld with -DNOCLEAN after a
successful first make buildworld.
Any chance the sources changed between buildworlds?
Ciao,
Sheldon.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
On Wed, Jun 28, 2000 at 07:54:17PM -0400, Donn Miller wrote:
make: don't know how to make
/usr/obj/usr/src/i386/usr/include/sys/types.h. Stop
*** Error code 2
This is what I got when I tried to ``make -DNOCLEAN buildworld'' after
the Perl 5.006 upgrade. Perl is being built at the wrong time,
On Wed, Jun 28, 2000 at 07:54:17PM -0400, Donn Miller wrote:
make: don't know how to make
/usr/obj/usr/src/i386/usr/include/sys/types.h. Stop
*** Error code 2
This is what I got when I tried to ``make -DNOCLEAN buildworld'' after
the Perl 5.006 upgrade. Perl is being built at the
Hi
I just committed a fix for this.
M
Recently, the make world problems with perl have been fixed, and I can do
a make world all the way through, provided I do a make world the first
time only. However, I did a cvsup to update my source tree again after
the first make world. I did a make
Recently, the make world problems with perl have been fixed, and I can do
a make world all the way through, provided I do a make world the first
time only. However, I did a cvsup to update my source tree again after
the first make world. I did a make -DNOCLEAN buildworld with /usr/obj
On Fri, 29 Oct 1999 08:46:29 -0400, "Chris D. Faulhaber" wrote:
As an interim hack, would the following patch, which verifies
kern.osreldate = 400011, suffice?
I'd be in favour of this if all the changes were associated with
comments containing ``XXX required for sigset_t migration''.
On Thu, 28 Oct 1999, Marcel Moolenaar wrote:
Peter Jeremy wrote:
(/me wonders how many MORE times we are going to have to say this because
of the signal changes...)
A very large number I suspect.
IMHO, the correct solution is to for the entire make world process to
be
"Chris D. Faulhaber" wrote:
On Thu, 28 Oct 1999, Marcel Moolenaar wrote:
Peter Jeremy wrote:
IMHO, the correct solution is to for the entire make world process to
be re-worked.
That's what I'm currently doing. If I have a stripped down make process
ready for public viewing,
Peter Jeremy wrote:
(/me wonders how many MORE times we are going to have to say this because
of the signal changes...)
A very large number I suspect.
IMHO, the correct solution is to for the entire make world process to
be re-worked.
That's what I'm currently doing. If I have a
As Peter Jeremy wrote ...
On 1999-Oct-28 07:36:53 +1000, David O'Brien wrote:
IF you are going to run -CURRENT, you need to read this list.
And read /usr/src/UPDATING which also warns about this
(/me wonders how many MORE times we are going to have to say this because
of the signal
From today's cvsup:
cd /usr/src ; make clean ; make buildworld
[snip]
rm -f .depend /usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GPATH
/usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GRTAGS
/usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GSYMS
/usr/obj/shared1/FreeBSD/src/gnu/lib/libgcc/GTAGS
echo
by Telenor Internet
more? http://www.ripe.net/cgi-bin/whois?tu36-ripe
-Original Message-
From: Mike Pritchard [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 27, 1999 10:00 PM
To: Tomas TPS Ulej
Subject: Re: make buildworld problem...
How old is your kernel? This looks like what you
/shared1/FreeBSD/src/gnu/lib/libgcc/../../../contrib/egcs/gcc/libgcc1.c
*** Signal 12
Stop in /shared1/FreeBSD/src/gnu/lib/libgcc.
*** Error code 1
RTFML (Read The FINE Mailing List)!! This has come up for the past many
weeks. You need to build a kernel BEFORE your ``make world''.
IF you
cc -c -O -pipe
^ -- try getting rid of this and see what happens.
Good Luck,
Jerry Hicks
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
14 matches
Mail list logo
