Eric Botcazou wrote:
>> Is it just a bug for me to generate LIBGNAT_TARGET_PAIRS in a way that
>> has superfluous spaces (whether leading, trailing or embedded), or shall I
>> send a patch to add a $(strip) to the right-hand side of the ifeq
>> comparison? Or perhaps we should do
>>
>> LIBGNAT_T
> Is it just a bug for me to generate LIBGNAT_TARGET_PAIRS in a way that
> has superfluous spaces (whether leading, trailing or embedded), or shall I
> send a patch to add a $(strip) to the right-hand side of the ifeq
> comparison? Or perhaps we should do
>
> LIBGNAT_TARGET_PAIRS:=$(strip $(LIBG
Dave Korn wrote:
> Eric Botcazou wrote:
>> Your .diff contains this
>>
>> + EH_MECHANISM=-gcc
>>
>> so it looks as though the base compiler was SJLJ.
>
> Ah, bingo! Thanks Eric; yes, I have a recent build of an SJLJ Gnat from
> HEAD lying around my PATH ahead of my old 4.3.2-with-ZCX. Getting
Eric Botcazou wrote:
>> That's what I am doing, kind of, just the other way round. In 4.3.2 I
>> compiled the existing port and switched it over to ZCX, and it worked well
>> enough to pass most of the testsuite, including EH. Now I'm changing the
>> target pairs on top of that and suddenly it'
> That's what I am doing, kind of, just the other way round. In 4.3.2 I
> compiled the existing port and switched it over to ZCX, and it worked well
> enough to pass most of the testsuite, including EH. Now I'm changing the
> target pairs on top of that and suddenly it's complaining, which is w
Eric Botcazou wrote:
>> I was planning to do whatever's needed to make it work on windows. I
>> don't think this line cause the build failure, because it certainly
>> appeared to work, when I tried it on 4.3.2 (without all the other changes
>> to the target pair list); but for some reason the sa
> I was planning to do whatever's needed to make it work on windows. I
> don't think this line cause the build failure, because it certainly
> appeared to work, when I tried it on 4.3.2 (without all the other changes
> to the target pair list); but for some reason the same trick isn't working
>
Laurent GUERBY wrote:
> On Tue, 2009-09-08 at 07:21 +0100, Dave Korn wrote:
>> EH_MECHANISM=-gcc
>
> I don't think this is correct for windows targets:
> EH_MECHANISM must be left to its original empty
> definition to get sjlj exceptions which are the only
> one working on windows IIRC.
I was
On Tue, 2009-09-08 at 07:21 +0100, Dave Korn wrote:
> EH_MECHANISM=-gcc
I don't think this is correct for windows targets:
EH_MECHANISM must be left to its original empty
definition to get sjlj exceptions which are the only
one working on windows IIRC.
Sincerely,
Laurent
