Re: Building -CURRENT on -STABLE

2020-01-12 Thread Gordon Bergling 
Hi,

if someone is facing the same error, the build variable MAKEOBJDIRPREFIX must 
be set within the environment and _not_ within the make context. I would also 
suggest that the source and object directories are on the same partition. 

My sources where located in my home directory and the object directory on a 
separate zfs pool, but using symlinks to fake the directory structure 
wasn't successful. With the following steps I was able to build on the fast
machine, and install via nfs on the client.

On the build machine:
# mkdir -p /boiler/nfs/{src,obj}
# export MAKEOBJDIRPREFIX=/boiler/nfs/obj
# cd /boiler/nfs/src && git pull
# make -s -j 4 buildworld buildkernel > /boiler/nfs/logs/build.log 2>&1

On the target machine (assuming server:/boiler/nfs is mounted on /boiler/nfs at 
the client)
# env MAKEOBJDIRPREFIX=/boiler/nfs/obj make installkernel
# env MAKEOBJDIRPREFIX=/boiler/nfs/obj make installworld
# mergemaster -Ui -m /boiler/nfs/src/

Best,

Gordon

On Thu, Jan 09, 2020 at 11:45:21AM +0100, Gordon Bergling wrote:
> Hi,
> 
> I am currently about to setup an -CURRENT system, which should gets updated 
> via a build 
> server that’s runs on -STABLE and shares the src and obj directories via NFS 
> to -CURRENT system.
> 
> While doing a „make -s -j 4 buildworld buildkernel“ the builds fails randomly 
> with the following error.
> 
> -
> ===> sbin/fsirand (all)
> ===> sbin/gbde (all)
> ===> sbin/geom (all)
> ===> kerberos5/libexec/kimpersonate (all)
> ld: error: undefined symbol: glabel_class_commands
> >>> referenced by geom.c
> >>>   geom.o:(get_class)
> 
> ld: error: undefined symbol: glabel_version
> >>> referenced by geom.c
> >>>   geom.o:(get_class)
> 
> ld: error: undefined symbol: gpart_class_commands
> >>> referenced by geom.c
> >>>   geom.o:(get_class)
> 
> ld: error: undefined symbol: gpart_version
> >>> referenced by geom.c
> >>>   geom.o:(get_class)
> cc: error: linker command failed with exit code 1 (use -v to see invocation)
> --- geom.full ---
> *** [geom.full] Error code 1
> 
> make[4]: stopped in /home/gbergling/sources/freebsd/freebsd/sbin/geom
> 1 error
> 
> make[4]: stopped in /home/gbergling/sources/freebsd/freebsd/sbin/geom
> A failure has been detected in another branch of the parallel make
> -
> 
> I also tried the build without the „j“-Flag but the error was the same.
> 
> Do you have any hints what could have caused this?
> 
> The -STABLE machine is stock and no special things are setup within src.conf 
> or make.conf.
> 
> Best regards,
> 
> Gordon
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: building current with DIRDEPS_BUILD [was meta mode]

2018-03-03 Thread Bryan Drewery 
On 3/3/2018 10:13 AM, Eitan Adler wrote:
> #make toolchain
> 

This is now known as DIRDEPS_BUILD. META_MODE is something different
now, see man src.conf.

This failure is not unexpected as the build breaks with LLVM updates.
I'll work on a fix this next week.

