public inbox for gentoo-portage-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Haubenwallner <haubi@gentoo.org>
To: gentoo-portage-dev <gentoo-portage-dev@lists.gentoo.org>
Subject: Re: [gentoo-portage-dev] install_qa_check() for hppa64 and ia64-hpux
Date: Thu, 16 Jul 2009 10:15:50 +0200	[thread overview]
Message-ID: <1247732150.1554.92.camel@salomon-22> (raw)
In-Reply-To: <200907151026.10126.vapier@gentoo.org>

On Wed, 2009-07-15 at 10:26 -0400, Mike Frysinger wrote:
> On Tuesday 14 July 2009 04:40:14 Michael Haubenwallner wrote:
> > have noticed that the "Evaluating misc gcc warnings" QA check does not
> > know about "hppa64" cpu in bin/misc-functions.sh:
> > alpha*|hppa64*|ia64*|powerpc64*|mips64*|sparc64*|sparcv9*|x86_64*)
> > gentoo_bug=yes ;; esac
> 
> looks fine to me -- feel free to add it.  or if you cant, i can throw it in if 
> people dont beat me to it.

Should be possible for me, thank you!

> 
> > This was while I was looking why this check blocked merging of gcc-4.3.3
> > on the 32bit platform CHOST=ia64-hp-hpux* due to:
> >         warning: implicit declaration of function 'strtok_r'
> >
> > Yes, ia64-hp-hpux* is a multilib platform with 32bit default - the 64bit
> > default would have CHOST=ia64w-hp-hpux*.
> 
> the hpux guys created their own 32bit ia64 ELF ABI !?  or they're using x86 
> emulation ?  both are wicked stupid ...

Exactly, it is a 32bit ia64 ELF ABI, not x86 (would have different byte
order, and would suggest HP-UX runs on x86 ;) ). It is the default
compiler output (both aCC and gcc) for backwards compatibility.
Did have a discussion with Steve Ellcey (gcc-dev at HP) to add
'ia64w-hp-hpux*' for 64bit default, and leave 'ia64-hp-hpux*' for 32bit
(both multilib-able).

> 
> > As we do not do multilib in Prefix, "ia64-hp-hpux*" is 32bit, and I want
> > to hear your thoughts about this additional line there:
> >             case ${CHOST} in
> >         +      ia64-hp-hpux*) ;; # multilib with 32bit default, 64bit is
> > ia64w-hp-hpux*
> > alpha*|hppa64*|ia64*|powerpc64*|mips64*|sparc64*|sparcv9*|x86_64*)
> > gentoo_bug=yes ;; esac

> the check is to catch the majority of users, and it does.  i dont want to go 
> down this rabbit hole.  about we just fix the source code in question and call 
> it a day.

AFAICS, it is the only exception to "*64*" being 64bit.
But ok, seems I'll have to mask gcc-4.3 even for hppa-hpux anyway.

/haubi/
-- 
Michael Haubenwallner
Gentoo on a different level




  reply	other threads:[~2009-07-16  8:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-14  8:40 [gentoo-portage-dev] install_qa_check() for hppa64 and ia64-hpux Michael Haubenwallner
2009-07-15 14:26 ` Mike Frysinger
2009-07-16  8:15   ` Michael Haubenwallner [this message]
2009-07-16  8:31     ` Michael Haubenwallner
2009-07-16 17:45     ` Mike Frysinger
2009-07-30 13:32       ` Michael Haubenwallner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1247732150.1554.92.camel@salomon-22 \
    --to=haubi@gentoo.org \
    --cc=gentoo-portage-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox