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

Yann E. MORIN wrote:
> Konrad, All,
> 
> On Monday 14 November 2011 11:37:59 Konrad Eisele wrote:
>> ---
>>  scripts/build/binutils/binutils.sh        |   14 +++-
>>  scripts/build/cc/gcc.sh                   |   15 +++-
>>  scripts/build/libc/glibc-eglibc.sh-common |  124 +++++++++++++++++++++++++---
>>  3 files changed, 134 insertions(+), 19 deletions(-)
> 
> Could you provide a sample .config where multilib works?
> 
> I'm strugling to get at least one configuration to at least pass the
> C library headers install step, and none works... :-(
> 
> If I could get a sane and known-working starting point, I could build
> from there.

$wget http://crosstool-ng.org/download/crosstool-ng/crosstool-ng-1.13.0.tar.bz2
$wget ftp://gaisler.com/gaisler.com/linux/patches/ct-1.diff
$tar xvf crosstool-ng-1.13.0.tar.bz2
$cat ct-1.diff | patch -p1 -d crosstool-ng-1.13.0
$cd crosstool-ng-1.13.0
$make -f Makefile.local.mk do_install
$make -f Makefile.local.mk do_build

The patch ct-1.diff adds crosstool-ng-1.13.0/build/ctng/.config
which is the conf file that build the toolchain in:
/opt/sparc-linux-4.6.0-toolchains/multilib (must be writable or change)
$make -f Makefile.local.mk do_install
install itself in crosstool-ng-1.13.0/build
$make -f Makefile.local.mk do_build
builds inside crosstool-ng-1.13.0/build/ctng using the supplied .config,
and finally to debug:
$make -f Makefile.local.mk do_build RESTART=<step> STOP=<step>
The toolchain has 4 multilib combinations:
"-msoft-float",  "-msoft-float -mv8", "-mv8" and "" .

-- Konrad

ps:
$cat /etc/slackware-version
Slackware 12.2.0
$uname  -a
Linux ada 2.6.27.31-smp #1 SMP Mon Dec 13 16:52:53 CET 2010 i686 Intel(R) Core(TM) i7 CPU         950  @ 3.07GHz GenuineIntel GNU/Linux


> 
> Regards,
> Yann E. MORIN.
> 


--
For unsubscribe information see http://sourceware.org/lists.html#faq

  reply	other threads:[~2011-12-13  8:38 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 [this message]
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   ` [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

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=4EE70D20.40909@gaisler.com \
    --to=konrad@gaisler.com \
    --cc=crossgcc@sourceware.org \
    --cc=yann.morin.1998@anciens.enib.fr \
    /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).