> ...
> Building 
> /srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen/clang-tblgen.full
> c++: error: no such file or directory:
> '/srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvmminimal/libllvmminimal.a'
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /srv/src/fbsd/head/usr.bin/clang/clang-tblgen
> .ERROR_TARGET='clang-tblgen.full'
> .ERROR_META_FILE='/srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen/clang-tblgen.full.meta'
> .MAKE.LEVEL='1'
> MAKEFILE=''
> .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose'
> _ERROR_CMD='/usr/bin/c++ -O2 -pipe
> -I/srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvm
> -I/srv/src/fbsd/head/lib/clang/include -I/srv/src/fbsd/head/
> contrib/llvm/include -DLLVM_BUILD_GLOBAL_ISEL -D__STDC_LIMIT_MACROS
> -D__STDC_CONSTANT_MACROS
> -DLLVM_DEFAULT_TARGET_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DLLV
> M_HOST_TRIPLE=\"x86_64-unknown-freebsd12.0\" -DDEFAULT_SYSROOT=\"\"
> -ffunction-sections -fdata-sections -isystem
> /srv/obj/srv/src/fbsd/head/stage/freebsd12-am
> d64/usr/include -DHOSTPROG -gline-tables-only -fstack-protector-strong
> -Wno-empty-body -Wno-string-plus-int -Wno-unused-const-variable
> -Wno-tautological-compa
> re -Wno-unused-value -Wno-parentheses-equality -Wno-unused-function
> -Wno-enum-conversion -Wno-unused-local-typedef
> -Wno-address-of-packed-member -Wno-switch -
> Wno-switch-enum -Wno-knr-promoted-parameter -Wno-parentheses
> -Qunused-arguments -std=c++11 -fno-exceptions -fno-rtti -stdlib=libc++
> -Wno-c++11-extensions  -Wl
> ,--gc-sections 
> -Wl,-rpath-link,/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/lib
> -o clang-tblgen.full  ClangASTNodesEmitter.o ClangAttrEmitter.o ClangC
> ommentCommandInfoEmitter.o
> ClangCommentHTMLNamedCharacterReferenceEmitter.o
> ClangCommentHTMLTagsEmitter.o ClangDataCollectorsEmitter.o
> ClangDiagnosticsEmitter
> .o ClangOptionDocEmitter.o ClangSACheckersEmitter.o NeonEmitter.o
> TableGen.o 
> /srv/obj/srv/src/fbsd/head/freebsd12-amd64/lib/clang/libllvmminimal/libllvmminima
> l.a -L/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/lib
> -lncursesw  -lpthread;'
> .CURDIR='/srv/src/fbsd/head/usr.bin/clang/clang-tblgen'
> .MAKE='make'
> .OBJDIR='/srv/obj/srv/src/fbsd/head/usr.bin/clang/clang-tblgen'
> .TARGETS=' all'
> DESTDIR='/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64'
> LD_LIBRARY_PATH=''
> MACHINE='host'
> MACHINE_ARCH='amd64'
> ...
> 
> Stop.
> make: stopped in /srv/src/fbsd/head
> .ERROR_TARGET='/srv/src/fbsd/head/usr.bin/clang/clang-tblgen.host'
> .ERROR_META_FILE=''
> .MAKE.LEVEL='0'
> MAKEFILE=''
> .MAKE.MODE='meta missing-filemon=yes missing-meta=yes silent=yes verbose'
> _ERROR_CMD='.PHONY'
> .CURDIR='/srv/src/fbsd/head'
> .MAKE='make'
> .OBJDIR='/srv/obj/srv/src/fbsd/head/amd64.amd64'
> .TARGETS='toolchain'
> DESTDIR=''
> LD_LIBRARY_PATH=''
> MACHINE='amd64'
> MACHINE_ARCH='amd64'
> MAKEOBJDIRPREFIX=''
> MAKESYSPATH='/srv/src/fbsd/head/share/mk'
> MAKE_VERSION='20170510'
> PATH='/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/bin:/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/usr/sbin:/srv/obj/srv/src/fbsd/head/stage/free
> bsd12-amd64/bin:/srv/obj/srv/src/fbsd/head/stage/freebsd12-amd64/sbin:/home/eax/bin:/opt/local/libexec/ccache:/usr/local/libexec/ccache:/home/eax/.cargo/bin:/
> Users/eax/.local/bin:/home/eax/.local/lib/npm/bin:/home/eax/.gem/ruby/2.5.0/bin:/home/eax/.rvm/bin:/home/eax/Library/Python/3.6/bin:/home/eax/Library/Python/2
> .7/bin:/opt/local/sbin:/opt/local/bin:/opt/local/bin/pear:/opt/local/lib/mariadb-10.2/bin:/usr/local/mysql/bin:/opt/local/libexec/perl5.24/sitebin:/home/eax/p
> erl5/bin:/home/eax/Library/Android/sdk/platform-tools:/home/eax/.luarocks/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin'
> SRCTOP='/srv/src/fbsd/head'
> OBJTOP='/srv/obj/srv/src/fbsd/head/amd64.amd64'
> @ 1520100350 [2018-03-03 18:05:50] Failed toolchain seconds=351
> make toolchain 181.64s user 100.10s system 80% cpu 5:51.48 total; max
> RSS 165028Ki
> 


