subject:"Building Current"

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"

Building -CURRENT on -STABLE

2020-01-09 Thread Gordon Bergling

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"

building current with meta mode

2018-03-03 Thread Eitan Adler

#make toolchain

...
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

-- 
Eitan Adler
___
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"

Building Current

2017-03-04 Thread Roberto Rodriguez Jr

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"

Error building -CURRENT from 10.1

2015-06-03 Thread Jonathan Anderson

Hi all,

I’m attempting to `make buildworld` from a 10.1-RELEASE box, and I’m 
encountering an error in the “bootstrap tools stage. It looks like gzip, which 
is part of the bootstrap tools, depends on `futimens` from a newish (since 
February?) libc / syscall API:

$ make buildworld
[...]
usr.bin/gzip/gzip.c:1103:6: warning: implicit declaration of function 
'futimens' is invalid in C99 [-Wimplicit-function-declaration]
if (futimens(fd, times)  0)
^
1 warning generated.
gzip.o: In function `copymodes':
usr.bin/gzip/gzip.c:(.text+0x2240): undefined reference to `futimens’


But we haven’t built the new libc yet:

$ grep ‘===’ build.log  do_some_manual_compression
=== tools/build (obj,includes,depend,all,install)
=== lib/clang/libllvm{support,tablegen} (obj,depend,all,install)
=== usr.bin/clang/[clang-]tblgen (obj,depend,all,install)
=== kerberos5/[stuff] (obj,depend,all,install)
=== usr.bin/compile_et (obj,depend,all,install)
=== lib/libelf (obj,depend,all,install)
=== lib/libdwarf (obj,depend,all,install)
=== cddl/usr.bin/sgsmsg (obj,depend,all,install)
=== cddl/lib/libctf (obj,depend,all,install)
=== cddl/usr.bin/ctf{convert,merge} (obj,depend,all,install)
=== games/fortune/strfile (obj,depend,all,install)
=== gnu/usr.bin/gperf (obj,depend,all,install)
=== gnu/usr.bin/groff (obj,depend,all,install)
=== usr.bin/soelim (obj,depend,all,install)
=== gnu/usr.bin/dtc (obj,depend,all,install)
=== usr.bin/lorder (obj,depend,all,install)
=== lib/libohash (obj,depend,all,install)
=== lib/libsqlite3 (obj,depend,all,install)
=== usr.bin/mandoc (obj,depend,all,install)
=== usr.bin/gzip (obj,depend,all,install)

So, how do I bootstrap 11-CURRENT from 10.1-RELEASE? Could there be something 
wrong with my specific environment? I don’t have any /etc/make.conf or 
/etc/src.conf.

Thanks,


Jon
—
jonat...@freebsd.org
___
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: Error building -CURRENT from 10.1

2015-06-03 Thread Jonathan Anderson

 
 On Jun 3, 2015, at 12:35 PM, Steve Kargl s...@troutmask.apl.washington.edu 
 wrote:
 
 On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote:
 
 So, how do I bootstrap 11-CURRENT from 10.1-RELEASE?
 
 
 Update your source tree.

My source tree is up-to-date as of a few hours ago.


Jon
--
jonat...@freebsd.org
___
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: Error building -CURRENT from 10.1

2015-06-03 Thread Steve Kargl

On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote:
 
 So, how do I bootstrap 11-CURRENT from 10.1-RELEASE?
 

Update your source tree.

-- 
Steve
___
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: Error building -CURRENT from 10.1

2015-06-03 Thread Baptiste Daroussin

On Wed, Jun 03, 2015 at 12:42:13PM -0230, Jonathan Anderson wrote:
  
  On Jun 3, 2015, at 12:35 PM, Steve Kargl 
  s...@troutmask.apl.washington.edu wrote:
  
  On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote:
  
  So, how do I bootstrap 11-CURRENT from 10.1-RELEASE?
  
  
  Update your source tree.
 
 My source tree is up-to-date as of a few hours ago.

Update it again :)

Best regards,
Bapt


pgpSXVy8cjKUj.pgp
Description: PGP signature

Re: Error building -CURRENT from 10.1

2015-06-03 Thread Jonathan Anderson

 
 On Jun 3, 2015, at 12:44 PM, Baptiste Daroussin b...@freebsd.org wrote:
 
 On Wed, Jun 03, 2015 at 12:42:13PM -0230, Jonathan Anderson wrote:
 
 On Jun 3, 2015, at 12:35 PM, Steve Kargl 
 s...@troutmask.apl.washington.edu wrote:
 
 On Wed, Jun 03, 2015 at 12:29:12PM -0230, Jonathan Anderson wrote:
 
 So, how do I bootstrap 11-CURRENT from 10.1-RELEASE?
 
 
 Update your source tree.
 
 My source tree is up-to-date as of a few hours ago.
 
 Update it again :)
 
 Best regards,
 Bapt


Ah, I see... *really* update. :)

Sorry Steve, I guess I’m not used to moving at the speed of -CURRENT!


Jon
--
jonat...@freebsd.org
___
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-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: problem building -current

2013-05-13 Thread Dimitry Andric

On May 7, 2013, at 16:10, Dimitry Andric d...@freebsd.org wrote:
 On 2013-05-07 16:01, Sergey Kandaurov wrote:
 On 7 May 2013 17:21, Michael W. Lucas mwlu...@michaelwlucas.com wrote:
 ...
 c++  -O2 -pipe 
 -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include 
 -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include
  -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. 
 -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
  -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS 
 -D__STDC_CONSTANT_MACROS -fno-strict-aliasing 
 -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd10.0\ 
 -DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\\ 
 -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c 
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp
  -o Process.o
 In file included from 
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp:85:
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:
  In member function 'virtual llvm::sys::TimeValue 
 llvm::sys::self_process::get_user_time() const':
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:75:
  error: 'CLOCK_PROCESS_CPUTIME_ID' was not declared in this scope
...
 Yes, this is an annoying problem.  When the CLOCK_PROCESS_CPUTIME_ID
 support was originally added, it was only put in sys/time.h, not in
 time.h.  So any application that includes the latter will not be able to
 use the define.

I have added a workaround (ugly, but functional :) in r250616.

-Dimitry

___
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

problem building -current

2013-05-07 Thread Michael W. Lucas


Hi,

I'm running an older -current:

bewilderbeast/usr/src;uname -a
FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT 
#15: Thu Nov  8 14:02:45 EST 2012 
mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/G

Trying to build new, and get:

...
c++  -O2 -pipe 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
 -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -fno-strict-aliasing 
-DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd10.0\ 
-DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\\ 
-I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c 
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/PluginLoader.cpp
 -o PluginLoader.o
c++  -O2 -pipe 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
 -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -fno-strict-aliasing 
-DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd10.0\ 
-DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\\ 
-I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c 
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/PrettyStackTrace.cpp
 -o PrettyStackTrace.o
c++  -O2 -pipe 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
 -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS 
-D__STDC_CONSTANT_MACROS -fno-strict-aliasing 
-DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd10.0\ 
-DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\\ 
-I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c 
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp 
-o Process.o
In file included from 
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp:85:
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:
 In member function 'virtual llvm::sys::TimeValue 
llvm::sys::self_process::get_user_time() const':
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:75:
 error: 'CLOCK_PROCESS_CPUTIME_ID' was not declared in this scope
*** [Process.o] Error code 1

Stop in /usr/src/lib/clang/libllvmsupport.
*** [bootstrap-tools] Error code 1

Stop in /usr/src.
*** [_bootstrap-tools] Error code 1

Stop in /usr/src.
*** [buildworld] Error code 1

Stop in /usr/src.

/etc/src.conf:
SENDMAIL_MC=/etc/mail/bwb.mc
WITHOUT_BIND=YES

SENDMAIL_MC=/etc/mail/bwb.mc
PERL_VERSION=5.10.1
WITHOUT_PKGNG=yes
# added by use.perl 2012-11-15 11:47:34
PERL_VERSION=5.14.2

I don't see any references to this error anywhere in the FreeBSD
lists. Any ideas how to get past it? Or should I just upgrade from
snapshot and try again?

Thanks,
==ml

-- 
Michael W. Lucas  -  mwlu...@michaelwlucas.com, Twitter @mwlauthor 
http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/
Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e
coupon code ILUVMICHAEL gets you 30% off  helps me.
___
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: problem building -current

2013-05-07 Thread Sergey Kandaurov

