All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@fs.tum.de>
To: Buck Rekow <rekow@bigskytel.com>
Cc: rth@twiddle.net, linux-kernel@vger.kernel.org,
	breed@users.sourceforge.net, achirica@users.sourceforge.net
Subject: Re: PROBLEM: Aironet compile failure 2.6-test9/Alpha architecture
Date: Sat, 22 Nov 2003 13:54:17 +0100	[thread overview]
Message-ID: <20031122125417.GP16828@fs.tum.de> (raw)
In-Reply-To: <3FBD67E7.5020405@bigskytel.com>

On Thu, Nov 20, 2003 at 06:18:31PM -0700, Buck Rekow wrote:

>  Aironet is not listed as i can find in the file MAINTAINERS, however, 
> This report needs to go somewhere and do something. The maintainer is 
> however listed in airo.c. merry carbon-copy, people.
> 
> Quite simply, the compile fails with the following error.   I'm not sure 
> anyone else  is using an aironet card under Alpha, so I guess someone 
> needs to report this.
> I must say Aironet can be a real pain.
> 
> predator:/usr/src/linux-2.6.0-test9# make modules
> make[1]: `arch/alpha/kernel/asm-offsets.s' is up to date.
>  CC [M]  drivers/net/wireless/airo.o
> drivers/net/wireless/airo.c: In function `emmh32_setseed':
> drivers/net/wireless/airo.c:1458: internal error--unrecognizable insn:
> (insn:TI 512 478 513 (set (reg:DI 1 $1)
>        (plus:DI (reg:DI 30 $30)
>            (const_int 4398046511104 [0x40000000000]))) -1 (insn_list 51 
> (insn_list:REG_DEP_ANTI 494 (nil)))
>    (nil))
> cpp0: output pipe has been closed
> make[3]: *** [drivers/net/wireless/airo.o] Error 1
> make[2]: *** [drivers/net/wireless] Error 2
> make[1]: *** [drivers/net] Error 2
> make: *** [drivers] Error 2
> 
> Here is the output of ver_linux
> Gnu C                  2.95.4
>...
> There is a possibility this may be caused by GCC bug PR-9164, which is 
> present in debian 3.0  Alpha (Debian people: READ: *fix it*)  which I am 
> running.    
> 
>  Hope this is fixable.

This is a bug in the compiler, but the gcc developers stopped any 
development on 2.95 long time ago.

Besides the fact that you'd have to wait half a year (or maybe two
years) until Debian 3.1 releases to get the fix if it was fixed, I doubt
anyone of the Debian gcc maintainers would spend his time on fixing bugs 
in gcc 2.95 .

You might have luck with trying to use the gcc-3.0 in stable to compile 
your kernel, but since I doubt anyone backported gcc 3.2 or 3.3 for 
alpha to the pretty ancient Debian stable it might be that the only way 
to get kernel 2.6 running for you would be to try to locally modify 
airo.c in a way that your gcc compiles it.

>    Buck Rekow

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


      parent reply	other threads:[~2003-11-22 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-21  1:18 PROBLEM: Aironet compile failure 2.6-test9/Alpha architecture Buck Rekow
2003-11-21  3:22 ` Richard Henderson
2003-11-21  4:11   ` Jeremy T. Bouse
2003-11-22 12:54 ` Adrian Bunk [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=20031122125417.GP16828@fs.tum.de \
    --to=bunk@fs.tum.de \
    --cc=achirica@users.sourceforge.net \
    --cc=breed@users.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rekow@bigskytel.com \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.