Bug 6272 - coreutils build fails
Summary: coreutils build fails
Status: RESOLVED WORKSFORME
Alias: None
Product: buildroot
Classification: Unclassified
Component: Other (show other bugs)
Version: unspecified
Hardware: PC Linux
: P5 minor
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-05-24 08:50 UTC by Ryan
Modified: 2014-01-07 08:34 UTC (History)
1 user (show)

See Also:
Host: mipsel-buildroot-linux-uclibc
Target: mipsel-buildroot-linux-uclibc
Build: i686-pc-linux-gnu

Attachments
Build log (11.04 KB, application/x-gzip)
2013-05-24 08:51 UTC, Ryan 		Details
Configuration file showing(-ish) the problem. (5.49 KB, application/x-gzip)
2013-05-29 00:57 UTC, Ryan 		Details
Failed configure. (13.37 KB, application/x-gzip)
2013-05-29 00:59 UTC, Ryan 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Ryan 2013-05-24 08:50:05 UTC 
Building coreutils on buildroot-2013.02 results in an error. Log is attached.
Comment 1 Ryan 2013-05-24 08:51:30 UTC 
Created attachment 4928 [details]
Build log
Comment 2 Thomas Petazzoni 2013-05-24 09:18:35 UTC 
Thanks for the report. Could you post a Buildroot .config (preferably minimal) that exhibits the problem, so that we can easily reproduce?
Comment 3 Ryan 2013-05-29 00:57:23 UTC 
Created attachment 4934 [details]
Configuration file showing(-ish) the problem.

See config.log line 1059 for more information.
Comment 4 Ryan 2013-05-29 00:59:26 UTC 
Created attachment 4940 [details]
Failed configure.

Line 1059 shows same failure type, but during the configure stages of systemd.
Comment 5 Ryan 2013-05-29 01:04:08 UTC 
Sorry for the delay... I was trying to find a simpler .config to provide, but was encountering errors elsewhere. Upon inspecting the logs, though, I did find that the error was related.

Some more info, I am using a vendor supplied toolchain(gcc-4.5.3-2.4) and kernel(3.3.8-2.0).
Comment 6 Thomas Petazzoni 2013-05-29 06:41:07 UTC 
Can you provide us the toolchain? Without it, we can't reproduce the problem, and the problem *looks* toolchain related. Thanks!
Comment 7 Thomas Petazzoni 2013-05-29 19:11:59 UTC 
Ok, I've found the toolchain on some random website. I'll need some time to reproduce the problem, though.
Comment 8 Ryan 2013-05-29 21:42:59 UTC 
Okay. If the toolchain you have found isn't enough, I can upload mine. Just let me know!
Comment 9 Thomas Petazzoni 2013-11-14 00:06:07 UTC 
In fact, I no longer have the toolchain, and I'm unable to find it on the web. Can you make it available somewhere, or reproduce the problem with a publicly available toolchain?
Comment 10 Thomas Petazzoni 2014-01-07 08:34:24 UTC 
Problem only happened with a very specific toolchain. However, we don't have access to this toolchain, and the reporter did not come back to give the toolchain, which was requested almost two months ago.

So I'll close this bug for now. Do not hesitate to reopen it with more informations.