From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: "konrad.gaisler" <konrad@gaisler.com>
Subject: Re: [PATCH 1/1] Add multilib build support for libc target. Libc is build <multilib>-times in seperate sysroot directories. In a last step links are created to reflect the expected multilib structure.
Date: Mon, 26 Dec 2011 21:30:00 -0000 [thread overview]
Message-ID: <201112262230.23785.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <4EF8C533.9010104@gaisler.com>
Konrad, All,
On Monday 26 December 2011 20:04:19 konrad.gaisler wrote:
> On 12/26/2011 05:56 PM, Yann E. MORIN wrote:
> > That is something we'll have to check later: is it possible to have more
> > than one multilib running on the target? I believe that would need some
> > non-trivial hackery to work properly...
> No, not multiple multilibs, but one of the multilibs subdirs. For example
> for the leon-sparc toolchain, the toolchain would have 4 subdirs: ./
> msoft-float/
> mv8 and mv8/msoft-float.
> on hardware without fpu but mv8 you would only copy and use the
> mv8/msoft-float multilib-subdir at /usr/lib, the others will not be used.
So, it is not possible to have (hypthetical setup for ARM with neon):
- the basic system (eg. /bin/busybox ;-)) using the default multilib
from "sysroot/lib" and "sysroot/usr/lib" (resp as "/lib" and "/usr/lib"
at runtime)
- some 'optimised' components (eg. mp3 player) using the float-optimised
multilib from "sysroot/neon/lib" and "sysroot/usr/lib/neon" (resp as
"/lib/neon" and "/usr/lib/neon" at runtime)
That would require that:
- the linker 'ld' sets the proper path to the dynamic linker, at _built-time_
- the dynamic linker looks in the proper search-path
Sounds like it's not too easy... :-/
But I agree with you, the most common setup would probably be to use only
one variant on the target, either everything from the defaults /lib and
/usr/lib, or everything from a sub-dir (eg. /lib/neon and usr/lib/neon)
and not a mix... Let's make that work first! ;-)
Thanks again!
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2011-12-26 21:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 10:45 Konrad Eisele
2011-12-12 23:07 ` [PATCH 1/1] Add multilib build support for libc target Yann E. MORIN
2011-12-13 8:38 ` Konrad Eisele
2011-12-13 17:15 ` Yann E. MORIN
2011-12-23 23:22 ` [PATCH 1/1] Add multilib build support for libc target. Libc is build <multilib>-times in seperate sysroot directories. In a last step links are created to reflect the expected multilib structure Yann E. MORIN
2011-12-24 21:10 ` konrad.gaisler
2011-12-26 16:57 ` Yann E. MORIN
2011-12-26 19:03 ` konrad.gaisler
2011-12-26 21:30 ` Yann E. MORIN [this message]
2011-12-26 17:29 ` Yann E. MORIN
2011-12-27 23:57 ` [PATCH 1/1] Add multilib build support [...] Yann E. MORIN
2011-12-31 18:01 ` Yann E. MORIN
2012-01-02 7:17 ` konrad.gaisler
-- strict thread matches above, loose matches on Subject: below --
2011-11-14 10:38 simple multilib option Konrad Eisele
2011-11-14 10:55 ` [PATCH 1/1] Add multilib build support for libc target. Libc is build <multilib>-times in seperate sysroot directories. In a last step links are created to reflect the expected multilib structure Konrad Eisele
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=201112262230.23785.yann.morin.1998@anciens.enib.fr \
--to=yann.morin.1998@anciens.enib.fr \
--cc=crossgcc@sourceware.org \
--cc=konrad@gaisler.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).