Re: Bug#886175: cross-toolchain-base-ports: Please add support for ia64
On 01/08/2018 03:18 AM, Matthias Klose wrote: Control: tags -1 - patch doesn't work, using gcc-7 7.2.0-19 (...) ia64-linux-gnu-ld.bfd.exe: cannot find -lunwind collect2: error: ld returned 1 exit status Makefile:977: recipe for target 'libgcc_s.so' failed make[5]: *** [libgcc_s.so] Error 1 I *think* this is because libunwind-dev has to be [ia64] as well in debian/control.source.in, but I am not 100% sure yet. Testing now. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#886175: cross-toolchain-base-ports: Please add support for ia64
On 01/25/2018 04:54 PM, James Clarke wrote: I *think* this is because libunwind-dev has to be [ia64] as well in debian/control.source.in, but I am not 100% sure yet. Testing now. Well, if it didn’t work without [ia64], it won’t work with. It currently has [amd64 i386 x32]. My original patch didn't have this limitation. But it still doesn't work anyway which drives me nuts, it did work here and I still have the build log and packages built. I might have used the internal libunwind for gcc. The problem is you need the target’s libunwind-dev, so cross-toolchain-base-ports needs to build it itself, I assume, if the target is ia64. No, I most certainly didn't do it that way. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#886175: cross-toolchain-base-ports: Please add support for ia64
Maybe it needs a stage1 with --disable-libunwind-exceptions? On Thu, Jan 25, 2018 at 11:00 AM, John Paul Adrian Glaubitz wrote: > On 01/25/2018 04:54 PM, James Clarke wrote: >>> >>> I *think* this is because libunwind-dev has to be [ia64] as well in >>> debian/control.source.in, but I am not 100% sure yet. Testing now. >> >> >> Well, if it didn’t work without [ia64], it won’t work with. > > > It currently has [amd64 i386 x32]. My original patch didn't have this > limitation. But it still doesn't work anyway which drives me nuts, it > did work here and I still have the build log and packages built. > > I might have used the internal libunwind for gcc. > >> The problem is you need the target’s libunwind-dev, so >> cross-toolchain-base-ports needs to build it itself, I assume, if the target >> is ia64. > > > No, I most certainly didn't do it that way. > > > Adrian > > -- > .''`. John Paul Adrian Glaubitz > : :' : Debian Developer - glaub...@debian.org > `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de > `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 >
Re: Bug#886175: cross-toolchain-base-ports: Please add support for ia64
On 01/25/2018 05:05 PM, Jason Duerstock wrote: Maybe it needs a stage1 with --disable-libunwind-exceptions? No, I would have remembered that, too. I am checking now whether any part of the ia64 patches for cross-gcc are missing. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Bug#886175: cross-toolchain-base-ports: Please add support for ia64
[sorry if HTML; replying from my phone] > On 25 Jan 2018, at 15:17, John Paul Adrian Glaubitz > wrote: > >> On 01/08/2018 03:18 AM, Matthias Klose wrote: >> Control: tags -1 - patch >> doesn't work, using gcc-7 7.2.0-19 >> (...) >> ia64-linux-gnu-ld.bfd.exe: cannot find -lunwind >> collect2: error: ld returned 1 exit status >> Makefile:977: recipe for target 'libgcc_s.so' failed >> make[5]: *** [libgcc_s.so] Error 1 > > I *think* this is because libunwind-dev has to be [ia64] as well in > debian/control.source.in, but I am not 100% sure yet. Testing now. Well, if it didn’t work without [ia64], it won’t work with. The problem is you need the target’s libunwind-dev, so cross-toolchain-base-ports needs to build it itself, I assume, if the target is ia64. James
