Bug#710749: libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly
tag #710749 patch tag #710749 moreinfo thanks Hi Aaron, On So 02 Jun 2013 04:29:48 CEST Aaron M. Ucko wrote: Source: libjpeg-turbo Version: 1.3.0-1 Severity: serious Justification: fails to build from source Thanks for addressing #710566 so promptly! Alas, on kfreebsd-amd64, libjpeg-turbo gets past it only to run into another error: when checking for object file format of host system (per logic propagated from acinclude.m4 to configure by way of aclocal.m4), it doesn't know what to make of kFreeBSD and falls back to assuming 32-bit ELF, which naturally fails: checking for object file format of host system... ELF ? configure: WARNING: unexpected host system. assumed that the format is ELF. checking for object file format specifier (NAFLAGS) ... -felf -DELF checking whether the assembler (nasm -felf -DELF) works... yes checking whether the linker accepts assembler output... no configure: error: configuration problem: maybe object file format mismatch. ELF is indeed a reasonable fallback these days, but I'd suggest defaulting to the ELF64 case when the CPU type is x86_64 or amd64 and the OS is unknown. Could you please take a look? Thanks! Attached you find a patch that may hopefully fix the reported issue. Can you please review (as I do not have kfreebsd here to test atm)? Thanks, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb Description: Default to ELF64 object format on 64-bit kFreeBSD Author: Mike Gabriel mike.gabr...@das-netzwerkteam.de --- a/acinclude.m4 +++ b/acinclude.m4 @@ -40,7 +40,7 @@ ;; esac ;; - freebsd* | netbsd* | openbsd*) + kfreebsd* | freebsd* | netbsd* | openbsd*) if echo __ELF__ | $CC -E - | grep __ELF__ /dev/null; then objfmt='BSD-a.out' else pgplEmD_tG2fy.pgp Description: Digitale PGP-Unterschrift
Processed: Re: Bug#710749: libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly
Processing commands for cont...@bugs.debian.org: tag #710749 patch Bug #710749 [src:libjpeg-turbo] libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly Added tag(s) patch. tag #710749 moreinfo Bug #710749 [src:libjpeg-turbo] libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 710749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710749: libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly
Mike Gabriel mike.gabr...@das-netzwerkteam.de writes: Can you please review (as I do not have kfreebsd here to test atm)? I don't have a personal kFreeBSD installation either, so I tested on falla.d.o; your patch is indeed sufficient there, thanks! -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710749: libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly
forwarded #710749 https://sourceforge.net/p/libjpeg-turbo/patches/39/ tag #710749 - moreinfo thanks Hi Aaron, On Di 04 Jun 2013 19:59:09 CEST Aaron M. Ucko wrote: Mike Gabriel mike.gabr...@das-netzwerkteam.de writes: Can you please review (as I do not have kfreebsd here to test atm)? I don't have a personal kFreeBSD installation either, so I tested on falla.d.o; your patch is indeed sufficient there, thanks! Ah, indeed. I am still not used to having all this infrastructure at hand since I have become DD. Preparing -2 upload with the patch included. Patch has been reported upstream. Best, Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabr...@das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb pgpQ0xBb4Ebri.pgp Description: Digitale PGP-Unterschrift
Processed: Re: Bug#710749: libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly
Processing commands for cont...@bugs.debian.org: forwarded #710749 https://sourceforge.net/p/libjpeg-turbo/patches/39/ Bug #710749 [src:libjpeg-turbo] libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly Set Bug forwarded-to-address to 'https://sourceforge.net/p/libjpeg-turbo/patches/39/'. tag #710749 - moreinfo Bug #710749 [src:libjpeg-turbo] libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 710749: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710749 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710749: libjpeg-turbo: FTBFS on kfreebsd-amd64: tries to use 32-bit assembly
Source: libjpeg-turbo Version: 1.3.0-1 Severity: serious Justification: fails to build from source Thanks for addressing #710566 so promptly! Alas, on kfreebsd-amd64, libjpeg-turbo gets past it only to run into another error: when checking for object file format of host system (per logic propagated from acinclude.m4 to configure by way of aclocal.m4), it doesn't know what to make of kFreeBSD and falls back to assuming 32-bit ELF, which naturally fails: checking for object file format of host system... ELF ? configure: WARNING: unexpected host system. assumed that the format is ELF. checking for object file format specifier (NAFLAGS) ... -felf -DELF checking whether the assembler (nasm -felf -DELF) works... yes checking whether the linker accepts assembler output... no configure: error: configuration problem: maybe object file format mismatch. ELF is indeed a reasonable fallback these days, but I'd suggest defaulting to the ELF64 case when the CPU type is x86_64 or amd64 and the OS is unknown. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
