![]() ![]() |
Aug 17 2004, 12:24 AM
Post
#1
|
|
|
Group: Members Posts: 6 Joined: 16-August 04 Member No.: 4,305 |
I'm trying so set up OpenEmbedded on a system on which I do not have root (so I can only put stuff in $HOME). I am using the instructions at http://www.openembedded.org/oe_wiki/index.php/GettingStarted. When I run oemake I get
QUOTE | checking for C compiler default output file name... configure: error: C compiler cannot create executables This is because the compiler can't find the libraries which I have in $HOME/oe/opt/cross/arm-linux/lib. Any suggestions on how to set up my build environment? |
|
|
|
Aug 17 2004, 01:44 AM
Post
#2
|
|
|
Group: Members Posts: 1,497 Joined: 12-November 03 From: Germany Member No.: 907 |
Some random bits:
* OE support is at oe@handhelds.org * Which package did you try to oemake? * Cross-toolchains are not to be relocated * I never use OE as root |
|
|
|
Aug 17 2004, 02:27 AM
Post
#3
|
|
|
Group: Members Posts: 6 Joined: 16-August 04 Member No.: 4,305 |
QUOTE * OE support is at oe@handhelds.org This isn't really an OE issue. The OE bits are working fine; the problem is setting up the Linux enviroment. QUOTE * Which package did you try to oemake? libtool-native is what's failing. It's failing when configure tries to test the compiler. QUOTE * I never use OE as root. But you use root to install it, right? The problem is that I don't have access to /opt, which is where the cross compiler wants to be. |
|
|
|
Aug 17 2004, 10:31 AM
Post
#4
|
|
|
Group: Members Posts: 1,497 Joined: 12-November 03 From: Germany Member No.: 907 |
QUOTE But you use root to install it, right? The problem is that I don't have access to /opt, which is where the cross compiler wants to be. No I don't and OE doesn't use /opt. OE puts all things it builds under $TMPDIR. QUOTE This isn't really an OE issue. The OE bits are working fine; the problem is setting up the Linux enviroment. I suspect you did something wrong when setting OE up. Use oe@handhelds.org and tell us more about your system, i.e. your local.conf, your OEPATH, etc. |
|
|
|
Aug 17 2004, 12:56 PM
Post
#5
|
|
|
Group: Members Posts: 4,515 Joined: 25-October 03 From: Bath, UK Member No.: 464 |
Mickey, I'm pretty sure the 2.95.3 toolchain tarball from the OpenZaurus website wants to be stuck in /opt (otherwise it'll be in /usr/local/arm which is also probably not accessible to a non-superuser).
Although OE will build the GCC 3.xx toolchain it doesn't build 2.95.3 iirc. Correct me if I'm wrong, but this could be an issue, but only for compiling the kernel. Si |
|
|
|
Aug 17 2004, 01:26 PM
Post
#6
|
|
|
Group: Members Posts: 1,497 Joined: 12-November 03 From: Germany Member No.: 907 |
The 2.95.3 cross toolchain has nothing to do with the original posters's problems, since libtool-native is a native package.
That aside, my statement that "OE puts all things it builds under $TMPDIR." is true since, as you correctly pointed out, OE doesn't build a 2.95.3 (yet). If it would, it would put it under $TMPDIR. Anyway, the original poster has a problem with his native compiler, not with an OE built one. Aside from telling us more about your environment, what does config.log under $TMPDIR/work/libtool-native-.../ contain? |
|
|
|
Aug 19 2004, 05:20 AM
Post
#7
|
|
|
Group: Members Posts: 6 Joined: 16-August 04 Member No.: 4,305 |
Okay, I got it working. I guess I must have set it up wrong the first time I tried it. When I saw that error, I though I needed a prebuilt toolchain. (It does seem that the prebuilt toolchain requires root.) I tried it again from scratch and it works (though it seems the oe-env script at openembedded.org changed between my attempts; maybe that did it).
|
|
|
|
![]() ![]() |
|
Lo-Fi Version | Time is now: 19th May 2013 - 06:40 PM |