-- 
Regards,
Bryan Drewery
bdrewery@freenode/EFNet
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Building Current

2017-03-04 Thread Ngie Cooper 

> On Mar 4, 2017, at 13:19, Roberto Rodriguez Jr  wrote:
> 
> Would make -DNO_CLEAN=NO also/maybe help as well?

Remove =NO from your invocation above. That would define a variable as: 
${NO_CLEAN=NO}=1
HTH,
-Ngie
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Building Current

2017-03-04 Thread Roberto Rodriguez Jr 
Would make -DNO_CLEAN=NO also/maybe help as well?
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Building Current

2017-03-04 Thread Navdeep Parhar 
On Sat, Mar 04, 2017 at 03:46:20PM -0500, Roberto Rodriguez Jr wrote:
> What tools can I use to make the building a little faster?
> 

The src tree supports incremental builds. You'll need to load the
filemon module and add WITH_META_MODE=yes in /etc/src-env.conf to use
it.  See the WITH_META_MODE bits in src.conf(5), build(7) for some more
details.

It would be nice to have WITH_META_MODE as default but that's a separate
discussion.

Regards,
Navdeep
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Building Current

2017-03-04 Thread Manfred Antar 

> On Mar 4, 2017, at 12:46 PM, Roberto Rodriguez Jr  
> wrote:
> 
> What tools can I use to make the building a little faster?
> 
> I'm using an AMD 64 HP 15 laptop and I update the source tree daily and
> rebuild so if I have any errors I could report. Just curious if there's any
> extra software I could be implementing to make the compiling faster. Thank
> you
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

You could use /usr/ports/devel/ccache
It will speed things up after a build or two


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Building Current

2017-03-04 Thread Manfred Antar 

> On Mar 4, 2017, at 12:46 PM, Roberto Rodriguez Jr  
> wrote:
> 
> What tools can I use to make the building a little faster?
> 
> I'm using an AMD 64 HP 15 laptop and I update the source tree daily and
> rebuild so if I have any errors I could report. Just curious if there's any
> extra software I could be implementing to make the compiling faster. Thank
> you
> ___
> freebsd-current@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
> 
> -- 
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> 

You could use /usr/ports/devel/ccache
It will speed things up after a build or two


-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Building current no longer possible on 8.2, worked 7 days ago

2013-05-22 Thread Ulrich Spörlein 
On Tue, 2013-05-21 at 04:10:30 +0200, Ulrich Spörlein wrote:
 On Mon, 2013-05-20 at 23:06:40 +0200, Matthias Andree wrote:
  Am 20.05.2013 15:49, schrieb Ulrich Spörlein:
   Hey all,
   
   I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d
   ago, now it's kaput:
  
  ...
  
   This is on src r250825 and the host is running
   FreeBSD scan.freebsd.your.org 8.2-STABLE FreeBSD 8.2-STABLE #2 r223420: 
   Wed Jun 22 11:15:56 UTC 2011
   u...@scan.freebsd.your.org:/usr/obj/usr/src/sys/GENERIC  amd64
  
  In case you haven't noticed, FreeBSD 8.2 went out of support end of July
  2012, i. e. 10 months ago...
 
 Just updated to 8-STABLE and the same build error occurs.

