Bug #2589

buildworld issues

Added by ano 12 months ago. Updated 11 months ago.

Status:ClosedStart date:09/26/2013
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

make buildworld failed on fresh dfly-3.4.3:
===> gnu/lib/gcc44/libstdc++
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libstdc++.a /usr/obj/usr/src/world_x86_64/usr/lib/gcc44
sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libstdc++_p.a /usr/obj/usr/src/world_x86_64/usr/lib/gcc44/profile/libstdc++.a
sh /usr/src/tools/install.sh -s -o root -g wheel -m 444 libstdc++.so.9 /usr/obj/usr/src/world_x86_64/usr/lib/gcc44
install: libstdc++.so.9: No such file or directory
*** Error code 71

History

#1 Updated by swildner 12 months ago

On Thu, 26 Sep 2013 20:33:39 +0200,
wrote:

> make buildworld failed on fresh dfly-3.4.3:
> ===> gnu/lib/gcc44/libstdc++
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libstdc++.a
> /usr/obj/usr/src/world_x86_64/usr/lib/gcc44
> sh /usr/src/tools/install.sh -C -o root -g wheel -m 444 libstdc++_p.a
> /usr/obj/usr/src/world_x86_64/usr/lib/gcc44/profile/libstdc++.a
> sh /usr/src/tools/install.sh -s -o root -g wheel -m 444
> libstdc++.so.9 /usr/obj/usr/src/world_x86_64/usr/lib/gcc44
> install: libstdc++.so.9: No such file or directory
> *** Error code 71

Can you check if your tree is dirty?

cd /usr/src
git status

Sascha

#2 Updated by ano 12 months ago

There is fresh dfly with "make src-create"

10:43 ano@px:/usr/src:$ git status
# On branch DragonFly_RELEASE_3_4
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# nohup.out
# sys/config/ANO
nothing added to commit but untracked files present (use "git add" to track)

#3 Updated by swildner 12 months ago

On Fri, 27 Sep 2013 08:41:48 +0200,
wrote:

>
> Issue #2589 has been updated by ano.
>
>
> There is fresh dfly with "make src-create"
>
> 10:43 ano@px:/usr/src:$ git status
> # On branch DragonFly_RELEASE_3_4
> # Untracked files:
> # (use "git add ..." to include in what will be committed)
> #
> # nohup.out
> # sys/config/ANO
> nothing added to commit but untracked files present (use "git add" to
> track)

Hmm,

was it a -j x build? Do you have a log file of the build? Maybe the line
with the actual error was further up in the log. Look for "error:".

Sascha

#4 Updated by ano 12 months ago

I do not use -j option on VPS and already deleted nohup.out.

I have tried to build world after your last commit (54ff46d7fce3643db9c2988d826476dc96ab7d66) which seems unrelated to the problem but buildworld finished with no errors.

#5 Updated by marino 11 months ago

  • Status changed from New to Closed

seems to have resolved itself...

Also available in: Atom PDF