Skip to contentSkip to conversation

libffi-native 3.0.9 fails to build on at least x86_64

DISCUSSION Robert Schuster 3 participants 4 messages Mar 8, 2011

lore
Share & tools
lore
#0 lore raw

Hi,
I tried building libffi-native on an Ubuntu 10.04 amd64 box (during angstrom build for pandaboard) and it fails. Investigation found out that during libffi's configure it will symlink 'src/x86/ffitarget.h' to 'include/ffitarget.h'. Unfortunately this will create a broken softlink because 'src' and 'include' are on the same directory level. I manually corrected the softlink to '../src/x86/ffitarget.h' and then I could continue the build.

Clearly this is not what should happen. Anyone an idea why ffi does that?

(For testing purposes I tried brand new libffi 3.0.10rc8 and it shows exactly the same error).

Regards,
Robert

#1 lore raw

Re: libffi-native 3.0.9 fails to build on at least x86_64 [solved, problem on my side]

Hi,
I moved the whole OE directory (bitbake, oe, configdir) to a new location and made it available through the same path using a symlink. As it looks OE does not like that at all.

Regards,
Robert

Am 08.03.2011 07:50, schrieb Robert Schuster:

Quoted 24 lines

Hi,
I tried building libffi-native on an Ubuntu 10.04 amd64 box (during angstrom build for pandaboard) and it fails. Investigation found out that during libffi's configure it will symlink 'src/x86/ffitarget.h' to 'include/ffitarget.h'. Unfortunately this will create a broken softlink because 'src' and 'include' are on the same directory level. I manually corrected the softlink to '../src/x86/ffitarget.h' and then I could continue the build.

Clearly this is not what should happen. Anyone an idea why ffi does that?

(For testing purposes I tried brand new libffi 3.0.10rc8 and it shows exactly the same error).

Regards,
Robert

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#2 lore raw

Re: libffi-native 3.0.9 fails to build on at least x86_64 [solved, problem on my side]

Quoted 4 lines · Robert Schuster

Hi,
I moved the whole OE directory (bitbake, oe, configdir) to a new location and made it available through the same path using a symlink. As it looks OE does not like that at all.

Hi,

that's why I use mount --bind instead of symlinks/hardlinks (ie tmp/work pointing to different partition/md).

Regards,

Signature · 1 line
Martin 'JaMa' Jansa     jabber: [email protected]
#3 lore raw

Re: libffi-native 3.0.9 fails to build on at least x86_64 [solved, problem on my side]

In reply to Robert Schuster

Robert Schuster <[email protected]> [2011-03-08 08:54:55]:

Quoted 3 lines

I moved the whole OE directory (bitbake, oe, configdir) to a new location and made it available through the same path using a symlink. As it looks OE does not like that at all.

In OE manual, in Getting started section there's information about OEBASE/TOPDIR: "You must choose a location with _no symlinks above it_."

It's some problem with handling of symlinks in the path in Python or something like that.

-- ynezz