public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Sven LUTHER <LUTHERSV@e-i.com>
To: Franz.Sirl-kernel@lauterbach.com
Cc: egcs@cygnus.com
Subject: Re: Cross compiler (again)
Date: Tue, 07 Jul 1998 23:46:00 -0000	[thread overview]
Message-ID: <35A315CB.D2AE0A78@e-i.com> (raw)

You wrote :
| Am Mon, 06 Jul 1998 schrieb luther@dpt-info.u-strasbg.fr:
| >Hello, ...
| >
| >i managed to compile a m68k-linux -> ppc-linux-glibc1 cross compiler
| thanks to 
| >the help i received from this list.
| >
| >Yesterday i got hold of some ppc-linux-glibc2 includes and libraries,
| and was in the process of building a cross compiler for them.
| >
| >I got the message (while compiling libgcc2.c:1719)
| >
| >* conflicting types for atexit
| >declared in stdlib.h:502 and in gcc/gbl-ctors.h:43
| 
| Have you specified --target=powerpc-unknow-linux-gnu (no glibc1!)?
| That's the correct one for glibc-2.1.
|
| Franz.

The exact configure options were :

./configure --target=ppc-linux --with-headers=/usr/local/include-ppc
--with-libs=/usr/local/libs-ppc

i use linux-ppc because so i have shorter executable names. ppc-linux
get changed to powerpc-unknown-linux-gnu by config.sub so it should
cause no problem.

is there another way to declare aliases for target names ?

a yes i use glibc2.0.94 as it is the correct one for ppc and not
glibc2.0.[567]. i got it from the debian/slink ppc packages.

Friendly,

Sven LUTHER

             reply	other threads:[~1998-07-07 23:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-07-07 23:46 Sven LUTHER [this message]
  -- strict thread matches above, loose matches on Subject: below --
1998-07-07 16:57 Franz Sirl
1998-07-07 10:14 luther
1998-07-17 18:50 ` Rask Ingemann Lambertsen

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=35A315CB.D2AE0A78@e-i.com \
    --to=luthersv@e-i.com \
    --cc=Franz.Sirl-kernel@lauterbach.com \
    --cc=egcs@cygnus.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 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).