On 7 May 2013 17:21, Michael W. Lucas mwlu...@michaelwlucas.com wrote:

 Hi,

 I'm running an older -current:

 bewilderbeast/usr/src;uname -a
 FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT 
 #15: Thu Nov  8 14:02:45 EST 2012 
 mwlu...@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/G

 Trying to build new, and get:

 ...
 c++  -O2 -pipe 
 -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include 
 -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include 
 -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. 
 -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include
  -DLLVM_ON_UNIX -DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS 
 -D__STDC_CONSTANT_MACROS -fno-strict-aliasing 
 -DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd10.0\ 
 -DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\\ 
 -I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c 
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp
  -o Process.o
 In file included from 
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp:85:
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:
  In member function 'virtual llvm::sys::TimeValue 
 llvm::sys::self_process::get_user_time() const':
 /usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:75:
  error: 'CLOCK_PROCESS_CPUTIME_ID' was not declared in this scope
 *** [Process.o] Error code 1

You can try to install this change into your /usr/include/time.h and try again.
http://svnweb.freebsd.org/base?view=revisionrevision=245428

--- head/include/time.h 2013/01/14 17:41:04 245427
+++ head/include/time.h 2013/01/14 18:01:19 245428
@@ -112,6 +112,7 @@
 #define CLOCK_MONOTONIC_FAST   12  /* FreeBSD-specific. */
 #define CLOCK_SECOND   13  /* FreeBSD-specific. */
 #define CLOCK_THREAD_CPUTIME_ID14
+#defineCLOCK_PROCESS_CPUTIME_ID15
 #endif /* !defined(CLOCK_REALTIME)  __POSIX_VISIBLE = 200112 */

 #if !defined(TIMER_ABSTIME)  __POSIX_VISIBLE = 200112

-- 
wbr,
pluknet
___
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: problem building -current

2013-05-07 Thread Dimitry Andric


On 2013-05-07 16:01, Sergey Kandaurov wrote:

On 7 May 2013 17:21, Michael W. Lucas mwlu...@michaelwlucas.com wrote:

...

c++  -O2 -pipe -I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/tools/clang/include 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support -I. 
-I/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/../../lib/clang/include -DLLVM_ON_UNIX 
-DLLVM_ON_FREEBSD -D__STDC_LIMIT_MACROS -D__STDC_CONSTANT_MACROS -fno-strict-aliasing 
-DLLVM_DEFAULT_TARGET_TRIPLE=\x86_64-unknown-freebsd10.0\ 
-DLLVM_HOSTTRIPLE=\x86_64-unknown-freebsd10.0\ -DDEFAULT_SYSROOT=\\ 
-I/usr/obj/usr/src/tmp/legacy/usr/include -fno-exceptions -fno-rtti -c 
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp -o Process.o
In file included from 
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Process.cpp:85:
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:
 In member function 'virtual llvm::sys::TimeValue 
llvm::sys::self_process::get_user_time() const':
/usr/src/lib/clang/libllvmsupport/../../../contrib/llvm/lib/Support/Unix/Process.inc:75:
 error: 'CLOCK_PROCESS_CPUTIME_ID' was not declared in this scope
*** [Process.o] Error code 1


You can try to install this change into your /usr/include/time.h and try again.
http://svnweb.freebsd.org/base?view=revisionrevision=245428

--- head/include/time.h 2013/01/14 17:41:04 245427
+++ head/include/time.h 2013/01/14 18:01:19 245428
@@ -112,6 +112,7 @@
  #define CLOCK_MONOTONIC_FAST  12  /* FreeBSD-specific. */
  #define CLOCK_SECOND  13  /* FreeBSD-specific. */
  #define CLOCK_THREAD_CPUTIME_ID   14
+#defineCLOCK_PROCESS_CPUTIME_ID15
  #endif /* !defined(CLOCK_REALTIME)  __POSIX_VISIBLE = 200112 */

  #if !defined(TIMER_ABSTIME)  __POSIX_VISIBLE = 200112


Yes, this is an annoying problem.  When the CLOCK_PROCESS_CPUTIME_ID
support was originally added, it was only put in sys/time.h, not in
time.h.  So any application that includes the latter will not be able to
use the define.

There are multiple possibilities to solve this, but I'm thinking of
putting a -DCLOCK_PROCESS_CPUTIME_ID=15 on the command line for older
versions of -current...

-Dimitry
___
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

Problem building current

2011-12-05 Thread Alexander Yerenkow

Hello.
I think I have some problem building current on my system (which is not
current).
# uname -a
FreeBSD 9.0-RC1 FreeBSD 9.0-RC1 #0: Tue Oct 18 18:51:43 UTC 2011
r...@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64
# pwd
/zpool0/testenv/sources/10-kms/lib/libc

# svn info
Path: .
Working Copy Root Path: /zpool0/testenv/sources/10-kms
URL: http://svn.freebsd.org/base/head/lib/libc
Repository Root: http://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 228276
Node Kind: directory
Schedule: normal
Last Changed Author: jilles
Last Changed Rev: 228269
Last Changed Date: 2011-12-05 02:00:47 +0200 (пн, 05 дек 2011)

# make -DNO_CCACHE
cc -O2 -pipe -I/zpool0/testenv/sources/10-kms/lib/libc/include
-I/zpool0/testenv/sources/10-kms/lib/libc/../../include
-I/zpool0/testenv/sources/10-kms/lib/libc/amd64 -DNLS
-D__DBINTERFACE_PRIVATE
-I/zpool0/testenv/sources/10-kms/lib/libc/../../contrib/gdtoa -DINET6
-I/usr/obj/zpool0/testenv/sources/10-kms/lib/libc
-I/zpool0/testenv/sources/10-kms/lib/libc/resolv -D_ACL_PRIVATE
-DPOSIX_MISTAKE
-I/zpool0/testenv/sources/10-kms/lib/libc/../../contrib/tzcode/stdtime
-I/zpool0/testenv/sources/10-kms/lib/libc/stdtime
-I/zpool0/testenv/sources/10-kms/lib/libc/locale -DBROKEN_DES -DPORTMAP
-DDES_BUILTIN -I/zpool0/testenv/sources/10-kms/lib/libc/rpc -DYP
-DNS_CACHING -DSYMBOL_VERSIONING -std=gnu99 -fstack-protector
-Wsystem-headers -Werror -Wall -Wno-format-y2k -Wno-uninitialized
-Wno-pointer-sign -c
/zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c
/zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c: In function
'sctp_opt_info':
/zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:416: error:
'SCTP_REMOTE_UDP_ENCAPS_PORT' undeclared (first use in this function)
/zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:416: error:
(Each undeclared identifier is reported only once
/zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:416: error:
for each function it appears in.)
/zpool0/testenv/sources/10-kms/lib/libc/net/sctp_sys_calls.c:417: error:
dereferencing pointer to incomplete type
*** Error code 1


I'm getting this error when I'm trying to buildworld from svn checkouted
sources (e.g. I'm using plain make buildworld, without NO_CLEAN or some
else).

Any ideas why it is happening?
-- 
Regards,
Alexander Yerenkow
___
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

Installworld fails building Current from 4.7-R

2002-10-24 Thread Richard Cotrina

Hello :

I am getting an strange error when trying to install current ( make
installworld ). I cvsup-ed it in my 4.7- Release box, and I sompiling the
sources and the kernel without any error messages :

# make -j4 buildworld
# make buildkernel
# make installkernel
# reboot

All the above finished without problems. After rebooting, I tried to do :

# make installworld

and after a while, it finished with the following error :

== usr.bin/chpass
[ ! -e /usr/bin/chpass ] || chflags noschg /usr/bin/chpass || true
*** Signal 12

Stop in /usr/src/usr.bin/chpass.
*** Error Code 1

And the console gave me this message :

/kernel pid 21078 (sh),uid 0 : exited on signal 12 ( core dumped )

Does anyone have any ideas about what I did it wrong or it is missing ?

Thanks in advance for your help

Richard Cotrina


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

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Craig Rodrigues

Hi,

Did you see the instructions in /usr/src/Makefile and /usr/src/UPDATING?

This is from /usr/src/Makefile:

# For individuals wanting to upgrade their sources (even if only a
# delta of a few days):
#
# 1.  `cd /usr/src'   (or to the directory containing your source tree).
# 2.  `make buildworld'
# 3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is GENERIC).
# 4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is GENERIC).
# 5.  `reboot'(in single user mode: boot -s from the loader prompt).
# 6.  `mergemaster -p'
# 7.  `make installworld'
# 8.  `mergemaster'
# 9.  `reboot'
#
# See src/UPDATING `COMMON ITEMS' for more complete information.
#

-- 
Craig Rodrigues
http://www.gis.net/~craigr
[EMAIL PROTECTED]

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

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Richard Cotrina

Yes, I did. However make installworld fails as I said.

- Original Message -
From: Craig Rodrigues [EMAIL PROTECTED]
To: Richard Cotrina [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Sent: Thursday, October 24, 2002 5:02 PM
Subject: Re: Installworld fails building Current from 4.7-R

 Hi,

 Did you see the instructions in /usr/src/Makefile and /usr/src/UPDATING?

 This is from /usr/src/Makefile:

 # For individuals wanting to upgrade their sources (even if only a
 # delta of a few days):
 #
 # 1.  `cd /usr/src'   (or to the directory containing your source
tree).
 # 2.  `make buildworld'
 # 3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE' (default is
