On Tue, Nov 25, 2003 at 09:14:10PM -0700, M. Warner Losh wrote:
We recommend
make buildworld
make buildkernel
make installkernel
reboot -s - single user
make installworld
make buildkernel ; make installkernel can be shortened to just
make kernel.
On Tue, Nov 25, 2003 at 08:57:10AM -0800 I heard the voice of
Kevin Oberman, and lo! it spake thus:
While UPDATING contain details on updating a system, the Makefile in
/usr/src (actually Makefile.inc1) contains a target of 'world' and,
through V3 of FreeBSD, this was considered the
On (2003/11/24 15:39), Kevin Oberman wrote:
I end up with the following when I run `make world` on 5.1-RELEASE-p10.
Did you read UPDATING?
I fear a bikeshed, but I really think it may be past time to remove
the 'world' target from /usr/src/Makefile.inc1. It is rarely useful
and
* Kevin Oberman [EMAIL PROTECTED] [20031125 02:39]: wrote:
Date: Sat, 22 Nov 2003 06:07:03 -0800
From: Kris Kennaway [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
--nVMJ2NtxeReIH9PS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sat, Nov 22, 2003 at
Date: Tue, 25 Nov 2003 17:47:29 +0300
From: Odhiambo Washington [EMAIL PROTECTED]
--+g7M9IMkV8truYOl
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* Kevin Oberman [EMAIL PROTECTED] [20031125 02:39]: wrote:
Date:
On Tue, 25 Nov 2003 08:57:10 -0800
Kevin Oberman [EMAIL PROTECTED] wrote:
Now we are moving on to V5 and 'world' is growing increasingly dangerous
to use. Because changes are applied that will allow smooth upgrades
when the kernel is built after the new system is built, but before it is
Kevin Oberman wrote:
...Because changes are applied that will allow smooth upgrades
when the kernel is built after the new system is built, but before it is
installed, make world is increasingly unlikely to work...
The recent statfs changes demonstrated why the 'makeworld' 'makekernel'
sequence
On Tue, Nov 25, 2003 at 03:35:54PM -0800, walt wrote:
Kevin Oberman wrote:
...Because changes are applied that will allow smooth upgrades
when the kernel is built after the new system is built, but before it is
installed, make world is increasingly unlikely to work...
The recent statfs
Brooks Davis answered:
walt asked:
What does 'buildworld' give us that the new kernel might need?
The correct toolchain including the compiler and config(8).
Okay, thanks, that helps.
Just thinking out loud about worst-case examples for people who
do routinely use 'make world' (like I have for
In message: [EMAIL PROTECTED]
walt [EMAIL PROTECTED] writes:
: ...Because changes are applied that will allow smooth upgrades
: when the kernel is built after the new system is built, but before it is
: installed, make world is increasingly unlikely to work...
:
: The recent statfs
On Tue, Nov 25, 2003 at 06:51:15PM -0800, walt wrote:
Brooks Davis answered:
walt asked:
What does 'buildworld' give us that the new kernel might need?
The correct toolchain including the compiler and config(8).
Okay, thanks, that helps.
Just thinking out loud about worst-case
Date: Sat, 22 Nov 2003 06:07:03 -0800
From: Kris Kennaway [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
--nVMJ2NtxeReIH9PS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sat, Nov 22, 2003 at 03:16:06PM +0300, Odhiambo Washington wrote:
I end up with the
On Sat, Nov 22, 2003 at 03:16:06PM +0300, Odhiambo Washington wrote:
I end up with the following when I run `make world` on 5.1-RELEASE-p10.
Did you read UPDATING?
Kris
pgp0.pgp
Description: PGP signature
On Sat, Nov 22, 2003 at 03:16:06PM +0300, Odhiambo Washington wrote:
I end up with the following when I run `make world` on 5.1-RELEASE-p10.
Did you read UPDATING?
Kris
pgp0.pgp
Description: PGP signature
/usr/src/contrib/libstdc++/libsupc++/unwind-cxx.h:41:20: unwind.h: No such=
file or directory
mkdep: compile failed
*** Error code 1
=20
Stop in /usr/src/gnu/lib/libstdc++.
*** Error code 1
I'm running 5.1-CURRENT now, but I was able to build 5.1-RELEASE-p10. I
suspect you need to
15 matches
Mail list logo