public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Francis Galiegue <fg@mandrakesoft.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] gcc and glibc: big troubles
Date: Wed, 22 Nov 2000 10:59:29 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590678205767@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205756@msgid-missing>

On Tue, 21 Nov 2000, Jim Wilson wrote:

Jim,

Thanks very much for your complete answer. I'm afraid I'm not as good as you
guys, but I'm doing my best to follow :)

> 
> >/tmp/ccalpirm.s:6579: Internal error, aborting at ../../gas/config/tc-ia64.c
> >line 5190 in errata_nop_necessary_p
> >        if (regno > 16)
> >          abort ();		<----- This one
> 
> This is a bug in the hardware errata workaround patch.  This should be
> 	if (regno >= 64)
> 	  abort ();
> I found this problem in pre-release testing, so it is fixed in the 001117
> release, but I didn't release a separate patch for this bug fix.
> 

OK, I made a patch over the 001124 release... Compiling with it right now.

> 
> You can build specific tools, like gcc, by using
>     make all-gcc
> There are makefile dependencies which will force everything gcc requires
> (opcodes/bfd/binutils/gas/ld) to also be built.  You can build specific
> target libraries, like libstdc++, by using
>     make all-target-libstdc++
> Making all-gcc, all-gdb, and all-target-libstdc++, will probably build
> everything you want.
> 
> You can install specific tools, like gcc, by using
>    make install-gcc
> There are no dependencies here, so you need to separately install everything
> you want, e.g. bfd, binutils, gas, ld, gdb, gcc, target-libstdc++, and maybe
> some other stuff.
> 

Thanks, rebuilding with these right now.

> You can disable building the gdb gui by using --disable-gdbtk
> 

Already in my spec file.

> 
> I like to point out again that my releases are primarily for the Trillian
> group, to enable kernel, glibc, and Linux distribution work.  It was never
> the intent to recommend them to everyone.  I'd rather recommend the compilers
> that come with the Linux distributions, but unfortunately, all IA-64 GNU/Linux
> distributions are still using the old February toolchain, so as a stop gap
> measure I'm making my toolchains available to everyone.  Since you are
> Linux distributor though, you'd probably have to build my toolchain anyways.
> 

Yep, very useful for building from a chroot... Thanks for your time again.

-- 
Francis Galiegue, fg@mandrakesoft.com
"Programming is a race between programmers, who try and make more and more
idiot-proof software, and universe, which produces more and more remarkable
idiots. Until now, universe leads the race"  -- R. Cook



      parent reply	other threads:[~2000-11-22 10:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-21 15:36 [Linux-ia64] gcc and glibc: big troubles Francis Galiegue
2000-11-21 16:00 ` Jes Sorensen
2000-11-21 16:58 ` H . J . Lu
2000-11-21 19:14 ` Jim Wilson
2000-11-22 10:59 ` Francis Galiegue [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=marc-linux-ia64-105590678205767@msgid-missing \
    --to=fg@mandrakesoft.com \
    --cc=linux-ia64@vger.kernel.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