public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jan Svenungson <jan.svenungson@supertel.se>
To: gcc@gcc.gnu.org
Subject: Need help on this one.
Date: Mon, 03 Dec 2001 04:50:00 -0000	[thread overview]
Message-ID: <20011203134653.B18576@unicorn> (raw)

Hola!
I've posted a mail for help on the help-gcc list but no one was able to help me out, i have also tried to get hold of someone at the irc.linpeople.org #gcc but no luck there either... So if this mail is not apropriate for this list forgive me but i am really desperate with getting help with this thing...
What i am trying to do is to install gcc-2.95.3 on a slackware7 box and "make install" it to a separate partition. That partition will later be put in another box and act as "/" but are mounted in "/tmp/newinstall" on the building computer.
After the install is done (No errors, works fine!) i have tried to chroot into "/tmp/newinstall" (Which contains glibc, bash, etc. etc.) and things seem to work alright. I just need to set up some links and copy some files to the right place (cc1, cpp0, stuff like that). However, when i try to compile new things in the chroot environment gcc cant find the headers. It looks for them in "/tmp/newinstall/usr/lib/gcc-lib/i586-pc-linux-gnu/gcc-2.95.3/include/". I do not know how to make gcc understand that it is not in "/tmp/newinstall" at this point.
I have tried with "make prefix=/tmp/newinstall/usr local_prefix=/tmp/newinstall/usr/local/ gxx_include_dir=/tmp/newinstall/usr/include/g++ include_dir=/tmp/newinstall/usr/include/ install". I found some of these options in some docs at the gnu site but i dont know if these are the right ones to use really.
If i set up a link in the chroot environment from "/tmp/newinstall" to "/" it find the headers so obviously the install is ok actually, just that gcc doesn't know that "/tmp/newinstall" will be "/" later on. How the heck do i tell gcc this? glibc (and other programs) has the "make install_root=/whatever install" option and i assume gcc has to but i just cant find out what the right command options are...
Yours sincerely,
-- 

+------------------------------------+
|           Jan Svenungson           |
| jan<dot>svenungson<at>linux<dot>nu |
|            UIN: 6581164            |
|    Registered linux user #91145    |
+------------------------------------+
Those who can't write, write manuals.

             reply	other threads:[~2001-12-03 12:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-03  4:50 Jan Svenungson [this message]
2001-12-03  6:21 ` Paolo Carlini
2001-12-03  6:49   ` Paolo Carlini

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=20011203134653.B18576@unicorn \
    --to=jan.svenungson@supertel.se \
    --cc=gcc@gcc.gnu.org \
    --cc=jan.svenungson@linux.nu \
    /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).