ARCH teams, Please test sys-apps/pcmcia-3.2.8 and the split out sys-apps/pcmcia-cs-modules-3.2.8 on your ARCH and mark ~ARCH/ARCH accordingly. Hopefully this will be the last major release of pcmcia-cs (will be replaced by pcmciautils, see bug #84234).
mips doesn't support pcmcia hardware at this time, if it ever has, and unknown if it ever will. The last known mips laptop was made some where back in the Dark Ages, so it's really not applicable for us to test and keyword. If needed, we can use.mask any pcmcia related USE flags and such to avoid repoman conflicts (if we haven't done so already).
Adding robbat2 to CC: in the hope he can take care of the mips ARCH.
ARCH teams? Please test as this release should fix quite a few problems with the previous releases, both package- and ebuild wise.
Ran into some problems.. The Configure script from pcmcia-cs contains: if [ $VERSION_CODE -ge `version 2 5 0` -a "$CONFIG_PCMCIA" != "y" ] ; then echo "2.5.0 and later kernels require that PCMCIA be configured in the" echo " kernel source tree. To fix, reconfigure and rebuild your" echo " kernel with PCMCIA enabled." fail fi Though the e-build for pcmcia-cs-modules contains: if (linux_chkconfig_present PCMCIA || linux_chkconfig_present PCCARD); then eerror eerror "This package requires the in-kernel PCMCIA drivers to be disabled." eerror die "Kernel PCMCIA support detected" fi
The sys-apps/pcmcia-cs-modules package should only be used with kernel 2.4.x. I've modified the ebuilds to reflect this, thanks for pointing it out. If your ARCH doesn't support 2.4.x, please just test sys-apps/pcmcia-cs.
Created attachment 58060 [details, diff] Patch for compiling pcmcia-cs-3.2.8 with gcc-4.0.0 It would be good if this patch could be added, too.
I wondered about that comment ;) I ran pcmcia-cs 3.2.8 with my Orinoco Gold card for several hours last night. Worked fine. I'll wait to see if the gcc 4 patch is applied, and re-test.
Homer; are you using gcc-4?
Let me add a second request for that GCC4 patch, especially since this is supposedly the last version of pcmcia-cs we shouldn't exactly wait for this to be fixed upstream as we are with many GCC4 bugs. With that patch applied pcmcia-cs compiles perfectly on GCC4.
I hope to test everything during the next week (as I eventually got a replacement for my laptop hd so I can test it)
I have added the gcc4 patch to CVS and sent it upstream.
Sorry so long in getting back.. No, i'm not running gcc4, but wanted to make sure it didn't break anything ;) Will test again soon.
Ok, seems to work ok with my Orinoco Gold card.. Do we need to test it with more devices? emerge --info Portage 2.0.51.22-r1 (default-linux/amd64/2005.0, gcc-3.4.3-20050110, glibc-2.3.5-r0, 2.6.11-gentoo-r8 x86_64)================================================================= System uname: 2.6.11-gentoo-r8 x86_64 AMD Athlon(tm) 64 Processor 3200+ Gentoo Base System version 1.6.12 dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.8 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r2, 2.15.92.0.2-r9 sys-devel/libtool: 1.5.18 virtual/os-headers: 2.6.11 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=k8 -fomit-frame-pointer -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -fomit-frame-pointer -O2 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig buildpkg ccache distlocks fixpackages sandbox strict" GENTOO_MIRRORS="ftp://gentoo.netnitco.net/pub/mirrors/gentoo/source/ ftp://mirrors.tds.net/gentoo ftp://gentoo.ccccom.com" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://192.168.1.2/gentoo-portage" USE="amd64 X acpi alsa bash-completion berkdb bitmap-fonts bonobo bzip2 bzlib cdr crypt cups curl dga directfb dvd dvdread eds encode esd ethereal exif fam fbcon flac foomaticdb fortran ftp gdbm geoip gif gimpprint gmp gnome gnomedb gphoto2 gps gstreamer gtk gtk2 gtkhtml hal howl icq ieee1394 imagemagick imap imlib jabber java jp2 jpeg lzw lzw-tiff memlimit mozilla moznocompose moznoirc moznomail mp3 mpeg mpi msession msn ncurses nls no-old-linux nodrm nptl nptlonly offensive ogg oggvorbis opengl oscar oss pam pcmcia pcntl pcre pdflib perl pic png pnp posix ppds pthreads python quicktime readline samba sasl sdl session speex spell ssl sysvipc szip tcltk tcpd tidy tiff truetype truetype-fonts type1-fonts usb userlocales vim-with-x vorbis wxwindows xml2 xmms xpm xrandr xv xvid xvmc yahoo zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
I would say one device tested is sufficient for marking ~ARCH - otherwise it would be difficult to get anybody to test this package.
Added ~amd64, fixed in cvs
Tested and marked ~ppc.
Any progress on this?
My XXS1500 mips unit has been offline for months, and won't be back soon. It has a CF slot accessible via PCMCIA only. Until such time as we have more mips hardware with PCMCIA connections (most commonly via CF slots, as this is the method in the AMD Alchemy systems), I think we should just drop the ~mips keyword, or put pcmcia in use.mask for mips.
Mips herd, please see comment #18 - will you take care of masking USE=pcmcia on mips?
Removed alpha keyword after talking to kloeri. USE=pcmcia is masked on alpha.
I've use.masked pcmcia on MIPS for now in the following profiles: * default-linux/mips * selinux/2005.1/mips * uclibc/mips
