linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Joe Green <jgreen@mvista.com>
To: greyham@research.canon.com.au (Graham Stoney),
	linuxppc-embedded@lists.linuxppc.org (LinuxPPC Embedded Mailing
	List)
Subject: Re: Journeyman configure/build options for gcc & glibc?
Date: Wed, 16 Aug 2000 11:44:29 -0700	[thread overview]
Message-ID: <00081611524600.29732@minotaur.mvista.com> (raw)
In-Reply-To: <20000815073750.58C33274@elph.research.canon.com.au>


On Tue, 15 Aug 2000, Graham Stoney wrote:
> I thought I had the whole soft-float thing on 8xx worked out long ago, until I
> upgraded our root filesystem to the one from MontaVista's Journeyman kit, and
> found that my glibc-2.1.3.so (which my binaries work when linked against)
> doesn't work in place of the Journeyman glibc-2.1.2.so.  It's the usual
> symptom: A simple floating-point printf gives the wrong answer.
>
> So, my question: what configure options were used to build the gcc-2.95.2 &
> glibc-2.1.2 in Journeyman?  In particular:
>
> - Did the gcc configure include "-with-cpu=860" (or one of the other cpus's
>   to make -msoft-float the default).
>
> - Has the gcc specs file been hacked to pass -D_SOFT_FLOAT in the absence of
>   -mhard-float (note that -mcpu=860 won't do this by default in gcc-2.95.2)
>
> - Was CFLAGS set to include -msoft-float before building glibc?

I believe the compiler has been modified to default to both
-msoft-float and -D_SOFT_FLOAT for ppc_8xx.

> - Any other suggestions :-(

I recall the printf problem as something we specifically fixed.  I
asked the engineer who worked on it, and he said it was a varargs
problem, so the fix is in the the gcc package.

--
Joe Green <jgreen@mvista.com>
MontaVista Software, Inc.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  parent reply	other threads:[~2000-08-16 18:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-15  7:37 Journeyman configure/build options for gcc & glibc? Graham Stoney
2000-08-15 15:09 ` Dan Malek
2000-08-16 18:44 ` Joe Green [this message]
2000-08-17  3:16   ` Graham Stoney
2000-08-17 15:02     ` Joe Green
  -- strict thread matches above, loose matches on Subject: below --
2000-08-15 20:22 Ellie Abdollahi
2000-08-15 20:58 ` Dan Malek

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=00081611524600.29732@minotaur.mvista.com \
    --to=jgreen@mvista.com \
    --cc=greyham@research.canon.com.au \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).