Updated those machines to 9.1 and still the same build error. Am I the
only one seeing this?

I have a different 9-STABLE machine that is fine, but I cannot figure
out what is wrong on the two VMs where this problem occurrs.

The working system does:

=== tools/build (obj,includes,depend,all,install)
/usr/obj/data/src/freebsd-head/tmp/data/src/freebsd-head/tools/build created 
for /data/src/freebsd-head/tools/build
set -e; cd /data/src/freebsd-head/tools/build; 
/usr/obj/data/src/freebsd-head/make.amd64/make buildincludes; 
/usr/obj/data/src/freebsd-head/make.amd64/make installincludes
rm -f .depend
mkdep -f .depend -a
-I/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache 
-I/data/src/freebsd-head/tools/build/../../lib/libc/include 
-I/usr/obj/data/src/freebsd-head/tmp/legacy/usr/include -std=gnu99   
/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache/pwcache.c
cc  -O2 -pipe -I/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache  
-I/data/src/freebsd-head/tools/build/../../lib/libc/include -std=gnu99   
-I/usr/obj/data/src/freebsd-head/tmp/legacy/usr/include -c 
/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache/pwcache.c -o 
pwcache.o
building static egacy library
ranlib libegacy.a
sh /data/src/freebsd-head/tools/install.sh -C -o root -g wheel -m 444   
libegacy.a /usr/obj/data/src/freebsd-head/tmp/legacy/usr/lib


The broken ones do:

=== tools/build (obj,includes,depend,all,install)
/usr/obj/data/src/freebsd-head/tmp/data/src/freebsd-head/tools/build created 
for /data/src/freebsd-head/tools/build
set -e; cd /data/src/freebsd-head/tools/build; 
/usr/obj/data/src/freebsd-head/make.amd64/make buildincludes; 
/usr/obj/data/src/freebsd-head/make.amd64/make installincludes
rm -f .depend
mkdep -f .depend -a
-I/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache 
-I/data/src/freebsd-head/tools/build/../../lib/libc/include 
-I/usr/obj/data/src/freebsd-head/tmp/legacy/usr/include -std=gnu99   
/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache/pwcache.c
cc  -O2 -pipe -I/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache  
-I/data/src/freebsd-head/tools/build/../../lib/libc/include -std=gnu99   
-I/usr/obj/data/src/freebsd-head/tmp/legacy/usr/include -c 
/data/src/freebsd-head/tools/build/../../contrib/libc-pwcache/pwcache.c -o 
pwcache.o  
building static egacy library
ranlib /data/src/freebsd-head/tools/build/libegacy.a  
sh /data/src/freebsd-head/tools/install.sh -C -o root -g wheel -m 444   
libegacy.a /usr/obj/data/src/freebsd-head/tmp/legacy/usr/lib  
install: libegacy.a: No such file or directory
*** Error code 71

when building the legacy compatibility shims. The only difference is
that ranlib uses the relative path in the working case and that then
works out fine.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Building current no longer possible on 8.2, worked 7 days ago

2013-05-20 Thread Matthias Andree 
Am 20.05.2013 15:49, schrieb Ulrich Spörlein:
 Hey all,
 
 I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d
 ago, now it's kaput:

...

 This is on src r250825 and the host is running
 FreeBSD scan.freebsd.your.org 8.2-STABLE FreeBSD 8.2-STABLE #2 r223420: Wed 
 Jun 22 11:15:56 UTC 2011
 u...@scan.freebsd.your.org:/usr/obj/usr/src/sys/GENERIC  amd64

In case you haven't noticed, FreeBSD 8.2 went out of support end of July
2012, i. e. 10 months ago...

___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Building current no longer possible on 8.2, worked 7 days ago

