All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Murray <rmurray@cyberhqz.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: linux-mips@oss.sgi.com, config-patches@gnu.org
Subject: Re: config.guess changs
Date: Thu, 27 Dec 2001 21:06:00 -0800	[thread overview]
Message-ID: <20011227210600.G29645@cyberhqz.com> (raw)
In-Reply-To: <20011227095306.A16072@lucon.org>

[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Thu, Dec 27, 2001 at 09:53:06AM -0800, H . J . Lu wrote:
> > The config.guess rework of 12/12/2001 doesn't work on big endian machines,
> > as the preprocessor defines "mips" to be " 1", so the cpp -E output ends
> > up being "CPU= 1".
> 
> Try this patch.
> 
> 
> H.J.
> ----
> 2001-12-27  H.J. Lu  <hjl@gnu.org>
> 
> 	* config.guess (mips:Linux:*:*): Undefine CPU, mips and mipsel
> 	first.
> 
> --- config.guess	Wed Dec 12 19:53:12 2001
> +++ config.guess	Thu Dec 27 09:51:18 2001
> @@ -770,6 +770,9 @@ EOF
>      mips:Linux:*:*)
>  	eval $set_cc_for_build
>  	sed 's/^	//' << EOF >$dummy.c
> +	#undef CPU
> +	#undef mips
> +	#undef mipsel
>  	#if defined(__MIPSEL__) || defined(__MIPSEL) || defined(_MIPSEL) || defined(MIPSEL) 
>  	CPU=mipsel 
>  	#else

That fixes the problem here.

-- 
Ryan Murray, Debian Developer (rmurray@cyberhqz.com, rmurray@debian.org)
The opinions expressed here are my own.

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2001-12-31  0:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-27 10:08 config.guess changs Ryan Murray
2001-12-27 17:53 ` H . J . Lu
2001-12-28  5:06   ` Ryan Murray [this message]
2002-01-01 22:19   ` Ben Elliston

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=20011227210600.G29645@cyberhqz.com \
    --to=rmurray@cyberhqz.com \
    --cc=config-patches@gnu.org \
    --cc=hjl@lucon.org \
    --cc=linux-mips@oss.sgi.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.