 C Compiler Cannot Create Executables |
OESF Forums > Distros, Development, and Model Specific Forums > Everything Development > OpenZaurus/Opie/Qtopia  |
 Jun 6 2006, 09:38 AM
Post
#1
|
|
 Group: Members Posts: 902 Joined: 22-May 04 Member No.: 3,385  |
I must've done something trivial, but now when I run bitbake, it runs configure on some file, I get:
CODE checking for C compiler default output file name... configure: error: C compiler cannot create executables Yet I test compiled hello.c no prob. When I run configure by hand, it runs, doesn't halt... Is it some permissions stuff? I'm running bitbake as root, so shouldn't be. It just changed today. The only thing I recall doing is I uninstalled libiconv, cause had it installed for some reason and it was messing with the ./configure processes. I'm running Debian Etch. Trying different, but so far no idea what the prob. |
 |
 
|
|
Jun 6 2006, 09:48 AM
Post
#2
|
|
|
Group: Members Posts: 4,515 Joined: 25-October 03 From: Bath, UK Member No.: 464 |
QUOTE I'm running bitbake as root, so shouldn't be. Don't run bitbake as root. Danger, especially if one of the .bbs is written incorrectly and starts writing arm files all over over your filesystem. Si |
|
|
|
|
Jun 6 2006, 10:11 AM
Post
#3
|
|
|
Group: Members Posts: 902 Joined: 22-May 04 Member No.: 3,385 |
QUOTE(lardman @ Jun 6 2006, 06:48 PM) QUOTE I'm running bitbake as root, so shouldn't be. Don't run bitbake as root. Danger, especially if one of the .bbs is written incorrectly and starts writing arm files all over over your filesystem.  OK, point taken. I've chmodded the build directory with 777, just to make sure there are no file permissions issues. But obviously, the behavior is still the same, I run bitbake as a reg user, and it bombs out with the C compiler cannot create executables, which totally beats me since I'm compiling in another tab right now, no prob... What can I do, reinstall bitbake? |
|
|
|
|
Jun 6 2006, 10:33 AM
Post
#4
|
|
|
Group: Members Posts: 902 Joined: 22-May 04 Member No.: 3,385 |
I've traced it, it is indeed related to that libiconv. The cross tools which were created by OpenEmbedded when I still had libiconv installed obviously referenced it, so now that it's gone they have undefined references, so will see if they rebuild themselves, or reinstall OE.
|
|
|
|
|
Jun 6 2006, 01:16 PM
Post
#5
|
|
|
Group: Members Posts: 902 Joined: 22-May 04 Member No.: 3,385 |
QUOTE(lardman @ Jun 6 2006, 06:48 PM) QUOTE I'm running bitbake as root, so shouldn't be. Don't run bitbake as root. Danger, especially if one of the .bbs is written incorrectly and starts writing arm files all over over your filesystem. I delete all of the build/tmp directory to rebuild the cross tools etc by bitbake and fix the libiconv prob. But now I have a question, when I run bitbake now, it bombs when compiling automake-native with CODE configure:1833: checking whether autoconf is installed configure:1838: eval autoconf --version autoconf (GNU Autoconf) 2.59d Written by David J. MacKenzie and Akim Demaille. Copyright (C) 2006 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:1841: $? = 0 configure:1849: result: yes configure:1859: checking whether autoconf works configure:1866: cd conftest && eval autoconf -o /dev/null conftest.ac autom4te: cannot open /dev/null.tmp: Permission denied configure:1869: $? = 1 configure:1878: result: no configure:1882: error: The installed version of autoconf does not work. Obviously it doesn't make sense to change perms for /dev So then how do you go through this as non-root? |
|
|
|
|
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:
|
Lo-Fi Version | Time is now: 19th June 2013 - 10:24 AM |