2013-05-20 Thread Ulrich Spörlein 
On Mon, 2013-05-20 at 23:06:40 +0200, Matthias Andree wrote:
 Am 20.05.2013 15:49, schrieb Ulrich Spörlein:
  Hey all,
  
  I'm running the coverity builds/scan on a 8.2 VM, buildworld was fine 7d
  ago, now it's kaput:
 
 ...
 
  This is on src r250825 and the host is running
  FreeBSD scan.freebsd.your.org 8.2-STABLE FreeBSD 8.2-STABLE #2 r223420: Wed 
  Jun 22 11:15:56 UTC 2011
  u...@scan.freebsd.your.org:/usr/obj/usr/src/sys/GENERIC  amd64
 
 In case you haven't noticed, FreeBSD 8.2 went out of support end of July
 2012, i. e. 10 months ago...

Just updated to 8-STABLE and the same build error occurs.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

Re: Building -CURRENT with 4.5-RELEASE

2002-10-26 Thread Ulrich 'Q' Spoerlein 
On Tue, 22 Oct 2002 04:25:23 +0200, you wrote:

Is it possible, or do I need to use a more recent installation to be able to
build -CURRENT?

it was possible for me, but i had to go through a lot of hassles
installing -CURRENT from within -STABLE.

i used the DESTDIR-switch to install everything to /mnt/ (where my
-current partition was mounted). but mergemaster failed due to a system
call lacking (can't remember which one, i think it tried to start a
programm in /mnt/bin which failed because it was linked against libc.so.5
i fixed that by linking libc.so.4 to libc.so.5 temporarily).
the next pitfall is mergemaster NOT creating files/directories necessary,
thus using it on a clean partition (only installworld'd and
installkernel'd) will fail and you have to create some files/directories
by hand.

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Building -CURRENT with 4.5-RELEASE

2002-10-25 Thread M. Warner Losh 
In message: [EMAIL PROTECTED]
Tim Kientzle [EMAIL PROTECTED] writes:
:   On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard H=E4ring wrote:
: 
: make installworld dumps core at installing passwd (4.5-RELEASE).
: 
: 
: Brooks Davis:
: 
:  Are you running a current kernel at this point?  If you aren't it's safe
:  to say it won't work.
: 
: The directions in UPDATING leave you running
: an OLD kernel after rebooting into single-user.
: (Installkernel puts the kernel in the new location,
: but the old boot loader is still on disk, so it
: loads the kernel from the old location.)  If
: a new kernel is required at this point, then
: UPDATING is wrong or installkernel is wrong.

You are correct about this.  I'll update it to include installing the
new bootblocks as well, if that isn't already in there for the 4.x -
5.0 upgrade path.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: building -CURRENT on RELENG_4

2002-10-23 Thread Ruslan Ermilov 
On Wed, Oct 23, 2002 at 01:08:31AM +0700, Max Khon wrote:
 hi, there!
 
 cross-building -CURRENT on RELENG_4 is broken in src/usr.bin/xlint/lint1:
 
 --- cut here ---
 ...
 sh /usr/fbsd/HEAD/src/usr.bin/xlint/lint1/makeman /usr/libexec/lint1 -m lint.7
 lint1: illegal option -- m
 usage: lint1 [-abcdeghprstuvyzF] src dest
 gzip -cn lint.7  lint.7.gz
 --- cut here ---
 
Peter has broken it in his latest revision to xlint/lint1/Makefile.
This should fix it:

%%%
Index: Makefile
===
RCS file: /home/ncvs/src/usr.bin/xlint/lint1/Makefile,v
retrieving revision 1.15
diff -u -r1.15 Makefile
--- Makefile17 Sep 2002 01:49:00 -  1.15
+++ Makefile23 Oct 2002 10:58:53 -
@@ -17,6 +17,6 @@
 .PATH: ${.CURDIR}/../common
 
 lint.7: makeman
-   sh ${.CURDIR}/makeman ${BINDIR}/${PROG} -m ${.TARGET}
+   sh ${.CURDIR}/makeman ${DESTDIR}${BINDIR}/${PROG} -m ${.TARGET}
 
 .include bsd.prog.mk
%%%

DESTDIR is set to WORLDTMP during buildworld (WMAKEENV in Makefile.inc1).


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age



msg44803/pgp0.pgp
Description: PGP signature

Re: Building -CURRENT with 4.5-RELEASE

2002-10-23 Thread Gerhard Haering 
* Brooks Davis [EMAIL PROTECTED] [2002-10-22 16:55 -0700]:
 On Wed, Oct 23, 2002 at 01:48:14AM +0200, Gerhard H?ring wrote:
  * Brooks Davis [EMAIL PROTECTED] [2002-10-22 15:01 -0700]:
   Are you running a current kernel at this point?  If you aren't it's safe
   to say it won't work.
  
  No, this is 4.5-RELEASE, as I said. By current kernel, do you mean an
  up-to-date FreeBSD 4, like 4.7-STABLE, or a -CURRENT kernel?
 
 I mean a -CURRENT kernel like /usr/src/UPDATING tells you to use.
 UPDATING is the authoritative document on this subject.

Ah, thanks. I read about this in the handbook, but reading UPDATING just
didn't provide anything interesting before ;-)

With the information from UPDATING, I now got -CURRENT installed, building
from 4.7-RELEASE this time.

-- Gerhard

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Ruslan Ermilov 
On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote:
 Is it possible, or do I need to use a more recent installation to be able to
 build -CURRENT?
 
Yes, it is.  It should even be possible to build -CURRENT with
as early as 4.0-RELEASE.  If it doesn't, please drop me a line.


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age



msg45019/pgp0.pgp
Description: PGP signature

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Gerhard Häring 
* Ruslan Ermilov [EMAIL PROTECTED] [2002-10-22 12:23 +0300]:
 On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote:
  Is it possible, or do I need to use a more recent installation to be able to
  build -CURRENT?
  
 Yes, it is.  It should even be possible to build -CURRENT with
 as early as 4.0-RELEASE.  If it doesn't, please drop me a line.

make installworld dumps core at installing passwd (4.5-RELEASE).

I've now dl-ed and burnt the DP1 CD instead and am trying to get this to
run.

-- Gerhard

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Brooks Davis 
On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard Häring wrote:
 * Ruslan Ermilov [EMAIL PROTECTED] [2002-10-22 12:23 +0300]:
  On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote:
   Is it possible, or do I need to use a more recent installation to be able to
   build -CURRENT?
   
  Yes, it is.  It should even be possible to build -CURRENT with
  as early as 4.0-RELEASE.  If it doesn't, please drop me a line.
 
 make installworld dumps core at installing passwd (4.5-RELEASE).

Are you running a current kernel at this point?  If you aren't it's safe
to say it won't work.

-- Brooks

-- 
Any statement of the form X is the one, true Y is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4



msg45091/pgp0.pgp
Description: PGP signature

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Brooks Davis 
On Wed, Oct 23, 2002 at 01:48:14AM +0200, Gerhard Häring wrote:
 * Brooks Davis [EMAIL PROTECTED] [2002-10-22 15:01 -0700]:
  Are you running a current kernel at this point?  If you aren't it's safe
  to say it won't work.
 
 No, this is 4.5-RELEASE, as I said. By current kernel, do you mean an
 up-to-date FreeBSD 4, like 4.7-STABLE, or a -CURRENT kernel?

I mean a -CURRENT kernel like /usr/src/UPDATING tells you to use.
UPDATING is the authoritative document on this subject.

 When I came to FreeBSD, ppl told me that you don't update the kernel
 separately, so I'm not sure what you mean.

You don't want to randomly update the kernel without updating userland
because some program like ipfw will stop working sometimes.  On the
flip side, if you don't update the kernel before install world, the
old kernel may not support syscalls required by the new binaries.  In
the past this has included things like /bin/sh so it is necessicary to
install a new kernel before installing a new world unless you want to
get your self into a real mess.  Additionaly, it's very easy to switch
back to an old kernel.  Switching back to an older world requires
backups.

-- Brooks

-- 
Any statement of the form X is the one, true Y is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4



msg45098/pgp0.pgp
Description: PGP signature

Re: Building -CURRENT with 4.5-RELEASE

2002-10-22 Thread Gerhard Häring 
* Brooks Davis [EMAIL PROTECTED] [2002-10-22 15:01 -0700]:
 On Tue, Oct 22, 2002 at 11:52:11PM +0200, Gerhard Häring wrote:
  * Ruslan Ermilov [EMAIL PROTECTED] [2002-10-22 12:23 +0300]:
   On Tue, Oct 22, 2002 at 04:25:23AM +0200, Gerhard Haering wrote:
Is it possible, or do I need to use a more recent installation to be able to
build -CURRENT?

   Yes, it is.  It should even be possible to build -CURRENT with
   as early as 4.0-RELEASE.  If it doesn't, please drop me a line.
  
  make installworld dumps core at installing passwd (4.5-RELEASE).
 
 Are you running a current kernel at this point?  If you aren't it's safe
 to say it won't work.

No, this is 4.5-RELEASE, as I said. By current kernel, do you mean an
up-to-date FreeBSD 4, like 4.7-STABLE, or a -CURRENT kernel?

When I came to FreeBSD, ppl told me that you don't update the kernel
separately, so I'm not sure what you mean.

Confused,

Gerhard

PS: Using DP1 to compile -CURRENT CVS also doesn't work :-( 

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: building -current on -stable broken?

2002-05-01 Thread Kenneth D. Merry 

On Mon, Apr 29, 2002 at 10:33:05 +0300, Ruslan Ermilov wrote:
 On Sun, Apr 28, 2002 at 10:27:10PM -0600, Kenneth D. Merry wrote:
  
  I'm trying to build -current from today (4/28/2002) on a -stable box with a
  kernel/world from April 25th.
  
  It blows up in xlint:
  
  ==
  cc -O -pipe  -I. -I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1 
-I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1/../arch/i386 
-I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1/../common-D__FBSDID=__RCSID 
 -static -o lint1 cgram.o scan.o mem1.o mem.o err.o main1.o decl.o tree.o func.o 
init.o emit.o emit1.o inittyp.o -ll -lm
  cgram.o: In function `yyparse':
  cgram.o(.text+0x10b8): undefined reference to `xcalloc'
  cgram.o(.text+0x10f0): undefined reference to `xcalloc'
  scan.o: In function `ccon':
  scan.o(.text+0x23f7): undefined reference to `xcalloc'
  func.o: In function `label':
  func.o(.text+0x6a8): undefined reference to `xcalloc'
  init.o: In function `prepinit':
  init.o(.text+0x78): undefined reference to `xcalloc'
  init.o(.text+0x214): more undefined references to `xcalloc' follow
  emit.o: In function `outopen':
  emit.o(.text+0x4f): undefined reference to `xmalloc'
  emit.o: In function `outxbuf':
  emit.o(.text+0xd4): undefined reference to `xrealloc'
  emit1.o: In function `ttos':
  emit1.o(.text+0x2d5): undefined reference to `xmalloc'
  *** Error code 1
  
  Stop in /c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1.
  *** Error code 1
  
  Stop in /c/ken/perforce/FreeBSD-ken/src.
  *** Error code 1
  
  Stop in /c/ken/perforce/FreeBSD-ken/src.
  *** Error code 1
  
  Stop in /c/ken/perforce/FreeBSD-ken/src.
  ==
  
  Am I doing something wrong here or is building -current on -stable broken?
  
 Seems to work OK here; xcalloc() and xmalloc() are defined in mem.c.

The problem I'm having is a stale version of xlint/lint1/mem.c in my
cvsup-perforce gateway tree.

cvs has a similar problem.  If I update an existing tree, lint1/mem.c
doesn't get deleted even though everything in that directory is on the
HEAD, and mem.c is in the attic!

# pwd  
/a/src/usr.bin/xlint/lint1
# cvs update -Pd
cvs update: Updating .
# ls -la mem.c
-rw-r--r--  1 root  wheel  2398 Apr 15 11:43 mem.c
# cvs status mem.c
===
File: mem.c Status: Up-to-date

   Working revision:1.1 Mon Apr 15 17:43:04 2002
   Repository revision: 1.1 /usr/local/cvs/src/usr.bin/xlint/lint1/Attic/mem.c,v
   Sticky Tag:  (none)
   Sticky Date: (none)
   Sticky Options:  (none)


If I checkout a new copy of xlint, though, I don't get a copy of lint1/mem.c.

I suspect cvsup has a similar problem -- even if I remove the
checkouts.cvs:. file, xlint/lint1/mem.c still gets checked out, and
it's a version from 1995 at that!

C src/usr.bin/xlint/lint1/mem.c,v . . 2#871#110#10157933134#39763#444 1.1.1.1 
95.11.05.15.56.40 2#871#19#8155870004#23983#600

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: building -current on -stable broken?

2002-04-29 Thread Ruslan Ermilov 

On Sun, Apr 28, 2002 at 10:27:10PM -0600, Kenneth D. Merry wrote:
 
 I'm trying to build -current from today (4/28/2002) on a -stable box with a
 kernel/world from April 25th.
 
 It blows up in xlint:
 
 ==
 cc -O -pipe  -I. -I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1 
-I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1/../arch/i386 
-I/c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1/../common-D__FBSDID=__RCSID 
 -static -o lint1 cgram.o scan.o mem1.o mem.o err.o main1.o decl.o tree.o func.o 
init.o emit.o emit1.o inittyp.o -ll -lm
 cgram.o: In function `yyparse':
 cgram.o(.text+0x10b8): undefined reference to `xcalloc'
 cgram.o(.text+0x10f0): undefined reference to `xcalloc'
 scan.o: In function `ccon':
 scan.o(.text+0x23f7): undefined reference to `xcalloc'
 func.o: In function `label':
 func.o(.text+0x6a8): undefined reference to `xcalloc'
 init.o: In function `prepinit':
 init.o(.text+0x78): undefined reference to `xcalloc'
 init.o(.text+0x214): more undefined references to `xcalloc' follow
 emit.o: In function `outopen':
 emit.o(.text+0x4f): undefined reference to `xmalloc'
 emit.o: In function `outxbuf':
 emit.o(.text+0xd4): undefined reference to `xrealloc'
 emit1.o: In function `ttos':
 emit1.o(.text+0x2d5): undefined reference to `xmalloc'
 *** Error code 1
 
 Stop in /c/ken/perforce/FreeBSD-ken/src/usr.bin/xlint/lint1.
 *** Error code 1
 
 Stop in /c/ken/perforce/FreeBSD-ken/src.
 *** Error code 1
 
 Stop in /c/ken/perforce/FreeBSD-ken/src.
 *** Error code 1
 
 Stop in /c/ken/perforce/FreeBSD-ken/src.
 ==
 
 Am I doing something wrong here or is building -current on -stable broken?
 
Seems to work OK here; xcalloc() and xmalloc() are defined in mem.c.


Cheers,
-- 
Ruslan Ermilov  Sysadmin and DBA,
[EMAIL PROTECTED]   Sunbay Software AG,
[EMAIL PROTECTED]  FreeBSD committer,
+380.652.512.251Simferopol, Ukraine

http://www.FreeBSD.org  The Power To Serve
http://www.oracle.com   Enabling The Information Age



msg37842/pgp0.pgp
Description: PGP signature