GENERIC).
 # 4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is
GENERIC).
 # 5.  `reboot'(in single user mode: boot -s from the loader
prompt).
 # 6.  `mergemaster -p'
 # 7.  `make installworld'
 # 8.  `mergemaster'
 # 9.  `reboot'
 #
 # See src/UPDATING `COMMON ITEMS' for more complete information.
 #

 --
 Craig Rodrigues
 http://www.gis.net/~craigr
 [EMAIL PROTECTED]

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

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

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Mike Hunter



On Thu, 24 Oct 2002, Richard Cotrina wrote:

 Yes, I did. However make installworld fails as I said.

I ran into the same problem going from 4.6 to 5.0-CURRENT.

We used truss to see that sh was making funny calls, and concluded that
we'd need to run from the kernel to get it working.  We installed the
new kernel and were able to complete the install.

Definitely not knowledgeable enough to be posting to freebsd-current,

Mike Hunter


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

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Nate Lawson

On Thu, 24 Oct 2002, Mike Hunter wrote:
 On Thu, 24 Oct 2002, Richard Cotrina wrote:
 
  Yes, I did. However make installworld fails as I said.
 
 I ran into the same problem going from 4.6 to 5.0-CURRENT.
 
 We used truss to see that sh was making funny calls, and concluded that
 we'd need to run from the kernel to get it working.  We installed the
 new kernel and were able to complete the install.
 
 Definitely not knowledgeable enough to be posting to freebsd-current,
 
 Mike Hunter

That's why there is a reboot between installing the new kernel and doing
installworld.  You need to run the new kernel to have the ABI match.

-Nate


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

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread Nate Lawson

