On 28.11.2015 07:12, Helmut Grohne wrote:
On Sat, Nov 28, 2015 at 02:58:31AM +0100, Matthias Klose wrote:
No. Why would you handle hppa as a secondary or ternary architecture? You
need the hppa64 cross compiler to bootstrap hppa. Other architectures
require a multilib enabled compiler to bootstrap the architecture, however
hppa/hppa64 isn't multilib enabled. So maybe you don't have this target
enabled? Fyi, there is #800729 trying to address this issue properly and
not working around it. Unfortunately no reply yet.
I understand that you do need hppa64 cross compilers to bootstrap the
hppa port. That is why the proposed patch leaves with_hppa64 enabled
when setting hppa as a cross target.
What I do not understand is why I suddenly need hppa64 cross compilers
to bootstrap amd64, i386 or x32. This wasn't required a week ago. Where
does this new requirement come from?
And it wasn't required before. gcc-5-hppa64-linux-gnu is now in the archive for
x86 hosts.
Also why do the generated Build-Depends for targets amd64, i386 and x32
not list binutils-hppa64-linux-gnu when the build ends up using it. This
is inconsistent.
Sure, is this the only problem building a complete x86 stand alone cross
compiler?
