Re: make world for a jail
On Dec 20, 2006, at 10:37 AM, Robin Becker wrote: I'm trying to make world for a jail build following the recipe in http://www.onlamp.com/pub/a/bsd/2003/09/04/jails.html First off I started by updating the src tree. I copied /usr/share/ examples/cvsup/stable-supfile edited the host name then I ran SERVER=`fastest_cvsup -q -c ca,us` cvsup -L2 -h $SERVER /root/bin/stable-supfile that seemd fine and stuff appeared in /usr/src as expected. mkdir /usr/jails mkdir /usr/jails/mailserver cd /usr/src make world DESTDIR=/usr/jails/mailserver Now I get an error building sendmail chmod 444 freebsd.cf rm -f freebsd.submit.cf m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ /usr/ src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 /usr/src/etc/ sendmail/freebsd.submit.mc freebsd.submit.cf chmod 444 freebsd.submit.cf ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 I'm not sure what this means. I looked in UPDATING and see references to FreeBSD 6.1-RELEASE; so am I trying to build a 6.1 kernel with my 6.0 system? I'm guessing that *default release=cvs tag=RELENG_6 should have been *default release=cvs tag=RELENG_6_0 One other thing is that during the build I saw sub makes going on that had a different DESTDIR. Eg make -f Makefile.inc1 DESTDIR=/usr/obj/usr/src/tmp par-all how do I get things built into my desired location or is the make world eventually going to put them in the right place? I'd suggest not using make world. Use make buildworld followed by make installworld. Here is my very terse set of notes on building a fat jail: http://phryd.vox.com/library/post/freebsd-jail-howto-in-a- nutshell.html Note that my experience was with RELENG_6_1 -- fred ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make world for a jail
On 2006-12-20 18:37, Robin Becker [EMAIL PROTECTED] wrote: I'm trying to make world for a jail build following the recipe in http://www.onlamp.com/pub/a/bsd/2003/09/04/jails.html First off I started by updating the src tree. I copied /usr/share/examples/cvsup/stable-supfile edited the host name then I ran SERVER=`fastest_cvsup -q -c ca,us` cvsup -L2 -h $SERVER /root/bin/stable-supfile that seemd fine and stuff appeared in /usr/src as expected. mkdir /usr/jails mkdir /usr/jails/mailserver cd /usr/src make world DESTDIR=/usr/jails/mailserver That's not going to work, unless you have already run at least *once* the commands: # cd /usr/src # make DESTDIR=/usr/jails/mailserver distribution before running the installworld stage of make world. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make world for a jail
.. I fixed up my /usr/src tree to be latest RELENG_6_0 in line with my machine and ran cd /usr/src make world DESTDIR=/usr/jails/mailserver however, this seems to produce a lot of stuff in /usr/obj (the normal make world destination). Eventually the make fails with this message ## make: don't know how to make /usr/jails/mailserver/usr/lib/libc.a. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. ## In line with my earlier observation that the sub makes were being called like this make -f Makefile.inc1 DESTDIR=/usr/obj/usr/src/tmp par-all is there some magic that's required to make world into a specified DESTDIR? -- Robin Becker ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
make world for a jail
I'm trying to make world for a jail build following the recipe in http://www.onlamp.com/pub/a/bsd/2003/09/04/jails.html First off I started by updating the src tree. I copied /usr/share/examples/cvsup/stable-supfile edited the host name then I ran SERVER=`fastest_cvsup -q -c ca,us` cvsup -L2 -h $SERVER /root/bin/stable-supfile that seemd fine and stuff appeared in /usr/src as expected. mkdir /usr/jails mkdir /usr/jails/mailserver cd /usr/src make world DESTDIR=/usr/jails/mailserver Now I get an error building sendmail chmod 444 freebsd.cf rm -f freebsd.submit.cf m4 -D_CF_DIR_=/usr/src/etc/sendmail/../../contrib/sendmail/cf/ /usr/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 /usr/src/etc/sendmail/freebsd.submit.mc freebsd.submit.cf chmod 444 freebsd.submit.cf ERROR: Required audit group is missing, see /usr/src/UPDATING. *** Error code 1 I'm not sure what this means. I looked in UPDATING and see references to FreeBSD 6.1-RELEASE; so am I trying to build a 6.1 kernel with my 6.0 system? I'm guessing that *default release=cvs tag=RELENG_6 should have been *default release=cvs tag=RELENG_6_0 One other thing is that during the build I saw sub makes going on that had a different DESTDIR. Eg make -f Makefile.inc1 DESTDIR=/usr/obj/usr/src/tmp par-all how do I get things built into my desired location or is the make world eventually going to put them in the right place? -- Robin Becker ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
re: re: make: don't know how to make when trying to make world for a jail
I was running a small script I wrote to set up a jail. I've used it before and
it works. It does just the same thing that the manpage for jail tells you to
do.
make_jail.sh:
#!/bin/sh
D=$1
cd /usr/src
mkdir -p $D
make world DESTDIR=$D
cd etc
make distribution DESTDIR=$D
mount_devfs devfs $D/dev
cd $D
ln -sf dev/null kernel
Then I just run that script with ./make_jail.sh
/usr/jail/jail.henrikssons.net.
I get the exact same output if I run make world
DESTDIR=/usr/jail/jail.henrikssons.net manually or with any other path.
make.conf:
# $FreeBSD: src/share/examples/etc/make.conf,v 1.218 2003/09/24 04:19:26
gshapiro Exp $
#
# NOTE: Please would any committer updating this file also update the
# make.conf(5) manual page, if necessary, which is located in
# src/share/man/man5/make.conf.5.
#
# /etc/make.conf, if present, will be read by make (see
# /usr/share/mk/sys.mk). It allows you to override macro definitions
# to make without changing your source tree, or anything the source
# tree installs.
#
# This file must be in valid Makefile syntax.
#
# There are additional things you can put into /etc/make.conf.
# You have to find those in the Makefiles and documentation of
# the source tree.
#
#
# The CPUTYPE variable controls which processor should be targeted for
# generated code. This controls processor-specific optimizations in
# certain code (currently only OpenSSL) as well as modifying the value
# of CFLAGS to contain the appropriate optimization directive to gcc.
# The automatic setting of CFLAGS may be overridden using the
# NO_CPU_CFLAGS variable below.
# Currently the following CPU types are recognized:
# Intel x86 architecture:
# (AMD CPUs) athlon-mp athlon-xp athlon-4 athlon-tbird athlon k6-3
# k6-2 k6 k5
# (Intel CPUs)p4 p3 p2 i686 i586/mmx i586 i486 i386
# Alpha/AXP architecture: ev67 ev6 pca56 ev56 ev5 ev45 ev4
# Intel ia64 architecture: itanium
#
# (?= allows to buildworld for a different CPUTYPE.)
#
CPUTYPE=p3
#NO_CPU_CFLAGS= true# Don't add -march=cpu to CFLAGS automatically
#NO_CPU_COPTFLAGS=true # Don't add -march=cpu to COPTFLAGS automatically
#
# CFLAGS controls the compiler settings used when compiling C code.
# Note that optimization settings above -O (-O2, ...) are not recommended
# or supported for compiling the world or the kernel - please revert any
# nonstandard optimization settings to -O before submitting bug reports
# to the developers.
# Note also that at this time the -O2 setting is known to produce BROKEN
# CODE on the Alpha platform.
#
CFLAGS= -O -pipe
#
# CXXFLAGS controls the compiler settings used when compiling C++ code.
# Note that CXXFLAGS is initially set to the value of CFLAGS. If you wish
# to add to CXXFLAGS value, += must be used rather than =. Using =
# alone will remove the often needed contents of CFLAGS from CXXFLAGS.
#
#CXXFLAGS+= -fmemoize-lookups -fsave-memoized
#
# MAKE_SHELL controls the shell used internally by make(1) to process the
# command scripts in makefiles. Three shells are supported, sh, ksh, and
# csh. Using sh is most common, and advised. Using ksh *may* work, but is
# not guaranteed to. Using csh is absurd. The default is to use sh.
#
#MAKE_SHELL?=sh
#
# BDECFLAGS are a set of gcc warning settings that Bruce Evans has suggested
# for use in developing FreeBSD and testing changes. They can be used by
# putting CFLAGS+=${BDECFLAGS} in /etc/make.conf. -Wconversion is not
# included here due to compiler bugs, e.g., mkdir()'s mode_t argument.
#
#BDECFLAGS= -W -Wall -ansi -pedantic -Wbad-function-cast -Wcast-align \
# -Wcast-qual -Wchar-subscripts -Winline \
# -Wmissing-prototypes -Wnested-externs -Wpointer-arith \
# -Wredundant-decls -Wshadow -Wstrict-prototypes -Wwrite-strings
#
# To compile just the kernel with special optimizations, you should use
# this instead of CFLAGS (which is not applicable to kernel builds anyway).
# There is very little to gain by using higher optimization levels, and doing
# so can cause problems.
#
COPTFLAGS= -O -pipe
#
# To build the system compiler such that it forces high optimization levels to
# a lower one. GCC -O2+ is known to trigger known optimizer bugs at various
# times -- this is worse on the Alpha platform. The value assigned here will
# be the highest optimization value used.
#WANT_FORCE_OPTIMIZATION_DOWNGRADE=1
#
# Compare before install
#INSTALL=install -C
#
# Mtree will follow symlinks
#MTREE_FOLLOWS_SYMLINKS= -L
#
# To build ppp with normal permissions
#PPP_NOSUID=true
#
# To enable installing ssh(1) with the setuid bit turned on
#ENABLE_SUID_SSH= true
#
# To enable installing newgrp(1) with the setuid bit turned on.
# Without the setuid bit, newgrp cannot change users' groups.
#ENABLE_SUID_NEWGRP=true
#
# To avoid building various parts of the base system:
#NO_CVS=true# do not build CVS
#NO_CXX=true# do not build C++ and friends
NO_BIND
make: don't know how to make when trying to make world for a jail
Hi, I'm running FreeBSD 5.3-RELEASE-p5, updated it today without any problems at all but I'm getting errors when I run make world, after everything was cleaned, didn't knew I was going to build a jail so I cleaned. I completly removed obj and ran make clean and cleandir twice so no old files are left. I can run just make world I builds without any problems but when I run it with the path to my jail it fails. Any ideas why and how I can fix that? Here is the output: -- stage 1.2: bootstrap tools -- cd /usr/src; MAKEOBJDIRPREFIX=/usr/obj/usr/src/i386 DESTDIR= INSTALL=sh /usr/src/tools/install.sh PATH=/usr/obj/usr/src/i386/legacy/usr/sbin:/usr/obj/usr/src/i386/legacy/usr/bin:/usr/obj/usr/src/i386/legacy/usr/games:/sbin:/bin:/usr/sbin:/usr/bin WORLDTMP=/usr/obj/usr/src/i386 MAKEFLAGS=-m /usr/src/tools/build/mk DESTDIR=/usr/jail/jail.henrikssons.net -m /usr/src/share/mk make -f Makefile.inc1 BOOTSTRAPPING=503001 -DNOHTML -DNOINFO -DNOLINT -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -DNO_CPU_CFLAGS -DNO_WARNS bootstrap-tools === games/fortune/strfile /usr/obj/usr/src/i386/usr/src/games/fortune/strfile created for /usr/src/games/fortune/strfile rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/legacy/usr/include /usr/src/games/fortune/strfile/strfile.c echo strfile: /usr/jail/jail.henrikssons.net/usr/lib/libc.a /usr/obj/usr/src/i386/legacy/usr/lib/libegacy.a .depend cc -O -pipe -I/usr/obj/usr/src/i386/legacy/usr/include -c /usr/src/games/fortune/strfile/strfile.c make: don't know how to make /usr/jail/jail.henrikssons.net/usr/lib/libc.a. Stop *** Error code 2 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Daniel Johansson - [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make: don't know how to make when trying to make world for a jail
Daniel Johansson wrote: Hi, I'm running FreeBSD 5.3-RELEASE-p5, updated it today without any problems at all but I'm getting errors when I run make world, after everything was cleaned, didn't knew I was going to build a jail so I cleaned. I completly removed obj and ran make clean and cleandir twice so no old files are left. I can run just make world I builds without any problems but when I run it with the path to my jail it fails. Any ideas why and how I can fix that? Here is the output: What was the command that you ran and what's in your make.conf? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
