From: Christoph Plattner <christoph.plattner@dot.at>
To: Ulrich Drepper <drepper@cygnus.com>
Cc: "Rafael E. Herrera" <raffo@neuronet.pitt.edu>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Initial setup of the `glibc' in the target rootfile system
Date: Tue, 27 Feb 2001 20:52:40 +0100 [thread overview]
Message-ID: <3A9C0588.F2C47418@dot.at> (raw)
In-Reply-To: m3k86gil1b.fsf@otr.mynet.cygnus.com
To add some "light" here in the discussion.
The `user-defined-trusted-dirs=/lib' is exactly the "key" in the
discussion. It tells the online running library loader (file
./elf/ld-load.c)
where to search the libraries.
When building a cross tool chain and having the library install in
/usr/parisc/hppa-linux/lib, then the cross tool chain will search
there, but also the running programs, because this path is hard-coded
in the ld-load.c loader executable.
No my idea was, to give a "second search path" for the loader. So
the loader will search in /usr/parisc/hppa-linux/lib, will fail and
retry in /lib (as defined in `user-defined-trusted-dirs=/lib'). So also
the running binary on the target machine will access the glibc in /lib.
With friendly regards
Christoph P.
PS: Of course the way of using --prefix=/usr and installing with
install_root != /usr is a way, but lets say it, it is a HACK !!
The problems I have with many tools, is that they are not prepared
for cross-compiling very well. I need some evenings for bigger
packages.
Ulrich Drepper wrote:
>
> "Rafael E. Herrera" <raffo@neuronet.pitt.edu> writes:
>
> > export MACH=i386-linux
> > export DEST=/usr
> > export ROOT=~/parisk
> >
> > HOSTCC=gcc CC=hppa-linux-gcc $ROOT/source/glibc/configure \
> > --prefix=$DEST --build=$MACH \
> > --host=hppa-linux --target=hppa-linux \
> > --with-headers=$ROOT/source/linux/include --disable-profile \
> > --without-cvs --enable-add-ons
>
> This looks OK (though providing HOSTCC shouldn't be necessary) and
> --build, --host, and --target have no effect. The configure script
> will pick up all it has to know from the CC value.
>
> > make MAKE="make -j 10" user-defined-trusted-dirs=/lib
>
> Providing make isn't necessary. Also, the `user-defined-trusted-dirs'
> is not needed. Just run
>
> make -j10
>
> > make install user-defined-trusted-dirs=/lib \
> > install_root=/tmp/glibc
>
> Again, loose the `user-defined-trusted-dirs'. Also, is /tmp/glibc
> where the nfsroot is picked up? If not, just install in the nfsroot
> directory.
>
> --
> ---------------. ,-. 1325 Chesapeake Terrace
> Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
> Red Hat `--' drepper at redhat.com `------------------------
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
--
-------------------------------------------------------------------------
private: christoph.plattner@dot.at
company: christoph.plattner@alcatel.at
next prev parent reply other threads:[~2001-02-27 19:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-08 22:49 [parisc-linux] Initial setup of the `glibc' in the target root file system Christoph Plattner
2001-02-09 3:56 ` Alan Modra
2001-02-18 10:28 ` [parisc-linux] Initial setup of the `glibc' in the target rootfile system Christoph Plattner
2001-02-18 11:19 ` Alan Modra
2001-02-18 16:49 ` [parisc-linux] Initial setup of the `glibc' in the target rootfilesystem Christoph Plattner
2001-02-22 7:45 ` [parisc-linux] Initial setup of the `glibc' in the target rootfile system Rafael E. Herrera
2001-02-22 8:34 ` Christoph Plattner
2001-02-24 5:56 ` Rafael E. Herrera
2001-02-24 6:26 ` Ulrich Drepper
2001-02-24 7:27 ` Rafael E. Herrera
2001-02-24 7:42 ` Ulrich Drepper
2001-02-24 8:15 ` Rafael E. Herrera
2001-02-24 8:26 ` Alan Modra
2001-02-27 19:52 ` Christoph Plattner [this message]
2001-02-24 7:53 ` Alan Modra
2001-02-24 8:04 ` Ulrich Drepper
2001-02-24 8:21 ` Alan Modra
2001-02-24 8:43 ` Ulrich Drepper
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=3A9C0588.F2C47418@dot.at \
--to=christoph.plattner@dot.at \
--cc=drepper@cygnus.com \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=raffo@neuronet.pitt.edu \
/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