All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Paul Barker <paul@paulbarker.me.uk>,
	Philip Balister <philip@balister.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: Berkeley DB fails to build
Date: Fri, 24 Jan 2014 18:18:37 +0800	[thread overview]
Message-ID: <52E23DFD.50204@windriver.com> (raw)
In-Reply-To: <CANyK_8f__Lh=1VqfEb7YwNHZ=Cvy561J1aDMYgmoDtQT2w7QBA@mail.gmail.com>


Seems that it is caused by the libtool, but I'm not very sure, we can
reproduce it by:

$ sudo touch /usr/lib/libstdc++.so
$ bitbake db

// Robert

On 01/24/2014 03:01 AM, Paul Barker wrote:
> On 23 January 2014 17:54, Philip Balister <philip@balister.org> wrote:
>> On 01/23/2014 06:51 AM, Carlos Rafael Giani wrote:
>>> Hello,
>>>
>>> I noticed that since the C++ bindings for the berkeley DB were included
>>> in commit 23f29027db73d5759889b48fabdea7f6173217a7 , I cannot build db
>>> anymore.
>>> The error is:
>>>
>>>      /usr/lib/libstdc++.so: file not recognized: File format not recognized
>>>
>>> this is the offending part in the log.do_compile file:
>>
>> What distro is your build machine running? I've this from people using
>> Arch Linux.
>>
>
> I've tracked this down to libtool replacing '-lstdc++' with an
> explicit reference to '/usr/lib/libstdc++.so' before it runs ld. So
> it's libtool not ld at fault here. I did look at the recipe for
> Berkeley db and spotted that it overrides do_configure, allowing the
> shipped copies of libtool and related files to be used rather than
> running the autoreconf stuff that replaces them. That's my
> understanding at least.
>
> At that point I ran away and reverted the commit in question locally
> as libtool terrifies me and I don't need the c++ bindings myself!
>
> Sorry I can't be more help but I hope that points someone in the right
> direction.
>


  parent reply	other threads:[~2014-01-24 10:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 11:51 Berkeley DB fails to build Carlos Rafael Giani
2014-01-23 12:07 ` Robert Yang
2014-01-23 17:54 ` Philip Balister
2014-01-23 19:01   ` Paul Barker
2014-01-24  7:57     ` Iorga, Cristian
2014-01-24 10:18     ` Robert Yang [this message]
2014-01-24 12:08       ` Iorga, Cristian
2014-01-24 20:05         ` Philip Balister
2014-01-24 20:13   ` Carlos Rafael Giani
2014-01-25 11:21     ` Paul Barker

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=52E23DFD.50204@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul@paulbarker.me.uk \
    --cc=philip@balister.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.