public inbox for libffi-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Anthony Green <green@moxielogic.com>
To: Shigeharu TAKENO <shige@iee.niit.ac.jp>
Cc: "libffi-discuss@sourceware.org" <libffi-discuss@sourceware.org>
Subject: Re: problem for UltraSPARC-IIi
Date: Sat, 09 Nov 2013 11:19:00 -0000	[thread overview]
Message-ID: <CACxje58FRxxer8S07F4k2OHnUSL95_-i_BUj3_dth-P+NJbzbA@mail.gmail.com> (raw)
In-Reply-To: <201311090649.rA96nFRF002304@pc98tak.iee.niit.ac.jp>

Thanks!  The file to fix here is actually m4/ax_gcc_archflag.m4, which
comes from the upstream autoconf-archive project.  I've made the
change here and rebuilt configure.  I've also reported the bug along
with your patch to the autoconf-archive project.

AG

On Sat, Nov 9, 2013 at 1:49 AM, Shigeharu TAKENO <shige@iee.niit.ac.jp> wrote:
> shige 11/09 2013
> ----------------
>
> I use Solaris 10 on an UltraSPARC-IIi machine. The configure
> script of libffi-3.0.13 recognizes the cpu to ultrasparc3, but it
> is not correct because "UltraSPARC-IIi" should be identified as
> ultrasparc (IIi is not III). The following patch may fix the
> problem.
>
> ----- From here -----
> diff -uN libffi-3.0.13/configure.ORG libffi-3.0.13/configure
> --- libffi-3.0.13/configure.ORG 2013-03-18 07:36:19.000000000 +0900
> +++ libffi-3.0.13/configure     2013-11-08 18:55:24.797500000 +0900
> @@ -12811,7 +12811,7 @@
>
>
>       cputype=`(((grep cpu /proc/cpuinfo | cut -d: -f2) ; ($PRTDIAG -v |grep -i sparc) ; grep -i cpu /var/run/dmesg.boot ) | head -n 1) 2> /dev/null`
> -     cputype=`echo "$cputype" | tr -d ' -' |tr $as_cr_LETTERS $as_cr_letters`
> +     cputype=`echo "$cputype" | tr -d ' -' | sed 's/SPARCIIi/SPARCII/' |tr $as_cr_LETTERS $as_cr_letters`
>       case $cputype in
>           *ultrasparciv*) ax_gcc_arch="ultrasparc4 ultrasparc3 ultrasparc v9" ;;
>           *ultrasparciii*) ax_gcc_arch="ultrasparc3 ultrasparc v9" ;;
> ----- To here -----
>
> +========================================================+
>  Shigeharu TAKENO     NIigata Institute of Technology
>                        kashiwazaki,Niigata 945-1195 JAPAN
>  shige@iee.niit.ac.jp   TEL(&FAX): +81-257-22-8161
> +========================================================+

      reply	other threads:[~2013-11-09 11:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-09  6:49 Shigeharu TAKENO
2013-11-09 11:19 ` Anthony Green [this message]

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=CACxje58FRxxer8S07F4k2OHnUSL95_-i_BUj3_dth-P+NJbzbA@mail.gmail.com \
    --to=green@moxielogic.com \
    --cc=libffi-discuss@sourceware.org \
    --cc=shige@iee.niit.ac.jp \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).