From: Johannes Stezenbach <js@convergence.de>
To: linux-mips@linux-mips.org
Subject: Re: dietlibc nash pic/non-pic errors
Date: Wed, 4 Feb 2004 00:00:01 +0100 [thread overview]
Message-ID: <20040203230001.GB1667@convergence.de> (raw)
In-Reply-To: <4020137E.9020005@savages.net>
Shaun Savage wrote:
> I am want to cross compile dietlibc and nash(mkinitrd).
>
> I can cross compile static mipsel dietlibc libs
> but when I try to link it with nash I get
> the pic and non-pic error, can't merge
>
> I have gotten QPDF, SD on linux, busybox and ulibc cross compiled and
> working, so I sort of know what I am doing.
>
> I am using Maciej toolchain
- check that everything is compiled with '-fno-pic -mno-abicalls -G 0'
- you must have either a non-pic libgcc or make sure your programs
don't need libgcc
The standard configuration of gcc for mipsel-linux creates a
PIC libgcc only, so if you need a non-pic libgcc you must hack
the gcc configuration and rebuild your toolchain.
Or alternatively you can compile dietlibc as PIC
(remove '-fno-pic -mno-abicalls' from mips/Makefile.add
and diet.c).
HTH,
Johannes
prev parent reply other threads:[~2004-02-03 22:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-03 21:32 dietlibc nash pic/non-pic errors Shaun Savage
2004-02-03 23:00 ` Johannes Stezenbach [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=20040203230001.GB1667@convergence.de \
--to=js@convergence.de \
--cc=linux-mips@linux-mips.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