Author Topic: C Compiler Cannot Create Executables  (Read 5531 times)

ShiroiKuma

  • Hero Member
  • *****
  • Posts: 900
    • View Profile
C Compiler Cannot Create Executables
« on: June 06, 2006, 01:38:16 pm »
I must've done something trivial, but now when I run bitbake, it runs configure on some file, I get:
Code: [Select]
checking for C compiler default output file name... configure: error: C compiler cannot create executablesYet 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.
[span style=\'font-size:8pt;line-height:100%\']Das ganze tschechische Volk ist eine Simulantenbande.[/font][/span]
Militäroberarzt Bautze

lardman

  • Hero Member
  • *****
  • Posts: 4512
    • View Profile
    • http://people.bath.ac.uk/enpsgp/Zaurus/
C Compiler Cannot Create Executables
« Reply #1 on: June 06, 2006, 01:48:46 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.

Si
C750 OZ3.5.4 (GPE, 2.6.x kernel)
SL5500 OZ3.5.4 (Opie)
Nokia 770
Serial GPS, WCF-12, Socket Ethernet & BT, Ratoc USB
WinXP, Mandriva

ShiroiKuma

  • Hero Member
  • *****
  • Posts: 900
    • View Profile
C Compiler Cannot Create Executables
« Reply #2 on: June 06, 2006, 02:11:09 pm »
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130096\"][{POST_SNAPBACK}][/a][/div]
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?
[span style=\'font-size:8pt;line-height:100%\']Das ganze tschechische Volk ist eine Simulantenbande.[/font][/span]
Militäroberarzt Bautze

ShiroiKuma

  • Hero Member
  • *****
  • Posts: 900
    • View Profile
C Compiler Cannot Create Executables
« Reply #3 on: June 06, 2006, 02:33:34 pm »
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.
[span style=\'font-size:8pt;line-height:100%\']Das ganze tschechische Volk ist eine Simulantenbande.[/font][/span]
Militäroberarzt Bautze

ShiroiKuma

  • Hero Member
  • *****
  • Posts: 900
    • View Profile
C Compiler Cannot Create Executables
« Reply #4 on: June 06, 2006, 05:16:01 pm »
Quote
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.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=130096\"][{POST_SNAPBACK}][/a][/div]
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: [Select]
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?
[span style=\'font-size:8pt;line-height:100%\']Das ganze tschechische Volk ist eine Simulantenbande.[/font][/span]
Militäroberarzt Bautze