Hi Jing Yu,
> 2011-05-08 Jing Yu
>
> * configure.ac: Skip target-libiberty for
arm*-*-linux-androideabi.
> * configure: Regenerated.
Approved - please apply.
Cheers
Nick
ARM maintainers,
Is it ok to skip building target-libiberty for arm*-*-linux-androideabi target?
http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02208.html
Thanks,
Jing
On Fri, Jun 3, 2011 at 11:26 AM, DJ Delorie wrote:
>
>> Ping.
>> http://gcc.gnu.org/ml/gcc-patches/2011-0
> Ping.
> http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02208.html
>
> > I don't have the bandwidth to work on the ideal patch. Thus I am
> > wondering if we can skip target-libiberty for androideabi target
> > before the ideal patch is out.
Target-specific changes in the build are up to the targ
Ping.
http://gcc.gnu.org/ml/gcc-patches/2011-05/msg02208.html
On Tue, May 31, 2011 at 11:32 AM, Jing Yu wrote:
> Based on discussion on another thread
> (http://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg06627.html),
> what Joseph recommended was ripping out all support for building
> libibe
Based on discussion on another thread
(http://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg06627.html),
what Joseph recommended was ripping out all support for building
libiberty for the target side as it is not needed. Thus I doubt
skipping target-libiberty for all targets is acceptable.
I don'
Building gcc-4.6 arm android toolchain fails because of an
incompatible function definition between libiberty and bionic.
Thanking Joseph, I have learned that "there's no such thing as a
target libiberty" and we should rip all the target-libiberty rules
out. I don't know if someone is working on
