NetBSD-Bugs archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

port-amd64/54569: build.sh system seems broken



>Number:         54569
>Category:       port-amd64
>Synopsis:       build.sh system seems broken
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    port-amd64-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Sep 25 02:05:00 +0000 2019
>Originator:     The Grey Wolf
>Release:        NetBSD 9.99.11
>Organization:
Star Wolf Innovations
>Environment:
System: NetBSD eddie.starwolf.com 9.99.11 NetBSD 9.99.11 (EDDIE) #4: Thu Sep 19 01:20:40 PDT 2019 greywolf%eddie.starwolf.com@localhost:/sys/arch/amd64/compile/EDDIE amd64
Architecture: x86_64
Machine: amd64
>Description:

I seem to be having some build issues happening.  My pertinent environment/variables are as follows:

MACHINE=<amd64>
MACHINE_ARCH=<(not set)>
MAKEOBJDIR=</usr/src/build/arch/amd64/obj>
DESTDIR=</usr/src/build/arch/amd64/build/>
RELEASEDIR=</usr/src/build/arch/amd64/release/>
PATH=</usr/src/tools/tools-amd64/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/X11/bin:/usr/X11/sbin:/root/bin:/root/bashmodules>
MANPATH=</usr/src/tools/tools-amd64/man:>
BSDSRCDIR=</usr/src>
BSDOBJDIR=</usr/src/build/arch/amd64/obj>
BUILDROOT=</usr/src/build>
TOOLDIR=</usr/src/tools/tools-amd64>

MACHINE_ARCH is not set because things seem to go horribly wrong when it is set to x86_64, even though that appears to be the default MACHINE_ARCH for MACHINE=amd64.

My command line (general) is as such:

./build.sh -m amd64 -D /usr/src/build/arch/amd64/build/ \
	-O /usr/src/build/arch/amd64/obj \
	-R /usr/src/build/arch/amd64/release/ \
	-T /usr/src/tools/tools-amd64 -j12 {target}

Doesn't matter what my target is -- that command line works just fine; UNLESS:

If I add '-u' t o that command line, I get failures.  Isn't -u supposed to
skip cleandir and the tools rebuild?  The tools rebuild fails if the tools
already exist.  (This bug has been present for quite some time.)

If I add '-x' (to build X11), I get failures before the toolchain finishes
building.  Why there?  Does the toolchain contain any weird X11 dependencies?

So right now, I can't do a build-by-stages (tools, build, distribution,
release).  I can only pick one target and build to that, as each build
seems to require a total wipeout and restart.

My /etc/mk.conf:  https://www.starwolf.com/machines/eddie/mk.conf

Build Logs:
"build release", success: https://www.starwolf.com/machines/eddie/buildlogs/2019-09-23/1433-build-release.out.gz
"build release with -x", failure: https://www.starwolf.com/machines/eddie/buildlogs/2019-09-24/0031-build-release-fail.gz

"build tools", success: https://www.starwolf.com/machines/eddie/buildlogs/2019-09-24/0105-build-tools.out.gz
"build tools with -x", failure:  https://www.starwolf.com/machines/eddie/buildlogs/2019-09-24/0228-build-tools.fail.gz

I do in fact have the X sources at /usr/xsrc, updated 2019-09-23 (and
nothing new seems to have come in).

>How-To-Repeat:
	./build.sh -m amd64 -D /usr/src/build/arch/amd64/build/ \
	-O /usr/src/build/arch/amd64/obj -R \
	/usr/src/build/arch/amd64/release/ -T /usr/src/tools/tools-amd64 \
	-j12 -x {tools|build|release}
	
>Fix:
	Not known at this point.



Home | Main Index | Thread Index | Old Index