John Paul Adrian Glaubitz dixit:
>On 01/12/2014 02:43 AM, Thorsten Glaser wrote:
>> Hm, yes, the faulty build was on elgar, which did have
>> hardware issues.
>
>You're not particularly fond of original m68k hardware, are you? :)
Nah, I’ve got no opinion on them, this was a neutral fact.
I had to
On 01/12/2014 02:43 AM, Thorsten Glaser wrote:
> Hm, yes, the faulty build was on elgar, which did have
> hardware issues.
You're not particularly fond of original m68k hardware, are you? :)
elgar runs like a tank now, never had any issues again unless I
messed with it. Builds packages 24/7, sitt
Jakub Wilk dixit:
> And earlier in the build log[0], there's indeed:
> | checking for signed size type... unknown
>
> I can't think why would this check fail... But anyway, later versions built
> successfully[1][2], so I think this bug should be closed.
Hm, yes, the faulty build was on elgar, whi
close 728098
thanks
Hi Jakub!
On 01/12/2014 02:32 AM, Jakub Wilk wrote:
> I can't think why would this check fail... But anyway, later versions
> built successfully[1][2], so I think this bug should be closed.
Thank you very much for following up on this. Indeed, tiff now builds
fine on m68k and
[I'm not the maintainer of this package.]
* John Paul Adrian Glaubitz , 2013-10-28, 13:39:
tiff currently FTBFS on m68k since the configure script doesn't know
anything about the host architecture [1].
The interesting bits from the build log are:
==
5 matches
Mail list logo
