Unable to compile 2.4.14 on alpha

Unable to compile 2.4.14 on alpha

[Wakko Warner]

make[2]: Entering directory `/usr/src/2.4.14-test/arch/alpha/math-emu'
make[2]: Nothing to be done for `all_targets'.
make[2]: Leaving directory `/usr/src/2.4.14-test/arch/alpha/math-emu'
make[1]: Leaving directory `/usr/src/2.4.14-test/arch/alpha/math-emu'
ld -static -T arch/alpha/vmlinux.lds -N  arch/alpha/kernel/head.o init/main.o init/version.o \
        --start-group \
        arch/alpha/kernel/kernel.o arch/alpha/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o arch/alpha/math-emu/math-emu.o \
         drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/media/media.o drivers/scsi/scsidrv.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o drivers/md/mddev.o \
        net/network.o \
        /usr/src/2.4.14-test/arch/alpha/lib/lib.a /usr/src/2.4.14-test/lib/lib.a /usr/src/2.4.14-test/arch/alpha/lib/lib.a \
        --end-group \
        -o vmlinux
arch/alpha/kernel/kernel.o(.exitcall.exit+0x0): undefined reference to `local symbols in discarded section .text.exit'
mm/mm.o(.exitcall.exit+0x0): undefined reference to `local symbols in discarded section .text.exit'
fs/fs.o(.exitcall.exit+0x0): undefined reference to `local symbols in discarded section .text.exit'
fs/fs.o(.exitcall.exit+0x8): undefined reference to `local symbols in discarded section .text.exit'
fs/fs.o(.exitcall.exit+0x10): undefined reference to `local symbols in discarded section .text.exit'
fs/fs.o(.exitcall.exit+0x18): more undefined references to `local symbols in discarded section .text.exit' follow
make: *** [vmlinux] Error 1

[root@kakarot:/usr/src/2.4.14-test] ld --version
GNU ld version 2.11.92.0.12.3 20011121 Debian/GNU Linux
Copyright 2001 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License.  This program has absolutely no warranty.
[root@kakarot:/usr/src/2.4.14-test] gcc --version
2.95.4
[root@kakarot:/usr/src/2.4.14-test] 

gcc 3.0.3 didn't work either (I don't feel that's the problem)

2.4.16 did the same thing, except it was in char.o

I tried to link the kernel by removing arch/alpha/kernel/kernel.o and
replacing with the actual files.  the error is in arch/alpha/kernel/srm_env.o

I really need something to work as I have a DAC960 controller that I want to
try.

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: Unable to compile 2.4.14 on alpha

[J.A. Magallon]

On 20020115 Wakko Warner wrote:
>arch/alpha/kernel/kernel.o(.exitcall.exit+0x0): undefined reference to `local symbols in discarded section .text.exit'

Too bew binutils. .17 works again.

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-pre3-beo #5 SMP Sun Jan 13 02:14:04 CET 2002 i686

Re: Unable to compile 2.4.14 on alpha

[Wakko Warner]

> >arch/alpha/kernel/kernel.o(.exitcall.exit+0x0): undefined reference to `local symbols in discarded section .text.exit'
> 
> Too bew binutils. .17 works again.

Are you saying that 2.4.17 works but prior doesn't?  or were you refering to
binutils.

