Brokenness for Mips32 Little?

Brokenness for Mips32 Little?

[ANDY KENNEDY]

[INFO ]  =================================================================
[INFO ]  Installing ISL for host
[INFO ]  Installing ISL for host: done in 17.14s (at 01:00)
[INFO ]  =================================================================
[INFO ]  Installing CLooG for host
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:799:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:906:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:963:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1093:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1215:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1634:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1697:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1772:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1785:32: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1821:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:269:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/domain.c:1822:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:532:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:544:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:556:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:703:2: error: unknown type name 'isl_int'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:703:20: error: 'isl_int' undeclared (first use in this function)
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:703:29: error: expected expression before ')' token
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:704:10: error: expected ';' before 'v'
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:706:15: error: 'v' undeclared (first use in this function)
[ERROR]    gmake[2]: *** [libcloog_isl_la-domain.lo] Error 1
[ERROR]    /home/me/crosstool-ng/.build/src/cloog-0.18.0/source/isl/constraints.c:899:2: error: unknown type name 'isl_int'
[ERROR]    gmake[2]: *** [libcloog_isl_la-constraints.lo] Error 1
[ERROR]    gmake[1]: *** [all-recursive] Error 1


Workaround for this was to select ISL 1.12.0.  Is this expected?

Thanks,
Andy

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Brokenness for Mips32 Little?

[Bryan Hundven]

Andy,

On Mon, Apr 27, 2015 at 3:32 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
...
> Workaround for this was to select ISL 1.12.0.  Is this expected?
(I think you mean 0.12.2)

Yes, I have committed a change to add isl 0.14, but I need to make a
new commit that has gcc select the right companion libs needed, as
cloog is no longer needed with >=5.1.0 and <=4.9.2 isl-0.12.2 needs to
be select as well as cloog-isl.

Sorry for the breakage. That's my fault. Luckily, it's temporary.

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq

RE: Brokenness for Mips32 Little?

[ANDY KENNEDY]

> Sorry for the breakage. That's my fault. Luckily, it's temporary.

No problem.  Easy workaround.

Thanks!

Andy

> 
> -Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Brokenness for Mips32 Little?

[Bryan Hundven]

Andy,

On Mon, Apr 27, 2015 at 3:38 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>> Sorry for the breakage. That's my fault. Luckily, it's temporary.
> No problem.  Easy workaround.

As a side note:
https://sourceware.org/ml/crossgcc/2015-04/msg00003.html

Have you seen problems like this building mipsel?

Thanks,

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq

RE: Brokenness for Mips32 Little?

[ANDY KENNEDY]

> -----Original Message-----
> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
> Sent: Monday, April 27, 2015 5:42 PM
> To: ANDY KENNEDY
> Cc: crossgcc@sourceware.org
> Subject: Re: Brokenness for Mips32 Little?
> 
> Andy,
> 
> On Mon, Apr 27, 2015 at 3:38 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
> >> Sorry for the breakage. That's my fault. Luckily, it's temporary.
> > No problem.  Easy workaround.
> 
> As a side note:
> https://sourceware.org/ml/crossgcc/2015-04/msg00003.html
> 
> Have you seen problems like this building mipsel?
> 
> Thanks,
> 
> -Bryan

Not like that.  I have seen other issues (when attempting from 1.18.0) but
the tip seems to build without much issues (with the noted exception).

When doing 1.18.0 (against a newlib) I got strange conflicts and configure
reported that xgcc (I think) couldn't create executables.  I didn't dig too deep
as I was in a hurry and figured I should grab a later release (or in this case
the tip).

Sorry man,
Andy

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Brokenness for Mips32 Little?

[Bryan Hundven]

Andy,

On Mon, Apr 27, 2015 at 3:49 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>> -----Original Message-----
>> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
>> Sent: Monday, April 27, 2015 5:42 PM
>> To: ANDY KENNEDY
>> Cc: crossgcc@sourceware.org
>> Subject: Re: Brokenness for Mips32 Little?
>>
>> Andy,
>>
>> On Mon, Apr 27, 2015 at 3:38 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>> >> Sorry for the breakage. That's my fault. Luckily, it's temporary.
>> > No problem.  Easy workaround.
>>
>> As a side note:
>> https://sourceware.org/ml/crossgcc/2015-04/msg00003.html
>>
>> Have you seen problems like this building mipsel?
>>
>> Thanks,
>>
>> -Bryan
>
> Not like that.  I have seen other issues (when attempting from 1.18.0) but
> the tip seems to build without much issues (with the noted exception).
>
> When doing 1.18.0 (against a newlib) I got strange conflicts and configure
> reported that xgcc (I think) couldn't create executables.  I didn't dig too deep
> as I was in a hurry and figured I should grab a later release (or in this case
> the tip).
>
> Sorry man,
> Andy

