Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Robert Schuster <thebohemian@gmx.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: libffi-native 3.0.9 fails to build on at least x86_64 [solved, problem on my side]
Date: Tue, 08 Mar 2011 08:54:55 +0100	[thread overview]
Message-ID: <4D75E0CF.1040209@gmx.net> (raw)
In-Reply-To: <4D75D1A7.9040103@gmx.net>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

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:
> 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
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 270 bytes --]

  reply	other threads:[~2011-03-08  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08  6:50 libffi-native 3.0.9 fails to build on at least x86_64 Robert Schuster
2011-03-08  7:54 ` Robert Schuster [this message]
2011-03-08  8:24   ` libffi-native 3.0.9 fails to build on at least x86_64 [solved, problem on my side] Martin Jansa
2011-03-08  8:36   ` Petr Štetiar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D75E0CF.1040209@gmx.net \
    --to=thebohemian@gmx.net \
    --cc=openembedded-devel@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox