From: "René Pachernegg" <rene.pachernegg@apus.co.at>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Cross-compiling sysvinit
Date: Tue, 18 Jan 2000 11:21:16 +0100 [thread overview]
Message-ID: <38843E9C.E0EED65C@apus.co.at> (raw)
In-Reply-To: 3884359F.C191BB70@apus.co.at
Fixed it already. Thought I already tried everything. The prob was that
I set a link to the libs in the comiler/$target/lib dir. The linker
doesnt seem to like that. But copying the libs fixed it.
Regards
René
René Pachernegg wrote:
>
> Finally building the cross-compiler and the glibc succeded.
> Thanks to all the people from this mailing list who helped.
>
> Actually I am trying to cross-compile sysvinit without succes.
> The linker /powerpc-linux/ld tells me :
>
> cannot opten crt1.o: File or Directory not found
>
> I found crt1.o in my cross-compiled glibc in /lib and passed
> the directory with the -L option to the Linker. Additionally I added
> this directory to PATH. --> No changes
>
> Ann suggestions?
>
> Regards
> Rene
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-01-18 10:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-01-18 9:42 Cross-compiling sysvinit Reni Pachernegg
2000-01-18 10:21 ` René Pachernegg [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=38843E9C.E0EED65C@apus.co.at \
--to=rene.pachernegg@apus.co.at \
--cc=linuxppc-embedded@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).