Project

General

Profile

Actions
Copy link

Bug #2658

closed

make buildworld on master install: libstand.a: No such file or directory

Added by davshao about 10 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/30/2014
Due date:
% Done:

0%

Estimated time:

Description

make buildworld, make -j7 buildworld, make quickworld fail on various systems (an x86_64 and an i386) trying to update from master

commit 21c9b87db1815625fe21f025ed40acb155396299
Date: Sat Mar 29 10:07:03 2014 +0100

<sys/cdefs.h>: Use _Static_assert for CTASSERT.

to

commit 31c7f3d798ffb1febb5ffaac0830bf8cc52bacdb
Date: Sun Mar 30 12:27:07 2014 +0200

<sys/cdefs.h>: Simplify the CTASSERT definition better.

or later with

/etc/make.conf

CFLAGS+=-g
STRIP=

WITH_PKGNG=yes
DISABLE_VULNERABILITIES=yes

WITH_VIM_OPTIONS=yes

and error messages:

===> lib/libsmb
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libsmb.a /usr/obj/usr/src/world_x86_64/usr/lib
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libsmb_p.a /usr/obj/usr/src/world_x86_64/usr/lib/profile/libsmb.a
sh /usr/src/tools/install.sh -o root -g wheel -m 444 libsmb.so.2 /usr/obj/usr/src/world_x86_64/usr/lib
ln -fs libsmb.so.2 /usr/obj/usr/src/world_x86_64/usr/lib/libsmb.so
===> lib/libsmdb
===> lib/libsmutil
===> lib/libstand
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libstand.a /usr/obj/usr/src/world_x86_64/usr/lib
install: libstand.a: No such file or directory
  • Error code 71

On at least one system make buildworld still fails after having cleared out /usr/obj/usr

cd /usr/obj
rm -rf usr

Actions
Copy link
 #1

Updated by swildner about 10 years ago

  • Status changed from New to Closed

I fixed it.

http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/08ecb92056444de3f12a7eb1d94f7bd4465a0431

Thanks for reporting.

However, I am not sure how you got to the conclusion that it had anything to do with the CTASSERT commits, when it was in fact a hammer2 commit which broke it.

Regarding "No such file or directory" errors. If you have a buildlog, you will usually find one or more lines containing "error:" earlier in the log, which give a better clue about the real error which caused the library to not be built and subsequently not being there for linking (which is what the "No such file or directory" shows).

Actions
Copy link
 #2

Updated by swildner about 10 years ago

Oh I see, the hammer2 commit was between the two CTASSERT commits.

Actions
Copy link

Also available in: Atom PDF