Maybe it needs a stage1 with --disable-libunwind-exceptions?
On Thu, Jan 25, 2018 at 11:00 AM, John Paul Adrian Glaubitz
> 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.
> .''`. 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
Mailing list: https://launchpad.net/~cross-toolchain-base-devs
Post to : firstname.lastname@example.org
Unsubscribe : https://launchpad.net/~cross-toolchain-base-devs
More help : https://help.launchpad.net/ListHelp