[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gentoo-amd64
Subject:    RE: [gentoo-amd64] Re: madwifi-driverxxxx (was: LVM?)
From:       "Pat McCormack" <prmccormack () eircom ! net>
Date:       2004-06-27 6:51:52
Message-ID: HFEJLEPPNIAFPLEOKPOJEEAOCDAA.prmccormack () eircom ! net
[Download RAW message or body]

Thanks
The build seems easy enough. However there is a closed source HAL binary
involved (FCC regs apparently) that as far as I can see in the CVS
http://cvs.sourceforge.net/viewcvs.py/madwifi/madwifi/hal/linux/  tree is
not got an AMD64 build. Suse however have a madwifi rpm targeted at 86_64.
I'll look in it and see what HAL module they are using.

-----Original Message-----
From: Jeremy Huddleston [mailto:eradicator@gentoo.org]
Sent: 26 June 2004 23:28
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: madwifi-driverxxxx (was: LVM?)


If it is missing an amd64 keyword, it probably hasn't been tested yet.
Try emerging it.  It may just work.  Most of the problems I've seen have
been solved with adding an option to ./configure, patching to include
-fPIC in libs or patching to get compatibility with gcc-3.4.

If it does work, file a bug at http://bugs.gentoo.org to let us know so
we can keyword it.

On Sat, 2004-06-26 at 15:45, Pat McCormack wrote:
> Hi all,
> This is my first posting. I have installed my first Gentoo system on a
AMD64
> Gigabyte board (I use it for seismic processing- it flies).
> I am attempting to get my Atheros wireless card working. The driver is
> madwifi-driverxxxx. All the ebuilds I have found are masked with keyword
> ~x86. Is it a big job to redo an ebuild for the amd64 architecture? I've
> used Linux for years but am a complete newbie to portage.
> TIA
> Pat



--
gentoo-amd64@gentoo.org mailing list

[prev in list] [next in list] [prev in thread] [next in thread]