* how to build multi arch libstdc++
@ 2013-09-07 4:11 Zhang hw
2013-09-07 8:52 ` Jonathan Wakely
0 siblings, 1 reply; 4+ messages in thread
From: Zhang hw @ 2013-09-07 4:11 UTC (permalink / raw)
To: gcc-help
Hello , everybody!
I have compiled and installed a gcc-4.8.1 with configure
--build=x86_64-redhat-linux-gnu.There is a app need 32bit libstdc++
now , but there is nothing in "lib" directory , how to build and
install it?
I have compiled with xxx/libstdc++-v3/configure
--target=i686-redhat-linux-gnu and returned success , but after
installed it , I've got only the libraries in directory "lib64" ,
there was nothing in "lib" directory?
Can I compile and install a 32bit libstdc++ with parameters changing
for configure and make install? Or , shall I build a cross compiler
first?
Thanks!!
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to build multi arch libstdc++
2013-09-07 4:11 how to build multi arch libstdc++ Zhang hw
@ 2013-09-07 8:52 ` Jonathan Wakely
2013-09-07 11:03 ` Zhang hw
0 siblings, 1 reply; 4+ messages in thread
From: Jonathan Wakely @ 2013-09-07 8:52 UTC (permalink / raw)
To: Zhang hw; +Cc: gcc-help
On 7 September 2013 05:11, Zhang hw wrote:
> Hello , everybody!
> I have compiled and installed a gcc-4.8.1 with configure
> --build=x86_64-redhat-linux-gnu.There is a app need 32bit libstdc++
> now , but there is nothing in "lib" directory , how to build and
> install it?
x86_64-*-linux-gnu always builds a multilib compiler unless you use
--disable-multilib
> I have compiled with xxx/libstdc++-v3/configure
> --target=i686-redhat-linux-gnu and returned success , but after
> installed it , I've got only the libraries in directory "lib64" ,
> there was nothing in "lib" directory?
That doesn't make sense, i686-*-linux-gnu is a 32-bit non-multilib target.
> Can I compile and install a 32bit libstdc++ with parameters changing
> for configure and make install? Or , shall I build a cross compiler
> first?
As I said, just build on x86_64 without --disable-multilib
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to build multi arch libstdc++
2013-09-07 8:52 ` Jonathan Wakely
@ 2013-09-07 11:03 ` Zhang hw
2013-09-07 16:01 ` Jonathan Wakely
0 siblings, 1 reply; 4+ messages in thread
From: Zhang hw @ 2013-09-07 11:03 UTC (permalink / raw)
To: Jonathan Wakely; +Cc: gcc-help
Thank jwakely!
yes , I've compiled my x86_64 with "configure --disable-multilib" for
some compile errors. Is thers a simple way to build the 32bit lib on
my amd64 env now, against re-configure and re-build the whole gcc? It
need 2-3 hours to compile the gcc on my computer.
By the way , I downloaded a precompiled lib package from the fc
website for temporary using , and it looked like worked well.
2013/9/7, Jonathan Wakely <jwakely.gcc@gmail.com>:
> On 7 September 2013 05:11, Zhang hw wrote:
>> Hello , everybody!
>> I have compiled and installed a gcc-4.8.1 with configure
>> --build=x86_64-redhat-linux-gnu.There is a app need 32bit libstdc++
>> now , but there is nothing in "lib" directory , how to build and
>> install it?
>
> x86_64-*-linux-gnu always builds a multilib compiler unless you use
> --disable-multilib
>
>> I have compiled with xxx/libstdc++-v3/configure
>> --target=i686-redhat-linux-gnu and returned success , but after
>> installed it , I've got only the libraries in directory "lib64" ,
>> there was nothing in "lib" directory?
>
> That doesn't make sense, i686-*-linux-gnu is a 32-bit non-multilib target.
>
>> Can I compile and install a 32bit libstdc++ with parameters changing
>> for configure and make install? Or , shall I build a cross compiler
>> first?
>
> As I said, just build on x86_64 without --disable-multilib
>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: how to build multi arch libstdc++
2013-09-07 11:03 ` Zhang hw
@ 2013-09-07 16:01 ` Jonathan Wakely
0 siblings, 0 replies; 4+ messages in thread
From: Jonathan Wakely @ 2013-09-07 16:01 UTC (permalink / raw)
To: Zhang hw; +Cc: gcc-help
On Sep 7, 2013 12:03 PM, "Zhang hw" wrote:
>
> Thank jwakely!
> yes , I've compiled my x86_64 with "configure --disable-multilib" for
> some compile errors.
That would have been helpful to mention!
If you want to build multilib then don't disable multilib.
> Is thers a simple way to build the 32bit lib on
> my amd64 env now, against re-configure and re-build the whole gcc? It
> need 2-3 hours to compile the gcc on my computer.
No, you need to reconfigure. Use 'make -j2' or similar to speed it up.
See http://gcc.gnu.org/wiki/FAQ#gnu_stubs-32.h if that solves your errors.
> By the way , I downloaded a precompiled lib package from the fc
> website for temporary using , and it looked like worked well.
>
> 2013/9/7, Jonathan Wakely <jwakely.gcc@gmail.com>:
> > On 7 September 2013 05:11, Zhang hw wrote:
> >> Hello , everybody!
> >> I have compiled and installed a gcc-4.8.1 with configure
> >> --build=x86_64-redhat-linux-gnu.There is a app need 32bit libstdc++
> >> now , but there is nothing in "lib" directory , how to build and
> >> install it?
> >
> > x86_64-*-linux-gnu always builds a multilib compiler unless you use
> > --disable-multilib
> >
> >> I have compiled with xxx/libstdc++-v3/configure
> >> --target=i686-redhat-linux-gnu and returned success , but after
> >> installed it , I've got only the libraries in directory "lib64" ,
> >> there was nothing in "lib" directory?
> >
> > That doesn't make sense, i686-*-linux-gnu is a 32-bit non-multilib target.
> >
> >> Can I compile and install a 32bit libstdc++ with parameters changing
> >> for configure and make install? Or , shall I build a cross compiler
> >> first?
> >
> > As I said, just build on x86_64 without --disable-multilib
> >
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-09-07 16:01 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-09-07 4:11 how to build multi arch libstdc++ Zhang hw
2013-09-07 8:52 ` Jonathan Wakely
2013-09-07 11:03 ` Zhang hw
2013-09-07 16:01 ` Jonathan Wakely
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).