Skip to contentSkip to conversation

New: util-linux-2.30/.stamp_built' failed

Buildroot bugzilla at busybox.net 1 participant 11 messages Jun 19, 2017 – Feb 25, 2019

lore
Share & tools
lore
#0 lore raw

https://bugs.busybox.net/show_bug.cgi?id=9966

Bug ID: 9966
Summary: util-linux-2.30/.stamp_built' failed
Product: buildroot
Version: unspecified
Hardware: Other
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: tuzakli.refik at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---

/home/osboxes/Desktop/boards/arm/karo/tx6u_8033/fs/buildroot/output/host/usr/lib/libncurses.so:
file not recognized: File format not recognized
collect2: error: ld returned 1 exit status
Makefile:5997: recipe for target 'dmesg' failed
make[3]: *** [dmesg] Error 1
make[3]: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/osboxes/Desktop/boards/arm/karo/tx6u_8033/fs/buildroot/output/build/util-linux-2.30' Makefile:11718: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/home/osboxes/Desktop/boards/arm/karo/tx6u_8033/fs/buildroot/output/build/util-linux-2.30' Makefile:4913: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/osboxes/Desktop/boards/arm/karo/tx6u_8033/fs/buildroot/output/build/util-linux-2.30' package/pkg-generic.mk:227: recipe for target '/home/osboxes/Desktop/boards/arm/karo/tx6u_8033/fs/buildroot/output/build/util-linux-2.30/.stamp_built' failed
make: *** [/home/osboxes/Desktop/boards/arm/karo/tx6u_8033/fs/buildroot/output/build/util-linux-2.30/.stamp_built] Error 2

armv7 a9

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#1 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

https://bugs.busybox.net/show_bug.cgi?id=9966

Carlos Santos <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at buildroot.uclibc |casantos at datacom.ind.br
|.org |

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#2 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=9966

Carlos Santos <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED

--- Comment #1 from Carlos Santos <[email protected]> --- Please check if the problem persists on a recent master snapshot (as of commit 74235a6854d6e469f2dbc141fe08ce9ae94e7d3c).

Please provide a copy of your defconfig. Run

    $ make savedefconfig BR2_DEFCONFIG=/tmp/bug_9966_defconfig

Then attach /tmp/bug_9966_defconfig to this bug report.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#4 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=9966

Carlos Santos <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |WORKSFORME
             Status|ASSIGNED                    |RESOLVED

--- Comment #3 from Carlos Santos <[email protected]> --- Looks like the reporter attempted to perform a dirty build in an output directory containing traces of a previous build, for a different architecture.

Closing as RESOLVED/WORKSFORME, since the reporter did not provide enough information to reproduce the failure and was able to circumvent the problem by means of a clean build.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#5 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=9966

Micha? Miros?aw <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|RESOLVED                    |REOPENED
         Resolution|WORKSFORME                  |---

--- Comment #4 from Micha? Miros?aw <[email protected]> --- I just stumbled on this problem on 2018.11.3 after adding a patch that modifies configure.ac.

'make clean' does not help in this case.

It seems that this modification triggers regererating of aclocal.m4 (it has some parts replaced with an older version) and all the paths to tools and libraries in resulting Makefiles get mixed up.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#6 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=9966

Micha? Miros?aw <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |mirq-boogs at rere.qmqm.pl

--- Comment #5 from Micha? Miros?aw <[email protected]> --- Created attachment 7961
--> https://bugs.busybox.net/attachment.cgi?id=7961&action=edit
patch for util-linux configure.ac

For reproduction: put attached patch in package/util-linux/

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#8 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=9966

Carlos Santos <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------

         Resolution|---                         |WORKSFORME
             Status|REOPENED                    |RESOLVED

--- Comment #6 from Carlos Santos <[email protected]> --- (In reply to Micha? Miros?aw from comment #5)

Sorry, this is not a bug in Buildroot. You add a patch that knowingly breaks the build and then complain that the build gets broken.

Also, please do not reopen an old bug just because you saw a similar behavior in a new situation. A bug must be reopened if it's resolution was not correct. New problems must be reported as new bugs.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#9 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=9966

--- Comment #7 from Micha? Miros?aw <[email protected]> --- (In reply to Carlos Santos from comment #6)

I don't want to point fingers. Adding 'UTIL_LINUX_AUTORECONF = YES' line to package/util-linux/util-linux.mk fixes the problem.

I guess it has something to do with buildroot's makefile replacing config/ltmain.sh in the package but not in autotools it provides. The file get's replaced with unpatched version when ./configure runs autoreconf to update itself.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.
#10 lore raw

[Buildroot] [Bug 9966] util-linux-2.30/.stamp_built' failed

In reply to bugzilla at busybox.net

https://bugs.busybox.net/show_bug.cgi?id=9966

--- Comment #8 from Carlos Santos <[email protected]> --- (In reply to Micha? Miros?aw from comment #7)

Let me clarify my point: I'm not against adding a patch to disable rtcwake, even though I believe this should be submitted upstream first. My point is that such change would be an improvement, not a bug fix, so the right way to do it is by means of a patch on Buildroot that adds the required patch for util-linux and also turns AUTORECONF to YES.

Also, this discussion should happen on the buildroot mailing list, not on a bug report, so I stop here.

Signature · 2 lines
You are receiving this mail because:
You are on the CC list for the bug.