Richard Guenther wrote:
> On 7/26/07, Joel Sherrill <joel.sherrill@oarcorp.com> wrote:
>> Hi,
>>
>> I am taking a stab at getting libada to build multilib
>> and I just don't seem to grok the magic. I am doing this
>> for RTEMS but the target shouldn't matter as long as
>> it is multilib'ed. Instructions for building GNAT/RTEMS are at
>> http://www.rtems.org/wiki/index.php/RTEMSAda
>>
>> This works well except the Ada libraries are not multilibed.
>>
>> I started by adding --enable-libada --enable-multilib
>> to our configures but that didn't do anything to libada.
>>
>> As best I can tell, the top level configure/Makefile
>> magic is in place for libada to be multilib'ed but I
>> don't even see the multilib directory structure getting
>> created.
>>
>> I have tried to edit libada/configure.ac and libada/Makefile.in
>> based upon the multilib magic I see in other top level
>> directories. So far no luck on even getting the multilib
>> structure generated in the build tree. The attached patch
>> has what I have so far along with the other RTEMS patches to 4.2.0.
>>
>> I would really appreciate some hints. This is just
>> black magic.
>
> Ada is not multilib capable.
What exactly does you mean by this statement? I know the
current build structure doesn't build libada multilib and I
want to fix that. That was what the attached patch attempted
to do.
Is it explicitly disabled somewhere I missed?/
Embedded users whose target CPU doesn't match the
default CPU model end up custom building the
library. I want to get libada multilib'ed so this burden
isn't there.