Re: Release Compiler options
Am Dienstag, 5. Oktober 2004 03:52 schrieb Haulmark, Chris: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emanuel Strobl Sent: Monday, October 04, 2004 8:43 PM To: [EMAIL PROTECTED] Subject: Release Compiler options I really spent some time tracing the make release, but couldn't find any way to modify the compiler flags for the release. Why do I need a populated /usr/obj if it's never touched? I really think I'm missing something. Two years ago I had no problems building specail 4.4-RELEASEs. Any hint is welcome. There is an excellent hint for compiler flags to be found in the 19.4.3 section of the FreeBSD handbook. Hm, this is for the world and is very well known and documented. I'm talking about /usr/src/release/Makefile The /usr/obj directory composes of the compiled applications from the buildworld function. You can delete it after you did a successful completion of the installworld on a system. That's what happens when you do make clean in the /usr/src directory. Again, I'm not talking about make installworld, but 'make release' -Mano -Mano -- Chris Haulmark System Admin. Freelancer In market for IT corrections for a salary. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] pgpWQJkjHlmPT.pgp Description: PGP signature
Re: Release Compiler options
On Tue, Oct 05, 2004 at 10:45:09AM +0200, Emanuel Strobl wrote:
Am Dienstag, 5. Oktober 2004 03:52 schrieb Haulmark, Chris:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Emanuel Strobl
Sent: Monday, October 04, 2004 8:43 PM
To: [EMAIL PROTECTED]
Subject: Release Compiler options
I really spent some time tracing the make release, but
couldn't find any way
to modify the compiler flags for the release. Why do I need a
populated /usr/obj if it's never touched? I really think I'm missing
something. Two years ago I had no problems building specail
4.4-RELEASEs.
Any hint is welcome.
There is an excellent hint for compiler flags to be found in the
19.4.3 section of the FreeBSD handbook.
Hm, this is for the world and is very well known and documented.
I'm talking about /usr/src/release/Makefile
The /usr/obj directory composes of the compiled applications from
the buildworld function. You can delete it after you did a successful
completion of the installworld on a system. That's what happens
when you do make clean in the /usr/src directory.
Again, I'm not talking about make installworld, but 'make release'
If you're using 'make release' you're expected to a) have your own
local copy of the FreeBSD src CVS repository and b) know how to use
cvs(1) and make(1). 'make release' is aimed at expert users;
beginners would be well advised to steer clear of it.
What you do is edit the /usr/src/release/Makefile, specifically the
CHROOTDIR, BUILDNAME and CVSROOT it tells you to set. Or specify them
on the command line if you prefer.
Then you setup the ${LOCAL_PATCHES} variable to point to a file of
patches to apply to the checked out chroot'ed source tree (hint: try
applying a patch to ${CHROOTDIR}/etc/make.conf to fiddle with the make
flags). Similarly you can run a shell script ${LOCAL_SCRIPT} to do
whatever you want to the chroot'ed sources before building.
Cheers,
Matthew
--
Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks
Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey Marlow
Tel: +44 1628 476614 Bucks., SL7 1TH UK
pgpOeeTLWfQMg.pgp
Description: PGP signature
Re: Release Compiler options
Am Dienstag, 5. Oktober 2004 12:00 schrieb Matthew Seaman:
On Tue, Oct 05, 2004 at 10:45:09AM +0200, Emanuel Strobl wrote:
[...]
There is an excellent hint for compiler flags to be found in the
19.4.3 section of the FreeBSD handbook.
Hm, this is for the world and is very well known and documented.
I'm talking about /usr/src/release/Makefile
The /usr/obj directory composes of the compiled applications from
the buildworld function. You can delete it after you did a successful
completion of the installworld on a system. That's what happens
when you do make clean in the /usr/src directory.
Again, I'm not talking about make installworld, but 'make release'
If you're using 'make release' you're expected to a) have your own
local copy of the FreeBSD src CVS repository and b) know how to use
cvs(1) and make(1). 'make release' is aimed at expert users;
beginners would be well advised to steer clear of it.
What you do is edit the /usr/src/release/Makefile, specifically the
CHROOTDIR, BUILDNAME and CVSROOT it tells you to set. Or specify them
on the command line if you prefer.
Then you setup the ${LOCAL_PATCHES} variable to point to a file of
patches to apply to the checked out chroot'ed source tree (hint: try
applying a patch to ${CHROOTDIR}/etc/make.conf to fiddle with the make
Ok, so share/examples/etc/make.conf is not evaluated like
etc/defautls/make.conf was before? That's the point I guess.
Thanks for your explanation, I've been building releases some years ago, so
usually I'm quiet familar with cvs.
Thanks,
-Harry
flags). Similarly you can run a shell script ${LOCAL_SCRIPT} to do
whatever you want to the chroot'ed sources before building.
Cheers,
Matthew
pgpFeVpm7xFMS.pgp
Description: PGP signature
Re: Release Compiler options
Emanuel Strobl [EMAIL PROTECTED] writes: Ok, so share/examples/etc/make.conf is not evaluated like etc/defautls/make.conf was before? That's the point I guess. /etc/defaults/make.conf was *never* evaluated. That's *why* it was moved out to the examples tree. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Release Compiler options
On Tue, Oct 05, 2004 at 09:01:04AM -0400, Lowell Gilbert wrote:
Emanuel Strobl [EMAIL PROTECTED] writes:
Ok, so share/examples/etc/make.conf is not evaluated like
etc/defautls/make.conf was before? That's the point I guess.
/etc/defaults/make.conf was *never* evaluated. That's *why* it was
moved out to the examples tree.
/etc/defaults/make.conf was, and still is, evaluated in 4-stable. [1]
However since all lines in that file are commented out it doesn't
actually set any defaults (unlike e.g. /etc/defaults/rc.conf which
actually sets default values for many variables.)
However one has never (or at least not for a very long time) been
supposed to modify /etc/defaults/make.conf, but any local modifications
are supposed to go into /etc/make.conf which means that it made more
sense to move /etc/defaults/make.conf to /usr/share/examples/etc/make.conf
since it was just documentation of what variables one could set in
/etc/make.conf.
[1] From /usr/share/mk/sys.mk
[...]
.if exists(/etc/defaults/make.conf)
.include /etc/defaults/make.conf
.endif
__MAKE_CONF?=/etc/make.conf
.if exists(${__MAKE_CONF})
.include ${__MAKE_CONF}
.endif
[...]
--
Insert your favourite quote here.
Erik Trulsson
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: Release Compiler options
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Emanuel Strobl Sent: Monday, October 04, 2004 8:43 PM To: [EMAIL PROTECTED] Subject: Release Compiler options I really spent some time tracing the make release, but couldn't find any way to modify the compiler flags for the release. Why do I need a populated /usr/obj if it's never touched? I really think I'm missing something. Two years ago I had no problems building specail 4.4-RELEASEs. Any hint is welcome. There is an excellent hint for compiler flags to be found in the 19.4.3 section of the FreeBSD handbook. The /usr/obj directory composes of the compiled applications from the buildworld function. You can delete it after you did a successful completion of the installworld on a system. That's what happens when you do make clean in the /usr/src directory. -Mano -- Chris Haulmark System Admin. Freelancer In market for IT corrections for a salary. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
