From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Clarify MIPS ABIs support
Date: Wed, 25 Jul 2012 22:38:24 +0200 [thread overview]
Message-ID: <20120725223824.4881c01a@skate> (raw)
In-Reply-To: <50105627.6010905@zacarias.com.ar>
Le Wed, 25 Jul 2012 17:25:11 -0300,
Gustavo Zacarias <gustavo@zacarias.com.ar> a ?crit :
> > Makes sense. Gustavo, what do you think?
>
> Yes, it's the best option since we'll have the same dilemma sooner or
> latter with powerpc(64) for example.
Ok.
> > No, it could be this way. The bigger question is:
> >
> >>> TARGET_CFLAGS+=-fno-pic -mno-abicalls
> >
> > Why are those special CFLAGS needed from the beginning?
>
> From what i could unearth it basically breaks dynamic linking though it
> makes for smaller binaries.
> I've tried removing it in my tests to get uClibc dynamic linking working
> but something else is wrong, seemingly in the uClibc side.
> For starters the loader is wrong, ld-linux in the target vs. ld64-linux
> wanted by ELF files. And it seems there's something funky in the uClibc
> Makefile about that (wants mips64 arch to build it, but they're using
> unified ARCH as the kernel, so...)
Do you have a working mips64 kernel under Qemu? I vaguely remember that
you said that it was working with statically linked binary, but not
dynamically linked ones. Is this correct?
If you have a working mips64 kernel under Qemu, I'm interested by the
kernel config and Qemu config.
Thanks,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-07-25 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 20:47 [Buildroot] [PATCH] Clarify MIPS ABIs support Thomas Petazzoni
2012-07-25 16:29 ` Thomas Petazzoni
2012-07-25 17:32 ` Arnout Vandecappelle
2012-07-25 18:25 ` Thomas Petazzoni
2012-07-25 18:31 ` Thomas Petazzoni
2012-07-25 19:15 ` Thomas Petazzoni
2012-07-26 16:38 ` Arnout Vandecappelle
2012-07-27 6:31 ` Thomas Petazzoni
2012-07-26 19:01 ` Thomas Petazzoni
2012-07-26 19:38 ` Gustavo Zacarias
2012-07-27 6:56 ` Thomas Petazzoni
2012-07-27 10:17 ` Gustavo Zacarias
2012-07-25 20:25 ` Gustavo Zacarias
2012-07-25 20:38 ` Thomas Petazzoni [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=20120725223824.4881c01a@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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