Please keep the CC to linux-kernel as my spam filter is tagging your mail
server =(

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: Unable to compile 2.4.14 on alpha

[J.A. Magallon]

On 20020115 Wakko Warner wrote:
>> >arch/alpha/kernel/kernel.o(.exitcall.exit+0x0): undefined reference to `local symbols in discarded section .text.exit'
>> 
>> Too bew binutils. .17 works again.
>
>Are you saying that 2.4.17 works but prior doesn't?  or were you refering to
>binutils.
>

Recent binutils warn about symbols marked as discardable but referenced
when the driver is built-in instead of modularized. Older ones just shut up.

Original explanation:
http://marc.theaimsgroup.com/?l=linux-kernel&m=100753194504523&w=2

Corrected mainly in 2.4.17-pre6 (and some leftovers in following pres).
>From ChangeLog-2.4.17:

pre6:
...
- Create __devexit_p() function and use that on 
  drivers which need it to make it possible to
  use newer binutils                (Keith Owens)
...

>Please keep the CC to linux-kernel as my spam filter is tagging your mail
>server =(
>

OK.

My ISP has reached the spam-black-lists ? I'm beginning to think that
those lists are becoming useless. Everybody is there. Some day someone
will manage to send just ONE message faking vger and the linux kernel
list will be banned...

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-pre3-beo #5 SMP Sun Jan 13 02:14:04 CET 2002 i686

Re: Unable to compile 2.4.14 on alpha

[Wakko Warner]

Ok, 2.4.17:
gcc -D__KERNEL__ -I/usr/src/2.4.17/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev4 -Wa,-mev6 -DMODULE   -DEXPORT_SYMTAB -c DAC960.c
DAC960.c: In function `DAC960_V2_EnableMemoryMailboxInterface':
DAC960.c:1054: internal error--unrecognizable insn:
(insn 949 477 474 (set (reg:DI 2 $2)
        (plus:DI (reg:DI 30 $30)
            (const_int 4398046511104 [0x40000000000]))) -1 (nil)
    (nil))
cpp0: output pipe has been closed
make[2]: *** [DAC960.o] Error 1
make[2]: Leaving directory `/usr/src/2.4.17/drivers/block'
make[1]: *** [_modsubdir_block] Error 2
make[1]: Leaving directory `/usr/src/2.4.17/drivers'
make: *** [_mod_drivers] Error 2

any ideas?  gcc-3.0 compiles it but I don't know if that's a good idea or not.
the kernel compiled with 2.95.4

> Recent binutils warn about symbols marked as discardable but referenced
> when the driver is built-in instead of modularized. Older ones just shut up.
> 
> Original explanation:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=100753194504523&w=2
> 
> Corrected mainly in 2.4.17-pre6 (and some leftovers in following pres).
> >From ChangeLog-2.4.17:
> 
> pre6:
> ...
> - Create __devexit_p() function and use that on 
>   drivers which need it to make it possible to
>   use newer binutils                (Keith Owens)
> ...
-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: Unable to compile 2.4.14 on alpha

[J.A. Magallon]

On 20020116 Wakko Warner wrote:
>Ok, 2.4.17:
>gcc -D__KERNEL__ -I/usr/src/2.4.17/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev4 -Wa,-mev6 -DMODULE   -DEXPORT_SYMTAB -c DAC960.c
>DAC960.c: In function `DAC960_V2_EnableMemoryMailboxInterface':
>DAC960.c:1054: internal error--unrecognizable insn:
>(insn 949 477 474 (set (reg:DI 2 $2)
>        (plus:DI (reg:DI 30 $30)
>            (const_int 4398046511104 [0x40000000000]))) -1 (nil)
>    (nil))

ev5 ? No idea about alphas. gcc version ?

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.18-pre3-beo #5 SMP Sun Jan 13 02:14:04 CET 2002 i686

Re: Unable to compile 2.4.14 on alpha

[Wakko Warner]

> >Ok, 2.4.17:
> >gcc -D__KERNEL__ -I/usr/src/2.4.17/include -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common -pipe -mno-fp-regs -ffixed-8 -mcpu=ev4 -Wa,-mev6 -DMODULE   -DEXPORT_SYMTAB -c DAC960.c
> >DAC960.c: In function `DAC960_V2_EnableMemoryMailboxInterface':
> >DAC960.c:1054: internal error--unrecognizable insn:
> >(insn 949 477 474 (set (reg:DI 2 $2)
> >        (plus:DI (reg:DI 30 $30)
> >            (const_int 4398046511104 [0x40000000000]))) -1 (nil)
> >    (nil))
> 
> ev5 ? No idea about alphas. gcc version ?

the kernel was compiled with 2.95.4 which is in debian's woody.  I also
installed debian's gcc-3.0 package.  it does compile dac960.

No, it's an EV4.  gcc 2.95.2 did nothing but eat all my memory on this file.

just out of curiosity, I have this dac960 controller with alpha 2.70
firmware.  I know it says it needs 2.73, but the latest for alpha is 2.70. 
Any ideas if it'll work or not?

If I loose the contents of everything on this sytem, fine, I have another
disk with the system on it so I won't loose anything.  =)

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals

Re: Unable to compile 2.4.14 on alpha

[Mr. James W. Laferriere]

	Hello Wakko ,

On Tue, 15 Jan 2002, Wakko Warner wrote:
 ...snip...
> just out of curiosity, I have this dac960 controller with alpha 2.70
> firmware.  I know it says it needs 2.73, but the latest for alpha is 2.70.
> Any ideas if it'll work or not?
	Nope ,  The linux DAC960 driver needs 3.51-0-04 for dual flash .
	Or 2.73-0-00 for single flash .  And beleive me Leonard means what
	he put in the README.DAC960 file .
	2.73 usability is new to me as when one of these dropped into my
	hands all the driver supported was the Dual 3.51... firmware .
	Using either of the above will work on Linux ,  BUT not alpha
	vms/osf/nt .
	The cost for the items from Mylex isn't reasonable imo .  But if
	you want it & have a flash burner , Get two just like on the card
	now & download the firmware & burn it .  Don't get the XDBA
	version as IIRC the alpha boards don't support it .  But do check
	if MB you have does .  Might get lucky .

> If I loose the contents of everything on this sytem, fine, I have another
> disk with the system on it so I won't loose anything.  =)

>  Lab tests show that use of micro$oft causes cancer in lab animals
	And other living things !-)  Hth ,  JimL

       +------------------------------------------------------------------+
       | James   W.   Laferriere | System    Techniques | Give me VMS     |
       | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
       | babydr@baby-dragons.com | Coudersport PA 16915 |   only  on  AXP |
       +------------------------------------------------------------------+

Re: Unable to compile 2.4.14 on alpha

[Wakko Warner]

> > just out of curiosity, I have this dac960 controller with alpha 2.70
> > firmware.  I know it says it needs 2.73, but the latest for alpha is 2.70.
> > Any ideas if it'll work or not?
> 	Nope ,  The linux DAC960 driver needs 3.51-0-04 for dual flash .
> 	Or 2.73-0-00 for single flash .  And beleive me Leonard means what
> 	he put in the README.DAC960 file .

I just tried it on my alpha (modifying the source to accept 2.70) and it
appears to work.  atleast I can make a partition, mke2fs it and put files on
it.  I keep getting ecc uncorrectable errors (retryable) frequently.  No,
this isn't DAC's fault because it happens even if I don't load the module. 
I'm assuming it's either 2.4.17 (I doubt it) or the fact I compiled it with
gcc 3.0.3   gcc 2.95.4 wouldn't compile dac960.c

> 	2.73 usability is new to me as when one of these dropped into my
> 	hands all the driver supported was the Dual 3.51... firmware .
> 	Using either of the above will work on Linux ,  BUT not alpha
> 	vms/osf/nt .
> 	The cost for the items from Mylex isn't reasonable imo .  But if
> 	you want it & have a flash burner , Get two just like on the card
> 	now & download the firmware & burn it .  Don't get the XDBA
> 	version as IIRC the alpha boards don't support it .  But do check
> 	if MB you have does .  Might get lucky .

I think I did.  Now if the ecc errors would go away, I'd be happy.  The
machine's crashed many times on my already.

Any ideas on compiling the DAC960 module w/o using gcc 3.0

> > If I loose the contents of everything on this sytem, fine, I have another
> > disk with the system on it so I won't loose anything.  =)
> 
> >  Lab tests show that use of micro$oft causes cancer in lab animals
> 	And other living things !-)  Hth ,  JimL
> 
>        +------------------------------------------------------------------+
>        | James   W.   Laferriere | System    Techniques | Give me VMS     |
>        | Network        Engineer |     P.O. Box 854     |  Give me Linux  |
>        | babydr@baby-dragons.com | Coudersport PA 16915 |   only  on  AXP |
>        +------------------------------------------------------------------+
> 
-- 
 Lab tests show that use of micro$oft causes cancer in lab animals