From: Daniel Jacobowitz <drow@false.org>
To: Ersin Akinci <ersin.akinci@gmail.com>
Cc: binutils@sources.redhat.com
Subject: Re: Messed up library paths?
Date: Tue, 15 Feb 2005 18:32:00 -0000 [thread overview]
Message-ID: <20050215161215.GA26276@nevyn.them.org> (raw)
In-Reply-To: <f8a051a9050215080637018970@mail.gmail.com>
On Tue, Feb 15, 2005 at 11:06:40AM -0500, Ersin Akinci wrote:
> All of my toolchain (gcc, g++, cc, as, ld, etc.) has been compiled
> statically, so there are no missing dependencies. I have _no_ idea
> where the /home/ersin/vorpo/Programs/glibc-2.3.4/lib/libc.so.6 came
> from, since the directory it should be looking in is
> /home/ersin/vorpo/vorpo/Programs/glibc-orig-2.3.4/lib. I checked out
> all my environment variables, but nothing looks wrong. Is there
> something wrong with chroot?
You're missing how to use glibc in a nonstandard directory, which is
quite tricky. In this case, look at the text file in
/home/ersin/vorpo/Programs/glibc-2.3.4/lib/libc.so.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-02-15 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <f8a051a90502150803198089bb@mail.gmail.com>
2005-02-15 18:30 ` Ersin Akinci
2005-02-15 18:32 ` Daniel Jacobowitz [this message]
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=20050215161215.GA26276@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=ersin.akinci@gmail.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).