First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 130118
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Stefan Briesenick <sbriesen@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Scott Short <scottsshort@gmail.com>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 130118 depends on: Show dependency tree
Show dependency graph
Bug 130118 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)







View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2006-04-15 19:56 0000
Portage 2.1_pre7-r5 (default-linux/x86/2006.0, gcc-4.2.0-alpha20060408,
glibc-2.4-r1, 2.6.16-beyond2 i686)
=================================================================
System uname: 2.6.16-beyond2 i686 AMD Athlon(tm) Processor
Gentoo Base System version 1.12.0_pre17
ccache version 2.4 [enabled]
dev-lang/python:     2.4.2-r1
sys-apps/sandbox:    1.2.17
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2
sys-devel/binutils:  2.16.1-r2
sys-devel/libtool:   1.5.22
virtual/os-headers:  2.6.11-r3
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-march=athlon-xp -O3 -fomit-frame-pointer -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env
/usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config
/usr/lib/mozilla/defaults/pref /usr/share/X11/xkb /usr/share/config
/var/qmail/control"
CONFIG_PROTECT_MASK="/etc/eselect/compiler /etc/gconf /etc/revdep-rebuild
/etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-march=athlon-xp -O3 -fomit-frame-pointer -pipe"
DISTDIR="/portage/distfiles"
FEATURES="autoconfig ccache distlocks fixpackages metadata-transfer sandbox
sfperms strict"
GENTOO_MIRRORS="http://www.gtlib.gatech.edu/pub/gentoo
http://distfiles.gentoo.org
http://distro.ibiblio.org/pub/linux/distributions/gentoo"
MAKEOPTS="-j2"
PKGDIR="/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/portage"
PORTDIR_OVERLAY="/usr/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X alsa apache2 apm arts asf avi berkdb bitmap-fonts browserplugin
bzip2 cli crypt ctype cups curl dba dri eds emacs emboss encode esd expat
fastbuild foomaticdb force-cgi-redirect fortran ftp gd gdbm gif gimp gimpprint
gmp gnutls gpm gstreamer gtk gtk2 imagemagick imlib ipv6 isdnlog java jpeg
jpeg2k libg++ libwww logrotate mad md5sum memlimit mikmod motif mozilla
moznoirc moznomail mp3 mpeg ncurses nls nptl nptlonly nsplugin numeric nvidia
objc objc++ offensive ogg opengl oss pam pcre pdflib perl pic png posix ppds
pppd python quicktime readline real rtc sdl session simplexml soap sockets
spell spl ssl tcpd tokenizer toolbar truetype truetype-fonts type1-fonts udev
usb vorbis win32codecs wmf xchat xemacs xine xml xml2 xmms xsl xv zlib
elibc_glibc input_devices_keyboard input_devices_mouse kernel_linux
userland_GNU video_cards_nvidia video_cards_via video_cards_vga"
Unset:  ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL,
LDFLAGS, LINGUAS

I just made a simple correction to the ebuild & it compiles clean now. 
Change 3.4|4.[01]) to [20] 

pkg_setup() {
    local i
    if ! use x86 && ( use X || use gimp ); then
        ewarn
        ewarn "The iscan application needs CSS x86-only libs and"
        ewarn "thus can't be built currently. You can still use"
        ewarn "'xscanimage', 'xsane' or 'kooka' with sane-epkowa"
        ewarn "backend. But some low-end scanners are also not"
        ewarn "supported, because they need these x86 libs, too."
        ewarn
    fi

    # Select correct tarball for installed GCC. This is not a perfect
    # solution and should be expanded to other working GCC versions.
    einfo "GCC version: $(gcc-fullversion)"
    case "$(gcc-version)" in
        3.[23])
            if use x86; then
                MY_A="${SRC_GCC33##*/}"
                for i in ${BIN_GCC33}; do MY_A="${MY_A} ${i##*/}"; done
            else  # fallback to GCC 3.4, should not harm.
                MY_A="${SRC_GCC34##*/}"
                for i in ${BIN_GCC34}; do MY_A="${MY_A} ${i##*/}"; done
            fi
            ;;
        3.4|4.[01])  # 4.x seems to work (tested with Perfection 3490 PHOTO)
            MY_A="${SRC_GCC34##*/}"
            for i in ${BIN_GCC34}; do MY_A="${MY_A} ${i##*/}"; done
            ;;
        *)
            if use x86; then
                die "Your GCC version is not supported. You need either 3.2,
3.3, 3.4 or 4.x!"
            else
                MY_A="${SRC_GCC34##*/}"  # fallback to GCC 3.4, should not
harm.
                for i in ${BIN_GCC34}; do MY_A="${MY_A} ${i##*/}"; done
            fi
            ;;
    esac
}

------- Comment #1 From Jakub Moc 2006-04-16 02:41:47 0000 -------
Please, attach a unified diff next time, instead of pasting an (unfixed) ebuild
snip.

------- Comment #2 From Stefan Briesenick 2006-04-16 04:12:32 0000 -------
> Change 3.4|4.[01]) to [20]

wrong. Learn shellscript. ;-)

4.[01] means 4.0 *and* 4.1. You want 4.[012] if 4.2 also works (untested by me,
so it wasn't enabled).

I will fix it later...

------- Comment #3 From Stefan Briesenick 2006-04-16 04:17:23 0000 -------
in CVS. But no new revision (stays -r1).

------- Comment #4 From Stefan Briesenick 2006-04-16 04:18:00 0000 -------
forgot to "fix" this bug. ;-)

------- Comment #5 From Scott Short 2006-04-16 05:04:53 0000 -------
(In reply to comment #2)
> > Change 3.4|4.[01]) to [20]
> 
> wrong. Learn shellscript. ;-)
> 
> 4.[01] means 4.0 *and* 4.1. You want 4.[012] if 4.2 also works (untested by me,
> so it wasn't enabled).
> 
> I will fix it later...
> 

Thanks, I know I need to learn shellscript (I'm a first year computer science
student). But I am trying to contribute/help as much as I can. I have run this
build with a perfection 3170 photo scanner for a good bit & there are no
problems that I can see. I'll correct my overlay. [012] again, thanks, Scott.

First Last Prev Next    No search results available      Search page      Enter new bug