| Summary: | Configure for packages with "static" useflag fails (using uClibc-0.9.30.1-r1 and gcc-4.4.5) | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Sebastian Doering <moralapostel> |
| Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | example config.log from sys-devel/patch | ||
|
Description
Sebastian Doering
2010-11-16 21:55:57 UTC
Created attachment 254551 [details]
example config.log from sys-devel/patch
configure:2281: checking whether the C compiler works configure:2291: ./a.out configure:2295: $? = 139 configure:2302: error: in `/var/tmp/portage/sys-devel/patch-2.6.1/work/patch-2.6.1': configure:2306: error: cannot run C compiled programs. If you meant to cross compile, use `--host'. See `config.log' for more details. Is that filesystem mounted rw? Is executing files on that filesystem enabled (i.e. noexec is not a mount option)? (In reply to comment #2) Actually, forget about this one: > Is that filesystem mounted rw? And focus on this one: > Is executing files on that filesystem enabled > (i.e. noexec is not a mount option)? (In reply to comment #3) > (In reply to comment #2) > > Actually, forget about this one: > > > Is that filesystem mounted rw? > Yes it is. Obviously. > And focus on this one: > > > Is executing files on that filesystem enabled > > (i.e. noexec is not a mount option)? > I appreciate your replies, but these seem to be - no offense intended - redundant questions. How would I even be able to execute emerge or configure or anything else for that matter if the filesystem were 'noexec'.
> And focus on this one:
>
> > Is executing files on that filesystem enabled
> > (i.e. noexec is not a mount option)?
>
Additional information about the filesystem: xfs formated loop device:
"/dev/loop0 on /media/gentoo type xfs (rw,nosuid,nodev)"
But I really don't think there is any problem with the filesystem, since I already have compiled and installed some packages without problems.
I am currently in the process of rerunning the bootstrap.sh script, to make sure that the toolchain is sane.
On a hunch I changed the CHOST to "CHOST="i586-pc-linux-uclibc". With this CHOST the aforementioned packages compile fine. Switching back to i686 I see the same error again. => gcc bug?! Testing some other combinations of variables revealed that CHOST="i686-pc-linux-uclibc" CBUILD="i586-pc-linux-uclibc also works. Could that indicate a problem with my toolchain (I ran bootstrap.sh and compiled gcc/binutils/uclibc many times with the i686 CHOST, so it should be ok)? Seems weird to me. (In reply to comment #6) > On a hunch I changed the CHOST to "CHOST="i586-pc-linux-uclibc". With this > CHOST the aforementioned packages compile fine. Switching back to i686 I see > the same error again. > > => gcc bug?! Rather misunderstanding of the cross-compilation idea. As I guess, switching to i586- makes configure not match any compiler with that prefix and fallback to simple 'gcc' which uses your host's default compiler. Thus, as I see it, the problem is that your host system is unable to execute uclibc-based programs. In other words, you should try cross-compiling. I think you can find some information on the topic in the Embedded Handbook [1]. Feel free to reopen the bug if you really think it's an issue with Gentoo. [1] http://www.gentoo.org/proj/en/base/embedded/handbook/ |
