Bug 208292 - app-laptop/acer_acpi-0.5 doesn't compile w/ kernel 2.6.24 - CFLAGS was changed
|
Bug#:
208292
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: AMD64
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: normal
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: jurek@gentoo.org
|
Reported By: sapaly.nicolas@free.fr
|
|
Component: Ebuilds
|
|
|
URL:
|
|
Summary: app-laptop/acer_acpi-0.5 doesn't compile w/ kernel 2.6.24 - CFLAGS was changed
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2008-01-31 12:58 0000
|
After kernel upgrade (from 2.6.23-gentoo-r5 to 2.6.24-gentoo), acer_acpi-0.5
can't compile.
(I upgrade linux-headers to linux-headers-2.6.24 and recompile glibc)
Build.log :
* Messages for package app-laptop/acer_acpi-0.5:
*
* ERROR: app-laptop/acer_acpi-0.5 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1383: Called linux-mod_src_compile
* linux-mod.eclass, line 519: Called die
* The specific snippet of code:
* emake HOSTCC="$(tc-getBUILD_CC)" CC="$(get-KERNEL_CC)"
LDFLAGS="$(get_abi_LDFLAGS)" \
* ${BUILD_FIXES} ${BUILD_PARAMS}
${BUILD_TARGETS} \
* || die "Unable to make ${BUILD_FIXES}
${BUILD_PARAMS} ${BUILD_TARGETS}."
* The die message:
* Unable to make KERNELSRC=/usr/src/linux KERNELVERSION=2.6.24-gentoo all.
*
* If you need support, post the topmost build error, and the call stack if
relevant.
* A complete build log is located at
'/var/tmp/portage/app-laptop/acer_acpi-0.5/temp/build.log'.
Thank you for help
(In reply to comment #0)
> After kernel upgrade (from 2.6.23-gentoo-r5 to 2.6.24-gentoo), acer_acpi-0.5
> can't compile.
> (I upgrade linux-headers to linux-headers-2.6.24 and recompile glibc)
>
Please comment on why you think this text matches your bug so that we can
improve it:
Developer Relations: Maintainer of communication guidelines between fellow
developers
Bugs related to ebuilds belong in 'Gentoo Linux'
Also you didn't post any error whatsoever; attach a full emerge.log, post
emerge --info and reopen the bug then.
Created an attachment (id=142282) [details]
emerge.log
My emerge --info :
Portage 2.1.3.19 (default-linux/amd64/2007.0/no-multilib, gcc-4.1.2,
glibc-2.6.1-r0, 2.6.24-gentoo x86_64)
=================================================================
System uname: 2.6.24-gentoo x86_64 AMD Turion(tm) 64 Mobile Technology ML-30
Timestamp of tree: Tue, 29 Jan 2008 01:16:01 +0000
ccache version 2.4 [enabled]
app-shells/bash: 3.2_p17-r1
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python: 2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
dev-util/ccache: 2.4-r7
sys-apps/baselayout: 1.12.10-r5
sys-apps/sandbox: 1.2.18.1-r2
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10
sys-devel/binutils: 2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool: 1.5.24
virtual/os-headers: 2.6.24
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=k8 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf
/etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-march=k8 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks metadata-transfer sandbox sfperms strict
unmerge-orphans userfetch"
GENTOO_MIRRORS="http://mirror.ovh.net/gentoo-distfiles/
http://gentoo.modulix.net/gentoo/
http://ftp.club-internet.fr/pub/mirrors/gentoo
ftp://ftp.free.fr/mirrors/ftp.gentoo.org/ "
LANG="fr_FR.UTF-8"
LC_ALL="fr_FR.UTF-8"
LINGUAS="fr en"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress
--force --whole-file --delete --delete-after --stats --timeout=180
--exclude=/distfiles --exclude=/local --exclude=/packages
--filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow X acl acpi alsa amd64 apm avahi bash-completion berkdb bitmap-fonts
cairo cdr cjk cli cracklib crypt cups dbus dri dvd dvdr dvdread fortran gdbm
gnome gpm gstreamer gtk gtk2 gtkhtml hal iconv ipv6 isdnlog lm_sensors midi mmx
mudflap ncurses nls nptl nptlonly openmp pam pcre perl pmu pppd python readline
reflection session spl sse sse2 ssl tcpd truetype-fonts type1-fonts unicode vcd
xorg zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci
emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m
maestro3 trident usb-audio via82xx via82xx-modem ymfpci"
ALSA_PCM_PLUGINS="adpcm alaw asym copy dmix dshare dsnoop empty extplug file
hooks iec958 ioplug ladspa lfloat linear meter mulaw multi null plug rate route
share shm softvol" APACHE2_MODULES="actions alias auth_basic authn_alias
authn_anon authn_dbm authn_default authn_file authz_dbm authz_default
authz_groupfile authz_host authz_owner authz_user autoindex cache dav dav_fs
dav_lock deflate dir disk_cache env expires ext_filter file_cache filter
headers include info log_config logio mem_cache mime mime_magic negotiation
rewrite setenvif speling status unique_id userdir usertrack vhost_alias"
ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" LCD_DEVICES="bayrad
cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" LINGUAS="fr en"
USERLAND="GNU" VIDEO_CARDS="radeon"
Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LDFLAGS,
PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS,
PORTDIR_OVERLAY
you can fix this by finding the Makefile that is messing with CFLAGS, then use
a sed in the ebuild to change that to EXTRA_CFLAGS
quick reminder; 2.6.24 will go stable soon
As silly as may workaround sound, it worked for me.
I emerged it a few times in a row and once it worked suddenly.
Sorry, that I cannot tell, why, but I thought even it's no really fix, it might
help finding the problem.
BTW. the kernel 2.6.24 doesn't have any keyword restrictions anymore, doesn't
that mean it's stable?
(In reply to comment #6)
> you can fix this by finding the Makefile that is messing with CFLAGS, then
> use a sed in the ebuild to change that to EXTRA_CFLAGS
I just run into this too :-/ ... and yes, this replacement helps
(In reply to comment #6)
> you can fix this by finding the Makefile that is messing with CFLAGS, then use
> a sed in the ebuild to change that to EXTRA_CFLAGS
>
How can this be done? Thanks for helping! :D
(In reply to comment #10)
> (In reply to comment #6)
> > you can fix this by finding the Makefile that is messing with CFLAGS, then use
> > a sed in the ebuild to change that to EXTRA_CFLAGS
> >
>
> How can this be done? Thanks for helping! :D
>
I had problems with all acer_acpi ebuilds (dont know exactly if i used this
particular version), and found out why, i had MAKEOPTS="-j3" in my make.conf,
commenting it out helped; means it does not build in parallel, same as
MAKEOPTS="-j1".
it builds successfully 100% of the times started.
(In reply to comment #10)
> (In reply to comment #6)
> > you can fix this by finding the Makefile that is messing with CFLAGS, then use
> > a sed in the ebuild to change that to EXTRA_CFLAGS
> >
>
> How can this be done? Thanks for helping! :D
>
I guess something like this was meant:
--- acer_acpi-0.5.ebuild.old 2008-04-06 19:11:57.000000000 +0200
+++ acer_acpi-0.5.ebuild 2008-04-06 19:26:59.000000000 +0200
@@ -21,6 +21,12 @@
BUILD_PARAMS="KERNELSRC=${KV_DIR} KERNELVERSION=${KV_FULL}"
}
+src_unpack() {
+ unpack ${A}
+ cd "${S}"
+ sed -i -e "s/CFLAGS+/EXTRA_CFLAGS/" ${WORKDIR}/${P}/Makefile
+}
+
src_install() {
linux-mod_src_install
dodoc README COPYING NEWS AUTHORS
(In reply to comment #11)
> > (In reply to comment #6)
> > > you can fix this by finding the Makefile that is messing with CFLAGS, then use
> > > a sed in the ebuild to change that to EXTRA_CFLAGS
...
> I had problems with all acer_acpi ebuilds (dont know exactly if i used this
> particular version), and found out why, i had MAKEOPTS="-j3" in my make.conf,
> commenting it out helped; means it does not build in parallel, same as
> MAKEOPTS="-j1".
>
> it builds successfully 100% of the times started.
I wonder how the number of make jobs can affect the hardcoded contents of the
Makefile (a variable name) ...? :-)
> I guess something like this was meant:
>
> --- acer_acpi-0.5.ebuild.old 2008-04-06 19:11:57.000000000 +0200
> +++ acer_acpi-0.5.ebuild 2008-04-06 19:26:59.000000000 +0200
> @@ -21,6 +21,12 @@
> BUILD_PARAMS="KERNELSRC=${KV_DIR} KERNELVERSION=${KV_FULL}"
> }
>
> +src_unpack() {
> + unpack ${A}
> + cd "${S}"
> + sed -i -e "s/CFLAGS+/EXTRA_CFLAGS/" ${WORKDIR}/${P}/Makefile
> +}
> +
> src_install() {
> linux-mod_src_install
> dodoc README COPYING NEWS AUTHORS
>
Thanks for your help! But changing the ebuild file now results in a digest
verification failure. Do I need to put this new ebuild in a portage overlay? Is
this solution temporary?
Thanks!
(In reply to comment #14)
> But changing the ebuild file now results in a digest verification failure.
you can regenerate the digest by running
ebuild /path/to/modified.ebuild digest
> Do I need to put this new ebuild in a portage overlay? Is
> this solution temporary?
yes, you have to put it aside from the main tree (into overlay), else it would
get overwritten on next sync
I am having exactly the same problem with the app-laptop/tp_smapi-0.31 package.
(Gentoo 2008.0_beta1 with kernel 2.6.24-r4)
(In reply to comment #16)
> I am having exactly the same problem with the app-laptop/tp_smapi-0.31 package.
> (Gentoo 2008.0_beta1 with kernel 2.6.24-r4)
>
...but tp_smapi-0.37 (masked by ~) works.
> I had problems with all acer_acpi ebuilds (dont know exactly if i used this
> particular version), and found out why, i had MAKEOPTS="-j3" in my make.conf,
> commenting it out helped; means it does not build in parallel, same as
> MAKEOPTS="-j1".
>
> it builds successfully 100% of the times started.
>
- commenting out MAKEOPTS, actually doesn't work with this bug. At least not
on mine amd64.
But i can confirm that manual change of CFLAGS onto EXTRA_CFLAGS works.