Thanks for the insight. I'll compile it both ways, signed-char and unsigned-char to make sure everything works before I do a new release.
Cheers, Keith -----Original Message----- From: Michel Dänzer [mailto:[EMAIL PROTECTED] Sent: Monday, August 13, 2007 3:41 AM To: Paul Wise Cc: Keith Clifford; [EMAIL PROTECTED]; debian-powerpc; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: Open21xx Bug Report On Sat, 2007-08-11 at 15:55 +0000, Paul Wise wrote: > On Sat, 2007-08-11 at 08:19 -0700, Keith Clifford wrote: > > > This is the first time these problems have been brought to my attention. > > Unfortunately, I don't have access to the platforms that the build is > > failing on. So, unless someone is willing to step up and help me > > troubleshoot the problems on those platforms, there is little I can do. > > > > I guess you'll have to remove Open21xx from Debian. > > Looks like it never built/worked on those platforms: > > http://buildd.debian.org/build.php?arch=&pkg=open21xx > > 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. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
