linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@ica.net>
To: "David Edelsohn" <dje@watson.ibm.com>
Cc: "Users LinuxPPC" <linuxppc-user@lists.linuxppc.org>,
	"Developer LinuxPPC" <linuxppc-dev@lists.linuxppc.org>,
	"Fred Fish" <fnf@cygnus.com>
Subject: Re: [LinuxPPC] cross compiler, compiling
Date: Sun, 28 Mar 99 13:03:44 -0400	[thread overview]
Message-ID: <B0001827320@icamail.ica.net> (raw)


>	Without describing the directory structure for the cross-tools
>source and how it was configured, it is hard to diagnose what might be
>wrong.

would it be enough to say:

  target=powerpc-linux
  prefix=/usr/local/ppc
  includes=/usr/local/ppc/linuxppc-includes/
  libraries=/usr/local/ppc/linuxppc-lib
  cpu=603e

  root# ../egcs-1.1.1/configure --target=$target --prefix=$prefix \
        --enable-shared --enable-haifa --with-gnu-as --with-gnu-ld \
        --with-headers=$includes --with-libs=$libraries --with-newlib \
        --with-cpu=$cpu -v &> configure.log

for the includes i went to my LinuxPPC installation and took everything
from /usr/includes, resolved all links and removed obvious stuff like
X11, for the libs i took everything from /lib and /usr/lib, resolved
all references (which were almost always from /usr/lib to /lib) but
preserved the shared-library version links.

does that help? oh by the way my LinuxPPC kernel was compiled from the
Linux 2.2.1 sources. previous to doing this i had recompiled egcs 1.1.1
and binutils 2.9.1-19b on my x86; on the ppc i just installed the rpms
from Gary Thomas.

please don't hesitate to mention if i forgot anything else.

best regards,
   trevor woerner

------------------------------------------------------------

...Senior, for his first selection, will play "A Cup Of
   Coffee, A Sandwich, And You" from the opera: Aida

                             --- Groucho Marx
                                 The Cocoanuts, 1929


[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

             reply	other threads:[~1999-03-28 17:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-28 17:03 Trevor Woerner [this message]
1999-03-28 18:15 ` [LinuxPPC] cross compiler, compiling David Edelsohn
1999-03-31 14:24 ` puetzk6715
  -- strict thread matches above, loose matches on Subject: below --
1999-03-28  5:49 Trevor Woerner
1999-03-28 17:04 ` David Edelsohn

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=B0001827320@icamail.ica.net \
    --to=twoerner@ica.net \
    --cc=dje@watson.ibm.com \
    --cc=fnf@cygnus.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=linuxppc-user@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).