Bug#376159: Open21xx Bug Report
Good catch. Putting the EOF in the character buffer doesn't sound like a
bright thing to do either. I'll review the whole section and get a release
Thanks for you help,
From: Matej Vela [mailto:firstname.lastname@example.org]
Sent: Monday, August 13, 2007 4:37 AM
To: Michel Dänzer
Cc: email@example.com; Paul Wise; Keith Clifford; debian-powerpc;
Subject: Re: Bug#376159: Open21xx Bug Report
Michel Dänzer <firstname.lastname@example.org> writes:
> On Sat, 2007-08-11 at 15:55 +0000, Paul Wise wrote:
>> Looks like it never built/worked on those platforms:
>> Hopefully someone on the porter lists will be able to help (CCed).
>> If no-one replies, I'm willing to use the Debian development machines to
>> help you fix this issue. I'm not familiar with the open21xx source or
>> package, and I have little time for Debian stuff, so I'll need some
>> direction and hints about this.
> Given the list of failing architectures, I think the most likely cause
> is some code relying on char being signed by default. And indeed,
> building the as21 directory with -fsigned-char makes it build for me.
You're right, as21/cpp.c was comparing a plain char to EOF. I've
uploaded the attached patch, let's see if it works.