Hrm, they only thing different here is that he is turning on ssp,
which I'm guessing you have disabled.

Can you repro that?

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq

RE: Brokenness for Mips32 Little?

[ANDY KENNEDY]

> -----Original Message-----
> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
> Sent: Monday, April 27, 2015 5:51 PM
> To: ANDY KENNEDY
> Cc: crossgcc@sourceware.org
> Subject: Re: Brokenness for Mips32 Little?
> 
> Andy,
> 
> On Mon, Apr 27, 2015 at 3:49 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
> >> -----Original Message-----
> >> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
> >> Sent: Monday, April 27, 2015 5:42 PM
> >> To: ANDY KENNEDY
> >> Cc: crossgcc@sourceware.org
> >> Subject: Re: Brokenness for Mips32 Little?
> >>
> >> Andy,
> >>
> >> On Mon, Apr 27, 2015 at 3:38 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
> >> >> Sorry for the breakage. That's my fault. Luckily, it's temporary.
> >> > No problem.  Easy workaround.
> >>
> >> As a side note:
> >> https://sourceware.org/ml/crossgcc/2015-04/msg00003.html
> >>
> >> Have you seen problems like this building mipsel?
> >>
> >> Thanks,
> >>
> >> -Bryan
> >
> > Not like that.  I have seen other issues (when attempting from 1.18.0) but
> > the tip seems to build without much issues (with the noted exception).
> >
> > When doing 1.18.0 (against a newlib) I got strange conflicts and configure
> > reported that xgcc (I think) couldn't create executables.  I didn't dig too deep
> > as I was in a hurry and figured I should grab a later release (or in this case
> > the tip).
> >
> > Sorry man,
> > Andy
> 
> Hrm, they only thing different here is that he is turning on ssp,
> which I'm guessing you have disabled.
> 
> Can you repro that?
> 
> -Bryan

No fail.  Adding  libssp had no change.

--
For unsubscribe information see http://sourceware.org/lists.html#faq

Re: Brokenness for Mips32 Little?

[Bryan Hundven]

Andy,

On Mon, Apr 27, 2015 at 4:06 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>> -----Original Message-----
>> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
>> Sent: Monday, April 27, 2015 5:51 PM
>> To: ANDY KENNEDY
>> Cc: crossgcc@sourceware.org
>> Subject: Re: Brokenness for Mips32 Little?
>>
>> Andy,
>>
>> On Mon, Apr 27, 2015 at 3:49 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>> >> -----Original Message-----
>> >> From: Bryan Hundven [mailto:bryanhundven@gmail.com]
>> >> Sent: Monday, April 27, 2015 5:42 PM
>> >> To: ANDY KENNEDY
>> >> Cc: crossgcc@sourceware.org
>> >> Subject: Re: Brokenness for Mips32 Little?
>> >>
>> >> Andy,
>> >>
>> >> On Mon, Apr 27, 2015 at 3:38 PM, ANDY KENNEDY <ANDY.KENNEDY@adtran.com> wrote:
>> >> >> Sorry for the breakage. That's my fault. Luckily, it's temporary.
>> >> > No problem.  Easy workaround.
>> >>
>> >> As a side note:
>> >> https://sourceware.org/ml/crossgcc/2015-04/msg00003.html
>> >>
>> >> Have you seen problems like this building mipsel?
>> >>
>> >> Thanks,
>> >>
>> >> -Bryan
>> >
>> > Not like that.  I have seen other issues (when attempting from 1.18.0) but
>> > the tip seems to build without much issues (with the noted exception).
>> >
>> > When doing 1.18.0 (against a newlib) I got strange conflicts and configure
>> > reported that xgcc (I think) couldn't create executables.  I didn't dig too deep
>> > as I was in a hurry and figured I should grab a later release (or in this case
>> > the tip).
>> >
>> > Sorry man,
>> > Andy
>>
>> Hrm, they only thing different here is that he is turning on ssp,
>> which I'm guessing you have disabled.
>>
>> Can you repro that?
>>
>> -Bryan
>
> No fail.  Adding  libssp had no change.

Thanks for testing!

-Bryan

--
For unsubscribe information see http://sourceware.org/lists.html#faq