Skip to contentSkip to conversation

Compiling latest 2.6 bk snapshot on Alpha

DISCUSSION Mathieu Chouquet-Stringer 7 participants 9 messages Sep 3, 2003 – Sep 9, 2003 Alpha port

lore
Share & tools
lore
#0 lore raw

Hi all,

I've been hitting the same error every time I try to compile bk current on alpha, namely the linker can't do its job on .tmp_vmlinux1.
My compiler is "gcc version 3.2.3 (Debian)" (but I also tried with 3.3 and 2.95), same problem.

Here is the output:
LD .tmp_vmlinux1
init/built-in.o(.text+0x12a8): In function `inflate_codes':
: relocation truncated to fit: BRADDR .init.text init/built-in.o(.text+0x137c): In function `inflate_codes':
: relocation truncated to fit: BRADDR .init.text init/built-in.o(.text+0x15bc): In function `inflate_stored':
: relocation truncated to fit: BRADDR .init.text init/built-in.o(.text+0x2158): In function `inflate':
: relocation truncated to fit: BRADDR .init.text init/built-in.o(.text+0x2170): In function `inflate':
: relocation truncated to fit: BRADDR .init.text init/built-in.o(.text+0x21b4): In function `inflate':
: relocation truncated to fit: BRADDR .init.text init/built-in.o(.text+0x21d4): In function `inflate':
: relocation truncated to fit: BRADDR .init.text
make: *** [.tmp_vmlinux1] Error 1

Am I missing something? Is there a bk tree for Alpha (Jeff Garzik, in his bk doc talks about one but it seems to be dead)?

Signature · 4 lines
Mathieu Chouquet-Stringer              E-Mail : [email protected]
       Never attribute to malice that which can be adequately
                    explained by stupidity.
                     -- Hanlon's Razor --
#1 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Mathieu" == Mathieu Chouquet-Stringer <[email protected]> writes:

Mathieu> I've been hitting the same error every time I try to compile Mathieu> bk current on alpha, namely the linker can't do its job on Mathieu> .tmp_vmlinux1. My compiler is "gcc version 3.2.3 (Debian)" Mathieu> (but I also tried with 3.3 and 2.95), same problem.

Please check your binutils version. Here is the one I use, with great success :

maz@panther:/mnt/i386/linux-2.5$ alpha-linux-ld --version
GNU ld version 2.13.90.0.18 20030121
	M.
Signature · 1 line
Places change, faces change. Life is so very strange.
#2 lore raw
Quoted 5 lines · Marc Zyngier

Please check your binutils version. Here is the one I use, with great success :

maz@panther:/mnt/i386/linux-2.5$ alpha-linux-ld --version
GNU ld version 2.13.90.0.18 20030121

Mine is: GNU ld version 2.14.90.0.5 20030722 Debian GNU/Linux

Looks like it's not that good... :-)

Thanks for the tip!

Signature · 4 lines
Mathieu Chouquet-Stringer              E-Mail : [email protected]
       Never attribute to malice that which can be adequately
                    explained by stupidity.
                     -- Hanlon's Razor --
#3 lore raw

On Wed, 2003-09-03 11:00:24 -0400, Mathieu Chouquet-Stringer <[email protected]> wrote in message <20030903150024.GA18306@localhost>:

Quoted 8 lines · Marc Zyngier
Quoted 5 lines

Please check your binutils version. Here is the one I use, with great success :

maz@panther:/mnt/i386/linux-2.5$ alpha-linux-ld --version
GNU ld version 2.13.90.0.18 20030121

Mine is: GNU ld version 2.14.90.0.5 20030722 Debian GNU/Linux

I've just started a compile run with exactly this ld and gcc-3.3.2 20030812. This may take a while (it's a 166MHz NoName...).

Maybe you've simply created a too large kernel image. Have you compiled many features into the kernel (where modules would have worked also...)?

MfG, JBG

Signature · 4 lines
   Jan-Benedict Glaw       [email protected]    . +49-172-7608481
   "Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg
    fuer einen Freien Staat voll Freier Bürger" | im Internet! |   im Irak!
      ret = do_actions((curr | FREE_SPEECH) & ~(IRAQ_WAR_2 | DRM | TCPA));
#4 lore raw

If using RedHat-7.2 based thing on alpha or older you can use my own maintained RH rawhide for alpha:

ftp.rdsor.ro/pub/Linux/Distributions/AlphaLinux

There can find very latest gcc/binutils/glibc shaga, it must fit OK with any redhat for alphas.

I have no problem compiling latest kernel with tham.

Cristian

Quoted 20 lines · Jan-Benedict Glaw

On Wed, 2003-09-03 11:00:24 -0400, Mathieu Chouquet-Stringer <[email protected]>

wrote in message <20030903150024.GA18306@localhost>:

Quoted 8 lines · Marc Zyngier
Quoted 5 lines

Please check your binutils version. Here is the one I use, with great success :

maz@panther:/mnt/i386/linux-2.5$ alpha-linux-ld --version
GNU ld version 2.13.90.0.18 20030121

Mine is: GNU ld version 2.14.90.0.5 20030722 Debian GNU/Linux

I've just started a compile run with exactly this ld and gcc-3.3.2 20030812. This may take a while (it's a 166MHz NoName...).

Maybe you've simply created a too large kernel image. Have you compiled many features into the kernel (where modules would have worked also...)?

MfG, JBG

Signature · 7 lines
Life in itself has no meaning. 
Life is an opportunity to create meaning.

              \|/ ____ \|/ 
              "@'/ .. \`@" 
              /_| \__/ |_\ 
                 \__U_/ 
#5 lore raw

Miata 500 is alphaev6 ? (segfault while configure glibc with --target=alphaev6)

In reply to Jan-Benedict Glaw

Is subj true ?
I get seg fault compiling glibc with --target=alphaev6 some error that segfault at
the test binary while "cheking long long"

Is something wrong with gcc or glibc ? Or is not alphaev6, not support alphaev6 instruction set and segfault.

Packages installed:

glibc-2.3.2-78
gcc-3.3.2-3
binutils-2.14.90.0.5-7

#6 lore raw

Re: Miata 500 is alphaev6 ? (segfault while configure glibc with --target=alphaev6)

Quoted 6 lines · Balint Cristian

Is subj true ? I get seg fault compiling glibc with --target=alphaev6 some error that segfault at the test binary while "cheking long long"

Is something wrong with gcc or glibc ? Or is not alphaev6, not support alphaev6 instruction set and segfault.

Miata is ev56, and does not support the ev6 additions.

Signature · 2 lines
Måns Rullgård
[email protected]
#7 lore raw

Re: Miata 500 is alphaev6 ? (segfault while configure glibc with --target=alphaev6)

In reply to Balint Cristian
Quoted 1 line · Balint Cristian

Is subj true ?

My Miata MoBo has a 21164A on it, i.e. EV56.
Check /proc/cpuinfo ...

Regards,

Signature · 3 lines
Kurt Garloff  <[email protected]>                            Cologne, DE 
GPG key: See mail header, key servers                 SuSE Labs (Head)
SuSE Linux AG, Nuernberg, DE                            SCSI, Security
#8 lore raw

Re: Miata 500 is alphaev6 ? (segfault while configure glibc with --target=alphaev6)

In reply to Balint Cristian
Quoted 1 line · Balint Cristian

Is subj true ?

Nope. Miata is an EV5x--yours is probably an EV56.

Signature · 3 lines
Kelledin
"If a server crashes in a server farm and no one pings it, does 
it still cost four figures to fix?"