From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Error building gcc-cross
Date: Tue, 5 Jan 2010 10:20:44 -0800 [thread overview]
Message-ID: <20100105182044.GB21048@gmail.com> (raw)
In-Reply-To: <325d766d1001050900y3eef724eu5eb68fc04ec969d7@mail.gmail.com>
On (05/01/10 18:00), martin mangard wrote:
> hello
>
> I wanna run an application which depends on libstdc++.so.5. I use
> the default x86-machine configuration (i486) of the
> "org.openembedded.dev" branch to build the image. The default
> provider for the libstdc++ is in my case "gcc-cross_4.3.4.bb" which
> successfully builds "libstdc++.so.6"
>
> I would like to create a libstdc++ -compatibility package which
> provides an additional binary of the older version of libstdc++.
> I started to play with the gcc-cross recipe. "bitbake -b
> gcc-cross_3.4.4.bb" leaded to the following error.
gcc 3.4 will not build libstdc++.so.5. You have to use gcc 3.3
try to build one of those. They may be rusted over a long time.
You can also take a prebuild ipk
Thanks
-Khem
next prev parent reply other threads:[~2010-01-05 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 17:00 Error building gcc-cross martin mangard
2010-01-05 18:20 ` Khem Raj [this message]
2010-01-06 9:29 ` martin mangard
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=20100105182044.GB21048@gmail.com \
--to=raj.khem@gmail.com \
--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 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.