[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Tinycc-devel] Quick question regarding --with-libgcc
From: |
Thomas Preud'homme |
Subject: |
Re: [Tinycc-devel] Quick question regarding --with-libgcc |
Date: |
Fri, 15 Feb 2013 15:16:13 +0100 |
User-agent: |
KMail/1.13.7 (Linux/3.2.0-4-amd64; KDE/4.8.4; x86_64; ; ) |
Le vendredi 15 février 2013 15:13:25, Christian JULLIEN a écrit :
> Quick question, I thought that recent config work was supposed to solve,
> among other things, the need to pass --with-libgcc (sorry if I'm wrong)
>
> On RPi, while ./configure; make; make test works ROOTB
>
> I still have to use ./configure --with-libgcs if I later do a "make
> install" and want to use tcc as gcc replacement Doing so, I get no error
> while, without --with-libgcc, important ARM eabi functions are missing.
>
> ld uxlisp ...
> tcc: error: undefined symbol '__aeabi_uidiv'
> tcc: error: undefined symbol '__aeabi_uidivmod'
> tcc: error: undefined symbol '__aeabi_idiv'
> tcc: error: undefined symbol '__aeabi_idivmod'
> make[1]: *** [uxlisp] Error 1
>
> Could you please confirm that, at least in case of RPI, I still have to
> pass --with-libgcc
Yes, we still didn't write these functions for libtcc1.a. The nice thing is
that having a libtcc1.a for arm would solve the problem of alloca at the same
time.
>
> Can't we detect (how?) that a platform requires --with-libgcc
Yes but the best fix would be to just fix that specific issue. It shouldn't be
too long.
>
> Christian
Best regards,
Thomas
signature.asc
Description: This is a digitally signed message part.