Re: Bug#212912: gcc-3.3: [alpha] Linux linker/loader does not support -mieee-conformant
[CCing to debian-alpha] As Chris (currently listed as package maintainer for gcc alpha) seems to be away, I'll ask on debian-alpha (Falk?), if this patch should be included. In that case the documentation should be changed to explicitely mention Debian instead of Linux. Tyson Whitehead writes: On Sunday 28 September 2003 14:54, you wrote: did you submit this patch upstream? If not, please can you do and attach the upstream PR? Thanks, Matthias Hi Matthias. I'm not quite sure by what you mean be upstream. Is it a Debian thing or a GNU thing. If it's the later, I posted a message on GNU GCC mailing list about it a month or two ago. It didn't go anywhere. Richard Henderson (the Alpha fellow from Red Hat) said he wouldn't accept it into the general GCC unless all users of GCC (i.e. BSD, etc) came forward and said they wanted it. He also gave three reasons why he personally didn't like it: 1- The default under DEC C is to not IEEE compliance 2- IEEE compliance leads to 'severe' performance penalties 3- The vast majority of SIGFPEs are due to unitialized data reads While one and three might be true (timing tests show that two is just plain wrong), they miss the point of the patch. The patch is intended to help achieve the goal of having as many packages as possible run on the Debian Alpha distribution as possible (without needing to specify Alpha specific flags). This means matching the GNU defaults on the other Debian architectures, and that just happens to be IEEE compliant libraries and code. Thanks -T -- Tyson Whitehead ([EMAIL PROTECTED] -- WSC-) Computer EngineerDept. of Applied Mathematics, Graduate Student- Applied MathematicsUniversity of Western Ontario, GnuPG Key ID# 0x8A2AB5D8 London, Ontario, Canada
libc6 vs. libc6.1/testing rather strange (broken ?)
Hello, I try to run testing (upgraded from woody) but with lots of software I like to install I get: xmlto: Depends: libc6.1 (= 2.3.1-1) but 2.2.5-11.5 is to be installed Depends: xsltproc (= 1.0.29) but 1.0.16-0.1 is to be installed Depends: libpaper-utils but it is not going to be installed Depends: libxml2-utils but it is not going to be installed Especially the libc6.1 part reappears with a lot of packages. Why do I see this packages, if I cannot install them? I cannot get a newer glibc to satisfy this dependency. Yesterday I came around an example which might explain part of the problem: dcraw I got the source, compiled it and tried to install it, however: Depends: libc6 (= 2.3.2-1) [EMAIL PROTECTED]:/scratch/build/debian/dcraw-4.88.orig$ apt-cache show libc6 [EMAIL PROTECTED]:/scratch/build/debian/dcraw-4.88.orig$ apt-cache show libc6.1 Package: libc6.1 ... [EMAIL PROTECTED]:/scratch/build/debian/dcraw-4.88.orig$ dpkg -l libc6.1 ... ii libc6.12.2.5-11.5 GNU C Library: Shared libraries and Timezone Does this dependency have to read: Depends: libc6 (= 2.3.2-1) | libc6.1 (= 2.3.2-1) Should I fill bugs against such packages? Is the version numbering for libc6 and libc6.1 the same, i.e. do I have to wait for libc6.1 2.3.2-1 before I can use dcraw? (I removed the versioned dependency in this case but have not yet tried dcraw). Are these bugs in packages in testing? I though, either I can install a package including its dependencies, or I should get Sorry, there are no newer packages available which means that the woody version is the same as the testing one. Before starting to file bugs I just want to clearify that this not an oversight on my part. Greetings Helge -- Helge Kreutzmann, Dipl.-Phys. [EMAIL PROTECTED] gpg signed mail preferredgpg-key: finger [EMAIL PROTECTED] 64bit GNU powered http://www.itp.uni-hannover.de/~kreutzm Help keep free software libre: http://www.freepatents.org/ pgp8LzL0TYh2M.pgp Description: PGP signature
Re: libc6 vs. libc6.1/testing rather strange (broken ?)
Helge Kreutzmann [EMAIL PROTECTED] writes:
Yesterday I came around an example which might explain part of the
problem: dcraw
I got the source, compiled it and tried to install it, however:
Depends: libc6 (= 2.3.2-1)
Does this dependency have to read:
Depends: libc6 (= 2.3.2-1) | libc6.1 (= 2.3.2-1)
Should I fill bugs against such packages?
Yes. They should usually just use
Depends: ${shlibs:Depends}
or your version if they really need a specific libc version.
Is the version numbering for libc6 and libc6.1 the same, i.e. do I have to
wait
for libc6.1 2.3.2-1 before I can use dcraw?
Yes, it's really the same package, only for weird historical reason
the package is called libc6.1 on Alpha and IA64 and libc6 everywhere else.
The explicit dependency in dcraw is probably just a mistake, though,
there is basically no reason why a source would not work with older
glibcs.
(I removed the versioned dependency in this case but have not yet
tried dcraw).
BTW, are you trying to hook up a digital camera to your Alpha? I'd be
interested in experiences :)
--
Falk
Debian Install Compaq Alpha XP1000
Hello I am trying to install debian in a Compaq ALpha XP 1000. I am booting through the SRM console using a CD made with jigdo. This machine has 2 SCSI disks and the systams freezes when probing SCSI hardware. Can someone please help Thanks
Re: Debian Install Compaq Alpha XP1000
Dead Scsi Drive? Mine did this until I removed teh culprit drive. Try these links for more help... http://www.tux.org/~joel/xp1000.html http://h18002.www1.hp.com/alphaserver/workstations/retired/xpseries/xp1000/index.html Get the PDF of the SRM console commands if you do not have it yet. KeithG Marcio Gustavo Di Vernieri Cuppari wrote: Hello I am trying to install debian in a Compaq ALpha XP 1000. I am booting through the SRM console using a CD made with jigdo. This machine has 2 SCSI disks and the systams freezes when probing SCSI hardware. Can someone please help Thanks
Re: Debian Install Compaq Alpha XP1000
* Marcio Gustavo Di Vernieri Cuppari [EMAIL PROTECTED] wrote: I am trying to install debian in a Compaq ALpha XP 1000. I am booting through the SRM console using a CD made with jigdo. This machine has 2 SCSI disks and the systams freezes when probing SCSI hardware. Which kernel are you using? -- - nt
