| Summary: | emerge bluez-utils-2.17-r1 fails with Invalid configuration `emake': machine `emake' not recognized | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Colin Tinker <g1gsw> |
| Component: | New packages | Assignee: | Mobile Herd (OBSOLETE) <mobile+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | Dan.Johansson, idunno2468, pda, tschenturs |
| Priority: | High | Keywords: | InVCS |
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
config.log for bluez-utils
configure log |
||
|
Description
Colin Tinker
2005-06-25 05:27:12 UTC
Created attachment 61905 [details]
config.log for bluez-utils
config log
Created attachment 61906 [details]
configure log
I'm also getting this error on my Laptop while doing an "emerge --update --deep
--verbose world". I've attached the configure-log.
same over here: $ emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.12- gentoo-r1 i686) ================================================================= System uname: 2.6.12-gentoo-r1 i686 Intel(R) Pentium(R) M processor 2.00GHz Gentoo Base System version 1.6.12 Python: dev-lang/python-2.4.1-r1,dev-lang/python-2.3.5 [2.4.1 (#1, Jun 17 2005, 07:52:08)] distcc 2.18.3 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [enabled] ccache version 2.3 [enabled] dev-lang/python: 2.4.1-r1, 2.3.5 sys-apps/sandbox: [Not Present] sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.16 virtual/os-headers: 2.6.8.1-r1, 2.6.8.1-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CFLAGS="-march=pentium4 -mcpu=pentium4 -O2 -pipe -fomit-frame-pointer" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3. 4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/texmf/web2c /etc/env.d" CXXFLAGS="-march=pentium4 -mcpu=pentium4 -O2 -pipe -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig candy ccache distcc distlocks emergemail fixpackages nostrip sandbox sfperms strict" GENTOO_MIRRORS="http://sunsite.cnlab-switch.ch/ftp/mirror/gentoo ftp://ftp.tu-clausthal.de/pub/linux/ gentoo http://www.ibiblio.org/pub/Linux/distributions/gentoo" LANG="de_CH.UTF-8" LC_ALL="de_CH.UTF-8" LINGUAS="de" MAKEOPTS="-j5" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.i-no.de/gentoo-portage" USE="x86 X aalib acpi alsa apache2 arts avi bash-completion berkdb bitmap-fonts bluetooth bonobo cdr crypt cups curl dga directfb doc dvd dvdr dvdread emacs emboss encode examples exif fam flac foomaticdb fortran gcj gd gdbm gif gphoto2 gpm gtk gtk2 gtkhtml guile imagemagick imap imlib irda java jpeg junit kde lcms libg++ libwww mad maildir mikmod mmx mng motif mp3 mpeg mssql mysql ncurses nls nptl odbc ogg oggvorbis opengl pam pcmcia pda pdflib perl pic png pnp postgres python qt quicktime readline real ruby samba sasl scanner sdl slang speex spell sqlite sse sse2 ssl svg svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts unicode usb vorbis win32codecs wmf xml xml2 xmms xprint xv xvid yaz zlib video_cards_radeon linguas_de userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CBUILD, CTARGET, LDFLAGS Same problem here. A diff of bluez-utils-2.17.ebuild and
bluez-utils-2.17-r1.ebuild shows now change (but in the header).
Diff of bluez-utils-2.16-r1.ebuild and bluez-utils-2.17-r1.ebuild shows the problem:
@@ -52,7 +52,8 @@
--disable-initscripts \
--enable-obex \
--enable-hid2hci \
- --enable-bcm203x
+ --enable-bcm203x \
+ --localstatedir=/var \
emake || die "make failed"
}
The backslash in the line before emake is the culprit.
Alastair, I took the liberty of fixing this issue by adding a '|| die' statement to both 2.17 and 2.17-r1 since I was also affected by this. whoops! sorry for the mistake :( thanks brix! |
