public inbox for crossgcc@sourceware.org
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: crossgcc@sourceware.org
Cc: Konrad Eisele <konrad@gaisler.com>
Subject: Re: [PATCH 1/1] Add multilib build support [...]
Date: Tue, 27 Dec 2011 23:57:00 -0000	[thread overview]
Message-ID: <201112280057.05597.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <201112240022.18409.yann.morin.1998@anciens.enib.fr>

Konrad, All,

On Saturday 24 December 2011 00:22:18 Yann E. MORIN wrote:
> 
> I am slowly and not-so-smoothly coming up with a sane situation wrt the
> multilib patch, but there are still a few quirks I don't get right.
> 
> First, I split the code so it is more manageable. You can check it with:
> 
>     hg qclone -p http://crosstool-ng.org/hg/crosstool-ng/ct-ng.multilib  \
>                  http://crosstool-ng.org/hg/crosstool-ng                 \
>                  ct-ng.multilib
>     cd ct-ng.multilib
>     hg qpush -a

FYI, this MQ has been updated, and is now functional for the few tests
I did.

Beside your SPARC config, I managed to build an ARM multilib by tweaking
the gcc source code (by default, there is no multilib when targeting Linux).

In the coming days, I'll clean up the code (there are a few things left)
and do some more tests, and it will most probably be pushed upstream
before the end of the year!

Woohoo! Donuts! ;-)

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

  parent reply	other threads:[~2011-12-27 23:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 10:45 [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
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
2011-12-26 17:29     ` Yann E. MORIN
2011-12-27 23:57   ` Yann E. MORIN [this message]
2011-12-31 18:01   ` [PATCH 1/1] Add multilib build support [...] Yann E. MORIN
2012-01-02  7:17     ` konrad.gaisler

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=201112280057.05597.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).