[Redirected to current@ with sender's approval]

On Thu, 24 Oct 2002, Mike Hunter wrote:
 On Thu, 24 Oct 2002, Nate Lawson wrote:
 
  That's why there is a reboot between installing the new kernel and doing
  installworld.  You need to run the new kernel to have the ABI match.
 
 From my understanding of what was written earlier today (and what the guy
 who was helping me said) the boot loader is not updated during that first
 reboot, and therefore the old kernel is booted on that reboot.
 5.0-current moves the default location of the kernel IIRC.
 
 I'm pretty sure that I followed the UPDATING directions to the letter.
 
 Mike

I've run into the same problem in the past but manually selected the new
kernel.  Should we add the explicit step that you need to load
/boot/kernel/kernel when upgrading?  Or has that been fixed?

-Nate


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

Re: Installworld fails building Current from 4.7-R

2002-10-24 Thread The Gupta Age


|
|I've run into the same problem in the past but manually selected the new
|kernel.  Should we add the explicit step that you need to load
|/boot/kernel/kernel when upgrading?  Or has that been fixed?
|
|-Nate

I have posted atleast twice on current to add this
info to UPDATING. guess it still hasnt been done.


Saurabh Gupta


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

building -CURRENT on RELENG_4

2002-10-22 Thread Max Khon

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 ---

/fjoe


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 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

Building -CURRENT with 4.5-RELEASE

2002-10-21 Thread Gerhard Haering

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

-- Gerhard

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-25 Thread Giorgos Keramidas


On 2002-09-24 18:00, Lars Eggert [EMAIL PROTECTED] wrote:
 Alexander Kabaev wrote:
 On Tue, 24 Sep 2002 00:00:45 -0700
 Crist J. Clark [EMAIL PROTECTED] wrote:
 
 Not too sure about that. Now I'm getting SIGSEGV again,
 
 You are right. There was a stupid mistake in the latest version, sorry.
 Could you try yet another patch?
 
 http://people.freebsd.org/~kan/gcc-cpp.diff

 FYI, I saw the same error as Crist when building -current under 4.6,
 and with your patch, the buildworld/buildkernel succeeded.

Ditto.  I have managed to build a current world on RELENG_4 only with
Alexander's patch.

-- 
FreeBSD: The power to Serve -- http://www.FreeBSD.org
FreeBSD 5.0-CURRENT #0: Tue Sep 24 04:56:12 EEST 2002

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-25 Thread Crist J. Clark


On Tue, Sep 24, 2002 at 06:13:33PM -0400, Alexander Kabaev wrote:
  Nope, still getting it.
 
 I was able to reproduce the crash with your config file and unpatched
 GCC, however crash does not happen when I use the patch. Are you using
 make buildkernel or old config/make method? 

Since I'm building a CURRENT kernel on a STABLE box, I think
buildkernel is the only practical choice.

With the latest patch, today's automated build ran fine. Thanks. 
-- 
Crist J. Clark | [EMAIL PROTECTED]
   | [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Crist J. Clark


On Mon, Sep 23, 2002 at 03:59:46PM -0400, Alexander Kabaev wrote:
 On Mon, 23 Sep 2002 12:55:49 -0700
 Crist J. Clark [EMAIL PROTECTED] wrote:
 
  It seems to have worked. Thanks.
 
 Sorry for inconvenience, but could you please check that you got the
 latest version of the patch. Both versions will fix the bug, but the
 version I copied on freefall several hours ago appears to be more
 correct.

Not too sure about that. Now I'm getting SIGSEGV again,

  make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES |  MKDEP_CPP=cc -E 
CC=cc xargs mkdep -a -f .newdep -O -pipe -march=pentium3 -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
-Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. -I/usr/src.CURRENT/sys 
-I/usr/src.CURRENT/sys/dev -I/usr/src.CURRENT/sys/contrib/dev/acpica 
-I/usr/src.CURRENT/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common  
-mpreferred-stack-boundary=2 -ffreestanding
  cc: Internal error: Segmentation fault (program cpp0)
 Please submit a full bug report.
  See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
  mkdep: compile failed
  *** Error code 1

  Stop in /home/cjc/obj/usr/src.CURRENT/sys/GOKU.
  *** Error code 1

  Stop in /home/cjc/obj/usr/src.CURRENT/sys/GOKU.
  *** Error code 1

  Stop in /usr/src.CURRENT.
  *** Error code 1

  Stop in /usr/src.CURRENT.

And I had this patch,

  $ cvs diff cppmacro.c
  Index: cppmacro.c
  ===
  RCS file: /export/freebsd/ncvs/src/contrib/gcc/cppmacro.c,v
  retrieving revision 1.1.1.4
  diff -u -r1.1.1.4 cppmacro.c
  --- cppmacro.c  1 Sep 2002 20:37:29 -   1.1.1.4
  +++ cppmacro.c  23 Sep 2002 20:39:38 -
  @@ -349,6 +349,8 @@
 
 /* Commit the memory, including NUL, and return the token.  */
 len = dest - BUFF_FRONT (pfile-u_buff);
  +  if ((size_t) (BUFF_LIMIT (pfile-u_buff) - dest)  1)
  +_cpp_extend_buff (pfile, pfile-u_buff, 1);
 BUFF_FRONT (pfile-u_buff) = dest + 1;
 return new_string_token (pfile, dest - len, len);
   }

For the buildworld and buildkernel.
-- 
Crist J. Clark | [EMAIL PROTECTED]
   | [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Alexander Kabaev


On Tue, 24 Sep 2002 00:00:45 -0700
Crist J. Clark [EMAIL PROTECTED] wrote:

 Not too sure about that. Now I'm getting SIGSEGV again,

You are right. There was a stupid mistake in the latest version, sorry.
Could you try yet another patch?

http://people.freebsd.org/~kan/gcc-cpp.diff

-- 
Alexander Kabaev

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Crist J. Clark


On Tue, Sep 24, 2002 at 11:43:22AM -0400, Alexander Kabaev wrote:
 On Tue, 24 Sep 2002 00:00:45 -0700
 Crist J. Clark [EMAIL PROTECTED] wrote:
 
  Not too sure about that. Now I'm getting SIGSEGV again,
 
 You are right. There was a stupid mistake in the latest version, sorry.
 Could you try yet another patch?
 
 http://people.freebsd.org/~kan/gcc-cpp.diff

Nope, still getting it.

As for your other question about the configuration, it looks like
it's,

  options   IPSEC_ESP

That is killing it. If I comment out that option, I get past that
initial mkdep.

The whole configuration is attached.
-- 
Crist J. Clark | [EMAIL PROTECTED]
   | [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]


#
# $Id: GOKU,v 1.7 2002/07/30 07:50:02 cjc Exp cjc $
#

machine i386
cpu I686_CPU
ident   GOKU
maxusers0

#makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols

options INET#InterNETworking
options INET6   #IPv6 communications protocols
options IPSEC   #IP security
options IPSEC_ESP   #IP security (crypto; define w/ IPSEC)
options FFS #Berkeley Fast Filesystem
options COMPAT_43   #Compatible with BSD 4.3 [KEEP THIS!]
options KTRACE  #ktrace(1) support
options SYSVSHM #SYSV-style shared memory
options SYSVMSG #SYSV-style message queues
options SYSVSEM #SYSV-style semaphores
options P1003_1B#Posix P1003_1B real-time extentions
options _KPOSIX_PRIORITY_SCHEDULING
options SOFTUPDATES

device  isa
device  pci

options IPFIREWALL  #firewall
options IPFIREWALL_VERBOSE  #enable logging to syslogd(8)
options IPFIREWALL_FORWARD  #enable transparent proxy support
options IPFIREWALL_VERBOSE_LIMIT=100#limit verbosity
options IPV6FIREWALL#firewall for IPv6
options IPV6FIREWALL_VERBOSE
options IPV6FIREWALL_VERBOSE_LIMIT=100
options IPDIVERT#divert sockets
#optionsIPFILTER#ipfilter support
#optionsIPFILTER_LOG#ipfilter logging
#optionsIPFILTER_DEFAULT_BLOCK  #block all packets by default

device  fdc

# ATA and ATAPI devices
device  ata
device  atadisk # ATA disk drives
device  atapicd # ATAPI CDROM drives

# Floating point support - do not disable.
device  npx

# Power management support
#device apm

# Serial (COM) ports
device  sio

# Parallel port
device  ppc
device  ppbus   # Parallel port bus (required)
device  lpt # Printer
device  plip# TCP/IP over parallel
device  ppi # Parallel port interface device

# PCI Ethernet NICs.
device  miibus
device  xl  # 3Com 3c90x (``Boomerang'', ``Cyclone'')

# Pseudo devices - the number indicates how many units to allocated.
device  random  # Entropy device
device  loop# Network loopback
device  ether   # Ethernet support
device  tun # Packet tunnel.
device  pty # ttys (telnet etc)
device  md  # Memory disks
device  gif # IPv6 and IPv4 tunneling
device  faith   # IPv6-to-IPv4 relaying (translation)

# The `bpf' device enables the Berkeley Packet Filter.
# Be aware of the administrative consequences of enabling this!
device  bpf #Berkeley packet filter

# Give sound a shot
device  pcm

# USB device
device  usb

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Alexander Kabaev


 Nope, still getting it.

I was able to reproduce the crash with your config file and unpatched
GCC, however crash does not happen when I use the patch. Are you using
make buildkernel or old config/make method? 
 
 
   options IPSEC_ESP
 
 That is killing it. If I comment out that option, I get past that
 initial mkdep.

By adding or removing configuration options, you change the exact layout
of the string buffer in CPP0 and this prevents crash from happening.

-- 
Alexander Kabaev

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-24 Thread Lars Eggert


Alexander Kabaev wrote:
 On Tue, 24 Sep 2002 00:00:45 -0700
 Crist J. Clark [EMAIL PROTECTED] wrote:
 
Not too sure about that. Now I'm getting SIGSEGV again,
 
 You are right. There was a stupid mistake in the latest version, sorry.
 Could you try yet another patch?
 
 http://people.freebsd.org/~kan/gcc-cpp.diff

FYI, I saw the same error as Crist when building -current under 4.6, and 
with your patch, the buildworld/buildkernel succeeded.

Lars
-- 
Lars Eggert [EMAIL PROTECTED]   USC Information Sciences Institute



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-23 Thread Crist J. Clark


On Sun, Sep 22, 2002 at 11:09:56PM -0400, Alexander Kabaev wrote:
 I am asking people having CPP0 dying with SIG11 to try the patch at URL
 below. Success/failure reports are appreciated.
 
 http://people.freebsd.org/~kan/gcc-cpp.diff

It seems to have worked. Thanks.
-- 
Crist J. Clark | [EMAIL PROTECTED]
   | [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/| [EMAIL PROTECTED]

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-23 Thread Alexander Kabaev


On Mon, 23 Sep 2002 12:55:49 -0700
Crist J. Clark [EMAIL PROTECTED] wrote:

 It seems to have worked. Thanks.

Sorry for inconvenience, but could you please check that you got the
latest version of the patch. Both versions will fix the bug, but the
version I copied on freefall several hours ago appears to be more
correct.

-- 
Alexander Kabaev

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

Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Crist J. Clark


I've been unable to build CURRENT on STABLE for a few days. I made
sure to bring STABLE up to date. Is this just me? Is there a problem
with building CURRENT on STABLE at the moment?

 --
  Kernel build for GOKU started on Sat Sep 21 23:48:02 PDT 2002
 --
 === GOKU
 mkdir -p /home/cjc/obj/usr/src.CURRENT/sys
 cd /usr/src.CURRENT/sys/i386/conf;  
PATH=/home/cjc/obj/usr/src.CURRENT/i386/usr/sbin:/home/cjc/obj/usr/src.CURRENT/i386/usr/bin:/home/cjc/obj/usr/src.CURRENT/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
  config  -d /home/cjc/obj/usr/src.CURRENT/sys/GOKU  
/usr/src.CURRENT/sys/i386/conf/GOKU
 Kernel build directory is /home/cjc/obj/usr/src.CURRENT/sys/GOKU
 Don't forget to do a ``make depend''
 cd /home/cjc/obj/usr/src.CURRENT/sys/GOKU;  
MAKESRCPATH=/usr/src.CURRENT/sys/dev/aic7xxx/aicasm  make -DNO_CPU_CFLAGS -f 
/usr/src.CURRENT/sys/dev/aic7xxx/aicasm/Makefile
 Warning: Object directory not changed from original 
/home/cjc/obj/usr/src.CURRENT/sys/GOKU
 cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src.CURRENT/sys/dev/aic7xxx/aicasm
-c /usr/src.CURRENT/sys/dev/aic7xxx/aicasm/aicasm.c
 cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src.CURRENT/sys/dev/aic7xxx/aicasm
-c /usr/src.CURRENT/sys/dev/aic7xxx/aicasm/aicasm_symbol.c
 yacc -b aicasm_gram  -d -o aicasm_gram.c 
/usr/src.CURRENT/sys/dev/aic7xxx/aicasm/aicasm_gram.y
 cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src.CURRENT/sys/dev/aic7xxx/aicasm
-c aicasm_gram.c
 yacc -b aicasm_macro_gram -p mm -d -o aicasm_macro_gram.c 
/usr/src.CURRENT/sys/dev/aic7xxx/aicasm/aicasm_macro_gram.y
 cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src.CURRENT/sys/dev/aic7xxx/aicasm
-c aicasm_macro_gram.c
 lex -t   /usr/src.CURRENT/sys/dev/aic7xxx/aicasm/aicasm_scan.l  aicasm_scan.c
 cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src.CURRENT/sys/dev/aic7xxx/aicasm
-c aicasm_scan.c
 lex -t  -Pmm /usr/src.CURRENT/sys/dev/aic7xxx/aicasm/aicasm_macro_scan.l  
aicasm_macro_scan.c
 cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src.CURRENT/sys/dev/aic7xxx/aicasm
-c aicasm_macro_scan.c
 cc -O -pipe -nostdinc -I/usr/include -I. -I/usr/src.CURRENT/sys/dev/aic7xxx/aicasm
 -o aicasm aicasm.o aicasm_symbol.o aicasm_gram.o aicasm_macro_gram.o aicasm_scan.o 
aicasm_macro_scan.o -ll
 cd /home/cjc/obj/usr/src.CURRENT/sys/GOKU;  MAKEOBJDIRPREFIX=/home/cjc/obj  
MACHINE_ARCH=i386  MACHINE=i386  CPUTYPE=p3  
GROFF_BIN_PATH=/home/cjc/obj/usr/src.CURRENT/i386/usr/bin  
GROFF_FONT_PATH=/home/cjc/obj/usr/src.CURRENT/i386/usr/share/groff_font  
GROFF_TMAC_PATH=/home/cjc/obj/usr/src.CURRENT/i386/usr/share/tmac  
DESTDIR=/home/cjc/obj/usr/src.CURRENT/i386  INSTALL=sh 
/usr/src.CURRENT/tools/install.sh  
PATH=/home/cjc/obj/usr/src.CURRENT/i386/usr/sbin:/home/cjc/obj/usr/src.CURRENT/i386/usr/bin:/home/cjc/obj/usr/src.CURRENT/i386/usr/games:/sbin:/bin:/usr/sbin:/usr/bin
 make KERNEL=kernel depend
 rm -f .olddep
 if [ -f .depend ]; then mv .depend .olddep; fi
 make _kernel-depend
 cc -c -O -pipe -march=pentium3 -Wall -Wredundant-decls -Wnested-externs 
-Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual 
-fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src.CURRENT/sys 
-I/usr/src.CURRENT/sys/dev -I/usr/src.CURRENT/sys/contrib/dev/acpica 
-I/usr/src.CURRENT/sys/contrib/ipfilter -D_KERNEL -include opt_global.h 
-mpreferred-stack-boundary=2 -ffreestanding /usr/src.CURRENT/sys/i386/i386/genassym.c
 NM=nm sh /usr/src.CURRENT/sys/kern/genassym.sh genassym.o  assym.s
 awk -f /usr/src.CURRENT/sys/tools/vnode_if.awk /usr/src.CURRENT/sys/kern/vnode_if.src 
-h
 echo '#define NBPF 1'  bpf.h
 awk -f /usr/src.CURRENT/sys/tools/vnode_if.awk /usr/src.CURRENT/sys/kern/vnode_if.src 
-c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/kern/device_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk /usr/src.CURRENT/sys/kern/bus_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/kern/linker_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/mii/miibus_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/pccard/card_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/pccard/power_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/pci/pci_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/pci/pcib_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/ppbus/ppbus_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/sound/pcm/ac97_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/sound/pcm/channel_if.m -c
 awk -f /usr/src.CURRENT/sys/tools/makeobjops.awk 
/usr/src.CURRENT/sys/dev/sound/pcm/feeder_if.m -c
 awk -f /usr/src.CURRENT

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Maxim Konovalov



Works for me:

 Kernel build for GENERIC completed on Sun Sep 22 07:43:35 MSD 2002

$ uname -a
FreeBSD golf.macomnet.net 4.6-20020805-MACOMNET-STABLE FreeBSD
4.6-20020805-MACOMNET-STABLE #19: Fri Sep 20 17:09:52 MSD 2002
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GOLF  i386.

-- 
Maxim Konovalov, [EMAIL PROTECTED]




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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Giorgos Keramidas


On 2002-09-21 23:53, Crist J. Clark [EMAIL PROTECTED] wrote:
 I've been unable to build CURRENT on STABLE for a few days. I made
 sure to bring STABLE up to date. Is this just me? Is there a problem
 with building CURRENT on STABLE at the moment?

It isn't just you.  The same error stopped my build of current 2-3
days ago on 4.6-RELEASE.

  if [ -f .olddep ]; then mv .olddep .depend; fi
  rm -f .newdep
  make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES |  MKDEP_CPP=cc -E 
CC=cc xargs mkdep -a -f .newdep -O -pipe -march=pentium3 -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
-Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. -I/usr/src.CURRENT/sys 
-I/usr/src.CURRENT/sys/dev -I/usr/src.CURRENT/sys/contrib/dev/acpica 
-I/usr/src.CURRENT/sys/contrib/ipfilter -D_KERNEL -include opt_global.h -fno-common  
-mpreferred-stack-boundary=2 -ffreestanding
  cc: Internal error: Segmentation fault (program cpp0)
  Please submit a full bug report.
  See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
  mkdep: compile failed
  *** Error code 1

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread qhwt


On Sun, Sep 22, 2002 at 02:44:54PM +0300, Giorgos Keramidas wrote:
 On 2002-09-21 23:53, Crist J. Clark [EMAIL PROTECTED] wrote:
  I've been unable to build CURRENT on STABLE for a few days. I made
  sure to bring STABLE up to date. Is this just me? Is there a problem
  with building CURRENT on STABLE at the moment?
 
 It isn't just you.  The same error stopped my build of current 2-3
 days ago on 4.6-RELEASE.
 
   if [ -f .olddep ]; then mv .olddep .depend; fi
   rm -f .newdep
   make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES |  MKDEP_CPP=cc 
-E CC=cc xargs mkdep -a -f .newdep -O -pipe -march=pentium3 -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. 
-I/usr/src.CURRENT/sys -I/usr/src.CURRENT/sys/dev 
-I/usr/src.CURRENT/sys/contrib/dev/acpica -I/usr/src.CURRENT/sys/contrib/ipfilter 
-D_KERNEL -include opt_global.h -fno-common  -mpreferred-stack-boundary=2 
-ffreestanding
   cc: Internal error: Segmentation fault (program cpp0)
   Please submit a full bug report.
   See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
   mkdep: compile failed
   *** Error code 1

Try 'make depend  make' using cpp0 built from -CURRENT source
newer than the first import of gcc 3.2.1 prerelease:

$ pushd /usr/src/gnu/usr.bin/cc
$ make obj  make depend  make
$ popd
$ GCC_EXEC_PREFIX=/usr/obj/usr/src/usr.bin/cc/cpp0/ make depend
$ GCC_EXEC_PREFIX=/usr/obj/usr/src/usr.bin/cc/cpp0/ make

should work unless you are doing a cross-platform compiling.
The bug in cpp0 seems to me to have been fixed after the first
import of gcc 3.2.1-prerelease (2002-09-02(UTC)).

Cheers.

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread qhwt


On Sun, Sep 22, 2002 at 10:22:23PM +0900, I wrote:
 On Sun, Sep 22, 2002 at 02:44:54PM +0300, Giorgos Keramidas wrote:
  On 2002-09-21 23:53, Crist J. Clark [EMAIL PROTECTED] wrote:
   I've been unable to build CURRENT on STABLE for a few days. I made
   sure to bring STABLE up to date. Is this just me? Is there a problem
   with building CURRENT on STABLE at the moment?
  
  It isn't just you.  The same error stopped my build of current 2-3
  days ago on 4.6-RELEASE.
  
if [ -f .olddep ]; then mv .olddep .depend; fi
rm -f .newdep
make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES |  MKDEP_CPP=cc 
-E CC=cc xargs mkdep -a -f .newdep -O -pipe -march=pentium3 -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. 
-I/usr/src.CURRENT/sys -I/usr/src.CURRENT/sys/dev 
-I/usr/src.CURRENT/sys/contrib/dev/acpica -I/usr/src.CURRENT/sys/contrib/ipfilter 
-D_KERNEL -include opt_global.h -fno-common  -mpreferred-stack-boundary=2 
-ffreestanding
cc: Internal error: Segmentation fault (program cpp0)
Please submit a full bug report.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
mkdep: compile failed
*** Error code 1
 
 Try 'make depend  make' using cpp0 built from -CURRENT source
 newer than the first import of gcc 3.2.1 prerelease:
 
 $ pushd /usr/src/gnu/usr.bin/cc
 $ make obj  make depend  make
 $ popd
 $ GCC_EXEC_PREFIX=/usr/obj/usr/src/usr.bin/cc/cpp0/ make depend
 $ GCC_EXEC_PREFIX=/usr/obj/usr/src/usr.bin/cc/cpp0/ make
 
 should work unless you are doing a cross-platform compiling.
 The bug in cpp0 seems to me to have been fixed after the first
 import of gcc 3.2.1-prerelease (2002-09-02(UTC)).

Actually the bug seems to be not only in cpp0 but in some other tools
under /usr/libexec, so even if make depend succeeds, you'll get another
crash:

cc -c -O -pipe -march=pentiumpro -Wall -Wredundant-decls -Wnested-externs -Wstri
ct-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fform
at-extensions -ansi -g -nostdinc -I-  -I. -I/usr/src/sys -I/usr/src/sys/dev -I/u
sr/src/sys/contrib/dev/acpica -I/usr/src/sys/contrib/ipfilter -D_KERNEL -include
 opt_global.h -fno-common  -mpreferred-stack-boundary=2 -ffreestanding -Werror  
/usr/src/sys/netkey/keysock.c
In file included from /usr/src/sys/sys/systm.h:45,
 from /usr/src/sys/netkey/keysock.c:49:
machine/atomic.h: In function `atomic_set_long':
machine/atomic.h:253: internal error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
*** Error code 1

So I had to build the world in advance, and use the tools under
/usr/obj/usr/src/${ARCH}/usr/libexec/ .
Also, it seems like it doesn't crash without -march= option, so
NO_CPU_CFLAGS and NO_CPU_COPTFLAGS might help you.

Anyway, I just managed to build the kernel from 2002-09-21(UTC) source,
on another machine with world built from 2002-09-01(UTC).

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Jim Bloom




Giorgos Keramidas wrote:
 
 On 2002-09-21 23:53, Crist J. Clark [EMAIL PROTECTED] wrote:
  I've been unable to build CURRENT on STABLE for a few days. I made
  sure to bring STABLE up to date. Is this just me? Is there a problem
  with building CURRENT on STABLE at the moment?
 
 It isn't just you.  The same error stopped my build of current 2-3
 days ago on 4.6-RELEASE.
 
   if [ -f .olddep ]; then mv .olddep .depend; fi
   rm -f .newdep
   make -V CFILES -V SYSTEM_CFILES -V GEN_CFILES -V GEN_M_CFILES |  MKDEP_CPP=cc 
-E CC=cc xargs mkdep -a -f .newdep -O -pipe -march=pentium3 -Wall 
-Wredundant-decls -Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes 
-Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. 
-I/usr/src.CURRENT/sys -I/usr/src.CURRENT/sys/dev 
-I/usr/src.CURRENT/sys/contrib/dev/acpica -I/usr/src.CURRENT/sys/contrib/ipfilter 
-D_KERNEL -include opt_global.h -fno-common  -mpreferred-stack-boundary=2 
-ffreestanding
   cc: Internal error: Segmentation fault (program cpp0)
   Please submit a full bug report.
   See URL:http://www.gnu.org/software/gcc/bugs.html for instructions.
   mkdep: compile failed
   *** Error code 1
 

This is not just a problem with stable.  I had the same problem building a
kernel with Sept. 22, 7:30AM EDT cvsup of current source.  My machine is running
current from about a month ago.

Jim Bloom
[EMAIL PROTECTED]

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

Re: Trouble Building CURRENT on STABLE, cpp seg. fault

2002-09-22 Thread Alexander Kabaev


I am asking people having CPP0 dying with SIG11 to try the patch at URL
below. Success/failure reports are appreciated.

http://people.freebsd.org/~kan/gcc-cpp.diff

-- 
Alexander Kabaev


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

building -current on -stable broken?

2002-04-28 Thread Kenneth D. Merry



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?

Ken
-- 
Kenneth Merry
[EMAIL PROTECTED]

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

Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill


I think today is going to be one of those days  :-(

The first hint was after I built today's -STABLE, I then fired up a
cvs update against my -CURRENT sources, and got:

Script started on Wed Jan 30 05:12:16 2002
freebeast(4.5-STA)[1] cd /S4/usr/src  cvs update^M
cvs update: Updating .
cvs update: Updating bin
cvs update: Updating bin/cat
...
U etc/printcap
U etc/profile
U etc/protocols
cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e
tc/rc,v
freebeast(4.5-STA)[2] 

I looked around at the results from cvs log etc/rc and 1.293 was the
last revision I could see, so I don't know why it was trying to find
1.294.

I tried removing src/etc/rc  re-starting the cvs update, and the
process then seemed to go to completion without further incident.


I then re-booted the machine to run (yesterday's) -CURRENT, and started
the build process... which died rather soon.  Doing it again without -j8
showed:

 stage 2: cleaning up the object tree
--
...
=== lib/libc
/usr/src/share/mk/bsd.lib.mk, line 184: Inconsistent operator for libc.a
/usr/src/share/mk/bsd.lib.mk, line 192: Inconsistent operator for libc_p.a
/usr/src/share/mk/bsd.lib.mk, line 224: Inconsistent operator for libc_pic.a
make: fatal errors encountered -- cannot continue
*** Error code 1



Ummm...  OK; this doesn't look especially good.  bsd.lib.mk hasn't been
modified since 04 December, at revision 1.100 (bde).


I think I could use a bit of guidance at this point.

Thanks,
david
-- 
David H. Wolfskill  [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

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

Re: Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill


Date: Wed, 30 Jan 2002 05:58:24 -0800 (PST)
From: David Wolfskill [EMAIL PROTECTED]

cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e
tc/rc,v
freebeast(4.5-STA)[2] 

That, at least, did not occur on my laptop.


 stage 2: cleaning up the object tree
--
...
=== lib/libc
/usr/src/share/mk/bsd.lib.mk, line 184: Inconsistent operator for libc.a
/usr/src/share/mk/bsd.lib.mk, line 192: Inconsistent operator for libc_p.a
/usr/src/share/mk/bsd.lib.mk, line 224: Inconsistent operator for libc_pic.a
make: fatal errors encountered -- cannot continue
*** Error code 1

That, however, did.


Guidance, hints, etc. cheerfully accepted.  :-}

Thanks,
david (links to my resume at http://www.catwhisker.org/~david)
-- 
David H. Wolfskill  [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

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

Re: Weirdness in building -CURRENT today

2002-01-30 Thread Ruslan Ermilov


On Wed, Jan 30, 2002 at 06:33:43AM -0800, David Wolfskill wrote:
 Date: Wed, 30 Jan 2002 05:58:24 -0800 (PST)
 From: David Wolfskill [EMAIL PROTECTED]
 
 cvs [update aborted]: could not find desired version 1.294 in /cvs/freebsd/src/e
 tc/rc,v
 freebeast(4.5-STA)[2] 
 
 That, at least, did not occur on my laptop.
 
 
  stage 2: cleaning up the object tree
 --
 ...
 === lib/libc
 /usr/src/share/mk/bsd.lib.mk, line 184: Inconsistent operator for libc.a
 /usr/src/share/mk/bsd.lib.mk, line 192: Inconsistent operator for libc_p.a
 /usr/src/share/mk/bsd.lib.mk, line 224: Inconsistent operator for libc_pic.a
 make: fatal errors encountered -- cannot continue
 *** Error code 1
 
 That, however, did.
 
 
 Guidance, hints, etc. cheerfully accepted.  :-}
 
You probably have some locally modified src/ makefiles,
or some crap in /etc/make.conf.


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

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

Re: Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill

Date: Wed, 30 Jan 2002 17:02:07 +0200
From: Ruslan Ermilov [EMAIL PROTECTED]

  stage 2: cleaning up the object tree
 --
 ...
 === lib/libc
 /usr/src/share/mk/bsd.lib.mk, line 184: Inconsistent operator for libc.a
 /usr/src/share/mk/bsd.lib.mk, line 192: Inconsistent operator for libc_p.a
 /usr/src/share/mk/bsd.lib.mk, line 224: Inconsistent operator for libc_pic.a
 make: fatal errors encountered -- cannot continue
 *** Error code 1

You probably have some locally modified src/ makefiles,
or some crap in /etc/make.conf.

Thanks for the suggestions.  The locally-modified files I have on the
laptop are:

Index: contrib/libpcap/gencode.c
Index: include/Makefile
Index: sys/dev/an/if_aironet_ieee.h
Index: sys/dev/an/if_an.c
Index: sys/dev/an/if_anreg.h
Index: sys/dev/ar/if_ar.c
Index: sys/dev/sound/pci/maestro.c
Index: sys/dev/sound/pci/maestro_reg.h
Index: sys/dev/sound/pcm/buffer.c
Index: sys/dev/sound/pcm/buffer.h
Index: sys/dev/sound/pcm/channel.c
Index: sys/dev/sr/if_sr.c
Index: usr.sbin/ancontrol/ancontrol.8
Index: usr.sbin/ancontrol/ancontrol.c
Index: usr.sbin/ppp/Makefile

In the case of include/Makefile, the difference is appending dev/an to
LSUBDIRS; in the case of usr.sbin/ppp/Makefile, the difference is
specification of a fully-qualified path for m4 on line 26.

The non-comments I have in /etc/make.conf are:

g1-7(5.0-CUR)[12] grep -v '^#' /etc/make.conf
CFLAGS= -O -pipe
COPTFLAGS= -O -pipe
COMPAT22=   yes
COMPAT3X=   yes
COMPAT4X=   yes
PRINTERDEVICE=  ps
HAVE_MOTIF= yes
USA_RESIDENT=   YES
FORCE_PKG_REGISTER=YES
XFREE86_VERSION=4
WITH_PNG_MMX=YES
SENDMAIL_MC=/etc/mail/laptop.mc
g1-7(5.0-CUR)[13] 

The thing that's puzzling me is that I've been tracking -CURRENT (as
well as -STABLE) daily for a while, successfully.  And looking through
the archive of cvs-all, I don't see anything obvious within the last
couple of days.  (Last couple of days vs. last day because I'm
acutely aware of the effect where a change can go in OK, but can break
during the next build.  The gawk vs. one-true-awk incident is one such
case in recent memory, for example.)

Here's my recent CVSup history, in case it's of interest or value:

freebeast(5.0-CUR)[5] tail /var/log/cvsup-history.log
CVSup begin from cvsup14.freebsd.org at Sat Jan 26 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Sat Jan 26 04:37:34 PST 2002
CVSup begin from cvsup14.freebsd.org at Sun Jan 27 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Sun Jan 27 03:54:59 PST 2002
CVSup begin from cvsup14.freebsd.org at Mon Jan 28 03:47:02 PST 2002
CVSup ended from cvsup14.freebsd.org at Mon Jan 28 04:38:31 PST 2002
CVSup begin from cvsup14.freebsd.org at Tue Jan 29 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Tue Jan 29 03:56:22 PST 2002
CVSup begin from cvsup14.freebsd.org at Wed Jan 30 03:47:03 PST 2002
CVSup ended from cvsup14.freebsd.org at Wed Jan 30 03:53:49 PST 2002
freebeast(5.0-CUR)[6] 

(And yes, save for the last entry, I built both -STABLE and -CURRENT
after each CVSup.  I got today's -STABLE built OK, too -- both on the
laptop and the build machine.)

Thanks,
david(links to my resume at http://www.catwhisker.org/~david)
-- 
David H. Wolfskill  [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

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

Re: Weirdness in building -CURRENT today

2002-01-30 Thread Ruslan Ermilov


On Wed, Jan 30, 2002 at 07:41:51AM -0800, David Wolfskill wrote:
 Date: Wed, 30 Jan 2002 17:02:07 +0200
 From: Ruslan Ermilov [EMAIL PROTECTED]
 
 
   stage 2: cleaning up the object tree
  --
  ...
  === lib/libc
  /usr/src/share/mk/bsd.lib.mk, line 184: Inconsistent operator for libc.a
  /usr/src/share/mk/bsd.lib.mk, line 192: Inconsistent operator for libc_p.a
  /usr/src/share/mk/bsd.lib.mk, line 224: Inconsistent operator for libc_pic.a
  make: fatal errors encountered -- cannot continue
  *** Error code 1
 
 You probably have some locally modified src/ makefiles,
 or some crap in /etc/make.conf.
 
 Thanks for the suggestions.  The locally-modified files I have on the
 laptop are:
 
Should be fixed in the attached commit.


-- 
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

---BeginMessage---

bde 2002/01/30 07:14:25 PST

  Modified files:
sys/sys  syscall.mk 
  Log:
  Regenerate just this file after unbreaking makesyscalls.sh.  The previous
  commit broke the world in libc.
  
  Revision  ChangesPath
  1.53  +1 -1  src/sys/sys/syscall.mk

---End Message---

Re: Weirdness in building -CURRENT today

2002-01-30 Thread David Wolfskill


Date: Wed, 30 Jan 2002 18:31:14 +0200
From: Ruslan Ermilov [EMAIL PROTECTED]


 stage 2: cleaning up the object tree
--
...
=== lib/libc
/usr/src/share/mk/bsd.lib.mk, line 184: Inconsistent operator for libc.a
/usr/src/share/mk/bsd.lib.mk, line 192: Inconsistent operator for libc_p.a
/usr/src/share/mk/bsd.lib.mk, line 224: Inconsistent operator for libc_pic.a
make: fatal errors encountered -- cannot continue
*** Error code 1

Should be fixed in the attached commit [src/sys/sys/stscall.mk revision
1.53 -- dhw].

Aye; it's certainly past the trouble-spot now -- thanks to both of you!

Cheers,
david   (links to my resume at http://www.catwhisker.org/~david)
-- 
David H. Wolfskill  [EMAIL PROTECTED]
I believe it would be irresponsible (and thus, unethical) for me to advise,
recommend, or support the use of any product that is or depends on any
Microsoft product for any purpose other than personal amusement.

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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-24 Thread Max Khon


hi, there!

On Sat, 23 Dec 2000, Chris wrote:

 Actually, last time I checked, I think stable did not install with a RO
 /usr/src either.  Anyone know if this is still the case?

I have no problems with 'make installworld' with RO obj and src on
latest -stable

/fjoe



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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-24 Thread Matt Dillon



:On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote:
:
:I will fix it today.

Works like a charm now, thanks!  My -current source is broken out on
my -stable machine, so the only way to compile it is via an NFS mount
to a -current machine which, for obvious reasons, needs to be read-only.

In regards to your commit message backing out the change.  I kinda liked
the change (if it could be made to work).  What about modifying 'make'
itself to provide a MAKEOBJDIRBASE environment variable in addition
to the MAKEOBJDIRPREFIX environment variable?  Kinda messy, but I think
it would work.

What you would do is generate a MAKEOBJDIRBASE environment by running
`pwd` inside /usr/src/sys/compile/BLAH.  The make program would adjust
it's use of MAKEOBJDIRPREFIX:

1.   ${MAKEOBJDIRPREFIX}/`pwd`

By taking MAKEOBJDIRBASE into account.  Specifically, it would take the 
`pwd` that *it* runs and it would chop of MAKEOBJDIRBASE, leaving us
with:

${MAKEOBJDIRPREFIX}/(`pwd` with MAKEOBJDIRBASE chopped off at the head)

I believe this would produce the correct path.  But it does require 
modifying the 'make' program.

The only other alternative is to generate an appropriate MAKEOBJDIR
variable for each module directory.  That might require ripping up too
much stuff though.

-Matt



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

Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon


While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:

=== 3dfx
@ - /FreeBSD/FreeBSD-current/src/sys
ln: @: Read-only file system
*** Error code 1

Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
*** Error code 1

It looks like it's trying to mess around with something in /usr/src,
which is a read-only NFS mount.  Needless to say we do not want to
break being able to have a read-only /usr/src!

Anyone been messing with the 3dfx module recently ?

-Matt



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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Crist J. Clark


On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote:
 While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
 
 === 3dfx
 @ - /FreeBSD/FreeBSD-current/src/sys
 ln: @: Read-only file system
 *** Error code 1
 
 Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
 *** Error code 1
 
 It looks like it's trying to mess around with something in /usr/src,
 which is a read-only NFS mount.  Needless to say we do not want to
 break being able to have a read-only /usr/src!
 
 Anyone been messing with the 3dfx module recently ?

Myself and a few others found debris in our /usr/src/sys
recently. Looks like it might be what you have there. None of us were
sure if it was us messing it up or trouble somewhere else.

Do a 'make cleandir' in your _source tree_ and try the build again.
-- 
Crist J. Clark   [EMAIL PROTECTED]


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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Mike Smith


 While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
 
 === 3dfx
 @ - /FreeBSD/FreeBSD-current/src/sys
 ln: @: Read-only file system
 *** Error code 1
 
 Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
 *** Error code 1
 
 It looks like it's trying to mess around with something in /usr/src,
 which is a read-only NFS mount.  Needless to say we do not want to
 break being able to have a read-only /usr/src!
 
 Anyone been messing with the 3dfx module recently ?

All the modules do this.  Remove "MODULES_WITH_WORLD" from your 
/etc/make.conf; they're not compatible with a read-only source tree.

-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E




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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Chris Faulhaber


On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote:
 While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
 
 === 3dfx
 @ - /FreeBSD/FreeBSD-current/src/sys
 ln: @: Read-only file system
 *** Error code 1
 

Wouldn't using the buildkernel/installkernel targets be more appropriate
for a read-only source-tree?

-- 
Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]

FreeBSD: The Power To Serve   -   http://www.FreeBSD.org


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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon



:
:On Sat, Dec 23, 2000 at 12:24:51AM -0800, Matt Dillon wrote:
: While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
: 
: === 3dfx
: @ - /FreeBSD/FreeBSD-current/src/sys
: ln: @: Read-only file system
: *** Error code 1
: 
:
:Wouldn't using the buildkernel/installkernel targets be more appropriate
:for a read-only source-tree?
:
:-- 
:Chris D. Faulhaber - [EMAIL PROTECTED] - [EMAIL PROTECTED]

Tried using the buildkernel target, doesn't work either.

I don't have MODULES_WITH_WORLD set in /etc/make.conf.

I tried 'make cleandir' in /usr/src and that does not fix the problem
either.

Something got broken in the last week or two, it never did this sort
of thing before.

-Matt



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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon



:
: While trying to run 'make depend' in /usr/src/sys/compile/BLAH I got:
: 
: === 3dfx
: @ - /FreeBSD/FreeBSD-current/src/sys
: ln: @: Read-only file system
: *** Error code 1
: 
: Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
: *** Error code 1
: 
: It looks like it's trying to mess around with something in /usr/src,
: which is a read-only NFS mount.  Needless to say we do not want to
: break being able to have a read-only /usr/src!
: 
: Anyone been messing with the 3dfx module recently ?
:
:All the modules do this.  Remove "MODULES_WITH_WORLD" from your 
:/etc/make.conf; they're not compatible with a read-only source tree.

I've partially tracked it down to the ILINKS target in kmod.mk being
run while in the wrong directory.  It SHOULD be in
/FreeBSD/FreeBSD-current/src/sys/compile/TEST4/modules/3dfx 
(aka /usr/src/sys/compile/TEST4/modules/3dfx).  But instead,
when I echo `pwd` in the ILINKS target it appears to be cd'd into
the main modules source directory:

mv -f .newdep .depend
find ../../modules -type d -a ! -name CVS  | sed -e "s|../../modules|modules|g" | 
xargs mkdir -p ;  cd ../../modules ; env 
MAKEOBJDIRPREFIX=/FreeBSD/FreeBSD-current/src/sys/compile/TEST4/modules 
KMODDIR=/boot/kernel make depend
=== 3dfx
@ - /FreeBSD/FreeBSD-current/src/sys
/FreeBSD/FreeBSD-current/src/sys/modules/3dfx   
ln: @: Read-only file system
*** Error code 1

Stop in /FreeBSD/FreeBSD-current/src/sys/modules/3dfx.
*** Error code 1

Stop in /FreeBSD/FreeBSD-current/src/sys/modules.

This is not right.  Someone did something to change the compile dir 
as of the time the dependancies are run.  The cd in the 'find' sequence
is correct

It looks like someone blew up the making of the object directories under
compile/TEST4/modules.  Under 4.x I had paths like this:


/usr/src/sys/compile/TEST4/modules/FreeBSD/FreeBSD-current/usr/src/sys/modules/tx/

Under -current they are like this:

/usr/src/sys/compile/TEST4/modules/tx/...

The 'make' program can't find the object module directory any more.  Ahh..
so maybe I should remake the make program, eh?  Tried that, doesn't work.

Whoever 'fixed' object directory creation under /usr/src/sys/compile/BLAH
for modules broke it instead.

-Matt



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

found the fragger. Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon


Ok, I found it.  /usr/src/sys/conf/Makefile.i386 is broken.  It looks
like either you or David O'Brien (I'm guessing, your guys names are 
prominent in the CVS logs but I haven't tracked it down exactly)
screwed up the object directory creation while trying to optimize it.

It looks like it is trying to create short object directory names.
But the make program can't find them when looking for object directories.

This breaks MAKEOBJDIRPREFIX.  The 'make' program looks in:

1.   ${MAKEOBJDIRPREFIX}/`pwd`
2.   ${MAKEOBJDIR}
3.   obj.${MACHINE}
4.   obj
5.   /usr/obj/`pwd`

(taken from the 'make' man page)

And NONE of these is the object path you create in the Makefile.

This causes the make system to revert to tring to create the files
in the source directory rather then the object directory.

-Matt



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

Re: found the fragger. Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread David O'Brien


On Sat, Dec 23, 2000 at 11:24:50AM -0800, Matt Dillon wrote:
 like either you or David O'Brien (I'm guessing, your guys names are 

I will fix it today.


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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Crist J. Clark


On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote:

[snip]

 I tried 'make cleandir' in /usr/src and that does not fix the problem
 either.

Sorry, I was not clear enough. You need to do,

  # cd /usr/src/sys/modules
  # make cleandir

A 'cleandir' from /usr/src will not climb up into the modules.
-- 
Crist J. Clark   [EMAIL PROTECTED]


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

Re: found the fragger. Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon



:I will fix it today.
:

Thanks a lot Dave!

-Matt


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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Jeremy Lea


Hi,

On Sat, Dec 23, 2000 at 09:43:29AM -0800, Matt Dillon wrote:
 Something got broken in the last week or two, it never did this sort
 of thing before.

David's speedup commits to sys/conf/Makefile.*.  I informed him of the
problem, and asked him to back out the hacks, but he wants the
speedup...

Regards,
 -Jeremy

-- 
FreeBSD - Because the best things in life are free...
   http://www.freebsd.org/


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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Chris



Actually, last time I checked, I think stable did not install with a RO
/usr/src either.  Anyone know if this is still the case?

Chris

 It looks like it's trying to mess around with something in /usr/src,
 which is a read-only NFS mount.  Needless to say we do not want to
 break being able to have a read-only /usr/src!
 
 Anyone been messing with the 3dfx module recently ?
 
 -Matt
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with "unsubscribe freebsd-current" in the body of the message


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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread sthaug


 Actually, last time I checked, I think stable did not install with a RO
 /usr/src either.  Anyone know if this is still the case?

I have installed -stable many times with /usr/src mounted readonly
via NFS.

Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]


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

Re: Problem building -current kernel with read-only /usr/src.

2000-12-23 Thread Matt Dillon



:
: Actually, last time I checked, I think stable did not install with a RO
: /usr/src either.  Anyone know if this is still the case?
:
:I have installed -stable many times with /usr/src mounted readonly
:via NFS.
:
:Steinar Haug, Nethelp consulting, [EMAIL PROTECTED]

   Yah, -stable is fine.  I've done the same.  Most recently two days ago.

-Matt



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

Building -current kernel on ref5 broken ?

2000-10-29 Thread Darren Reed


Apart from the config(8) issue, I see this building GENERIC:

cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes  
-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual  -fformat-extensions -ansi  
-nostdinc -I- -I. -I../.. -I/usr/include -I../../contrib/dev/acpica/Subsystem/Include  
-D_KERNEL -include opt_global.h -elf  -mpreferred-stack-boundary=2  ../../pci/pci.c
../../pci/pci.c: In function `pci_add_map':
../../pci/pci.c:1008: `cfg' undeclared (first use in this function)
../../pci/pci.c:1008: (Each undeclared identifier is reported only once
../../pci/pci.c:1008: for each function it appears in.)
../../pci/pci.c:1008: too few arguments to function `pci_porten'
../../pci/pci.c:1010: too few arguments to function `pci_memen'
../../pci/pci.c:953: warning: unused variable `cmd'
*** Error code 1

Darren


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

Problem building -current kernel

2000-05-22 Thread Stephen J. Roznowski


I'm attempting to update my -current system from mid-April, and
I'm getting the following error:

make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx
Warning: Object directory not changed from original /usr/src/sys/compile/ISTARI
cc -c -x assembler-with-cpp -DLOCORE -O -pipe -Wall -Wredundant-decls -Wnested-e
xterns -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline -Wcast
-qual  -fformat-extensions -ansi  -nostdinc -I- -I. -I../.. -I../../../include
-D_KERNEL -include opt_global.h -elf  -mpreferred-stack-boundary=2 ../../i386/i3
86/bioscall.s
{standard input}: Assembler messages:
{standard input}:772: Error: operands given don't match any known 386 instructio
n
{standard input}:837: Error: operands given don't match any known 386 instructio
n
*** Error code 1

Lines, 772 and 837 contain:

lcall   * bioscall_vector

Any clue what I'm doing wrong?

Thanks,
-- 
Stephen J. Roznowski([EMAIL PROTECTED])



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

Re: Problem building -current kernel

2000-05-22 Thread Kris Kennaway


On Mon, 22 May 2000, Stephen J. Roznowski wrote:

 I'm attempting to update my -current system from mid-April, and
 I'm getting the following error:

make world first, or build the new binutils.

Kris


In God we Trust -- all others must submit an X.509 certificate.
-- Charles Forsythe [EMAIL PROTECTED]



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

Re: Error building current

2000-01-20 Thread David O'Brien


On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote:
 CVS'uped today:
... 
 gcc/version.c is "dead" in my CVS repository.  Has my repository been
 corrupted somehow?

Please try again.  Did you change release tags or something?  Possibly
checked out RELENG_3 on top of the HEAD or something?
 
-- 
-- David([EMAIL PROTECTED])


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

Re: Error building current

2000-01-20 Thread Warner Losh


In message [EMAIL PROTECTED] "David O'Brien" writes:
: On Thu, Jan 20, 2000 at 11:01:10AM -0800, Tim Moore wrote:
:  CVS'uped today:
: ... 
:  gcc/version.c is "dead" in my CVS repository.  Has my repository been
:  corrupted somehow?
: 
: Please try again.  Did you change release tags or something?  Possibly
: checked out RELENG_3 on top of the HEAD or something?

I hit this problem as well.  Put 'delete' in your cvsup file.
Otherwise you'll get screwed.  This is a misfeature of cvsup, imho,
but if you don't have 'delete' in your cvsup file, versions that go
away aren't removed and branch changes don't seem to happen...

Warner


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

Re: Error building current

2000-01-20 Thread John Polstra


In article [EMAIL PROTECTED],
Warner Losh  [EMAIL PROTECTED] wrote:
 
 I hit this problem as well.  Put 'delete' in your cvsup file.
 Otherwise you'll get screwed.  This is a misfeature of cvsup, imho,

I'm sorry you think so.  I did it that way for backward compatibility
with sup.  If I hadn't made it compatible, I never could have
persuaded anybody to try the software.

Also, there are situations (e.g., maintaining local modifications
in your repository) where delete should not be used.  So it really
needs to be an option.  It would be better if the default were to
delete and there was a "nodelete" option.  But that wouldn't have been
compatible.

John
-- 
  John Polstra   [EMAIL PROTECTED]
  John D. Polstra  Co., Inc.Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa



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

Error building current

2000-01-20 Thread Tim Moore


CVS'uped today:

cd /usr/src/gnu/usr.bin/cc/cc_tools; make build-tools
cannot open
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/version.c: no
such file
"/usr/src/gnu/usr.bin/cc/cc_tools/../Makefile.inc", line 28: warning: "sed
-e 's/.*\"\([^ \"]*\)[ \"].*/\1/' 
/usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/version.c"
returned non-zero status
make: don't know how to make c-parse.gperf. Stop

gcc/version.c is "dead" in my CVS repository.  Has my repository been
corrupted somehow?

Tim




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

89 matches

Mail list logo