First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 41201
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: foser (RETIRED) <foser@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Molchanov Alexander <xorader@mail.ru>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
fam-error Error compiling app-admin/fam-2.7.0-r2 text/plain Andres 2005-01-02 08:51 0000 3.21 KB Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 41201 depends on: Show dependency tree
Show dependency graph
Bug 41201 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: 2004-02-10 22:27 0000
# emerge -v fam
Calculating dependencies ...done!
>>> emerge (1 of 1) app-admin/fam-2.7.0 to /
>>> md5 src_uri ;-) fam-2.7.0.tar.gz
>>> Unpacking source...
>>> Unpacking fam-2.7.0.tar.gz to /var/tmp/portage/fam-2.7.0/work
autom4te-2.58: cannot open configure: Permission denied

!!! ERROR: app-admin/fam-2.7.0 failed.
!!! Function src_unpack, Line 22, Exitcode 1
!!! autoconf failed

# tar tzvf fam-2.7.0.tar.gz | egrep "/configure$"
-r-xr-xr-x mraymond/os  347684 2003-11-26 22:47:26 fam-2.7.0/configure

-----

ok, change ebuild:
# diff -U4 fam-2.7.0.ebuild.old fam-2.7.0.ebuild 
--- fam-2.7.0.ebuild.old        2004-02-11 09:20:17.044287962 +0300
+++ fam-2.7.0.ebuild    2004-02-11 09:20:40.575239062 +0300
@@ -17,8 +17,9 @@
 src_unpack() {
        unpack ${A}
        cd ${S}
        libtoolize -c -f || die "libtoolize failed"
+       chmod u+w configure
        aclocal || die "aclocal failed"
        autoconf || die "autoconf failed"
 }
----
# emerge -v fam
Calculating dependencies ...done!
>>> emerge (1 of 1) app-admin/fam-2.7.0 to /
>>> md5 src_uri ;-) fam-2.7.0.tar.gz
>>> Unpacking source...
>>> Unpacking fam-2.7.0.tar.gz to /var/tmp/portage/fam-2.7.0/work
>>> Source unpacked.
[... skiped ...]
make[2]: Entering directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib'
[... skiped ...]
/bin/sh ../libtool --mode=link g++  -O2 -mcpu=i686 -pipe   -o libfam.la -rpath /usr/lib -export-symbols fam.sym Client.lo fam.lo -lstdc++ -lrpcsvc 
rm -fr .libs/libfam.la .libs/libfam.* .libs/libfam.*
g++ "{ global:" > .libs/libfam.ver
g++: { global:: No such file or directory
g++: no input files
make[2]: *** [libfam.la] Error 1
make[2]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0'
make: *** [all] 

------- Comment #1 From Molchanov Alexander 2004-02-10 22:27:06 0000 -------
# emerge -v fam
Calculating dependencies ...done!
>>> emerge (1 of 1) app-admin/fam-2.7.0 to /
>>> md5 src_uri ;-) fam-2.7.0.tar.gz
>>> Unpacking source...
>>> Unpacking fam-2.7.0.tar.gz to /var/tmp/portage/fam-2.7.0/work
autom4te-2.58: cannot open configure: Permission denied

!!! ERROR: app-admin/fam-2.7.0 failed.
!!! Function src_unpack, Line 22, Exitcode 1
!!! autoconf failed

# tar tzvf fam-2.7.0.tar.gz | egrep "/configure$"
-r-xr-xr-x mraymond/os  347684 2003-11-26 22:47:26 fam-2.7.0/configure

-----

ok, change ebuild:
# diff -U4 fam-2.7.0.ebuild.old fam-2.7.0.ebuild 
--- fam-2.7.0.ebuild.old        2004-02-11 09:20:17.044287962 +0300
+++ fam-2.7.0.ebuild    2004-02-11 09:20:40.575239062 +0300
@@ -17,8 +17,9 @@
 src_unpack() {
        unpack ${A}
        cd ${S}
        libtoolize -c -f || die "libtoolize failed"
+       chmod u+w configure
        aclocal || die "aclocal failed"
        autoconf || die "autoconf failed"
 }
----
# emerge -v fam
Calculating dependencies ...done!
>>> emerge (1 of 1) app-admin/fam-2.7.0 to /
>>> md5 src_uri ;-) fam-2.7.0.tar.gz
>>> Unpacking source...
>>> Unpacking fam-2.7.0.tar.gz to /var/tmp/portage/fam-2.7.0/work
>>> Source unpacked.
[... skiped ...]
make[2]: Entering directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib'
[... skiped ...]
/bin/sh ../libtool --mode=link g++  -O2 -mcpu=i686 -pipe   -o libfam.la -rpath /usr/lib -export-symbols fam.sym Client.lo fam.lo -lstdc++ -lrpcsvc 
rm -fr .libs/libfam.la .libs/libfam.* .libs/libfam.*
g++ "{ global:" > .libs/libfam.ver
g++: { global:: No such file or directory
g++: no input files
make[2]: *** [libfam.la] Error 1
make[2]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/fam-2.7.0/work/fam-2.7.0'
make: *** [all] ïÛÉÂËÁ 2

!!! ERROR: app-admin/fam-2.7.0 failed.
!!! Function src_compile, Line 418, Exitcode 2
!!! emake failed

Reproducible: Always
Steps to Reproduce:
1. emerge -v fam
2.
3.

Actual Results:  
# emerge -v fam
Calculating dependencies ...done!
>>> emerge (1 of 1) app-admin/fam-2.7.0 to /
>>> md5 src_uri ;-) fam-2.7.0.tar.gz
>>> Unpacking source...
>>> Unpacking fam-2.7.0.tar.gz to /var/tmp/portage/fam-2.7.0/work
autom4te-2.58: cannot open configure: Permission denied

------- Comment #2 From Molchanov Alexander 2004-02-10 22:38:11 0000 -------
# gcc --version
gcc (GCC) 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, propolice-3.3-7)
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

# autoconf --version
autoconf (GNU Autoconf) 2.58
Written by David J. MacKenzie and Akim Demaille.

Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

# make --version
GNU Make 3.80
Copyright (C) 2002  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.

# emerge -pv glibc  

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild   R   ] sys-libs/glibc-2.3.2-r9  -build +nls -nptl -pic  0 kB

# ldd --version
ldd (GNU libc) 2.3.2
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

------- Comment #3 From Molchanov Alexander 2004-02-10 22:56:23 0000 -------
http://forums.gentoo.org/viewtopic.php?t=113225&highlight=fam

------- Comment #4 From Molchanov Alexander 2004-02-10 23:11:55 0000 -------
-------------
1) batang_gentoo wrote:

"
The following: 
Code:	
#       cd ${S} 
#       libtoolize -c -f || die "libtoolize failed" 
#       aclocal || die "aclocal failed" 
#       autoconf || die "autoconf failed" 
	


works because this was the cause of the problem as I have pointed out above in my previous post. But the question is, why did the ebuild author find it necessary to update the autotools files in the FAM package when they are working just fine as they are? 

I think there is a bug in the aclocal.m4 file that comes with the libtool-1.4.3-r3 package which is causing the compile error. 

EDIT: 
This is a confirmed bug in libtool-1.4.3 that causes this. I already filed a bug report #41140. 

See here for references: 
http://mail.gnome.org/archives/garnome-list/2003-August/msg00070.html 
http://mail.gnome.org/archives/garnome-list/2003-August/msg00073.html
"

-------------

2) solution:
+++
a) nano -w /usr/portage/app-admin/fam/fam-2.7.0.ebuild 

src_unpack() { 
        unpack ${A} 
        chmod u+w ${S}/configure
#       cd ${S} 
#       libtoolize -c -f || die "libtoolize failed" 
#       aclocal || die "aclocal failed" 
#       autoconf || die "autoconf failed" 
}

+++
b) emerge app-admin/fam-2.7.0 
<error occurs> 
cd /var/tmp/portage/fam-2.7.0/work/fam-2.7.0/lib 
../libtool g++  -g -O2   -o libfam.la -rpath /usr/local/lib -export-symbols fam.sym Client.lo fam.lo -lstdc++ -lrpcsvc 
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild compile 
ebuild /usr/portage/app-admin/fam/fam-2.7.0.ebuild merge

-------------
P.S.
sorry for spam, guys :(

------- Comment #5 From Alexander Holler 2004-02-11 02:10:37 0000 -------
I can confirm the bug and the solution.

------- Comment #6 From foser (RETIRED) 2004-02-11 03:26:14 0000 -------
@vapier, you make changes to a pack assigned to me in a marked stable ebuild
and i don't even get notified. This is _wrong_, very wrong, all of it.

Solve it yourself.

------- Comment #7 From foser (RETIRED) 2004-02-11 03:53:44 0000 -------
*** Bug 41140 has been marked as a duplicate of this bug. ***

------- Comment #8 From André Terpstra 2004-02-11 04:24:35 0000 -------
Confirmed. This BTW only happens in a "stable" 2.6 kernel-based installation. I
also have un unstable (ACCEPT="~x86") 2.6 installation where fam-2.7.0 compiled
without errors a few days ago.

------- Comment #9 From Caleb Tennis 2004-02-11 07:31:03 0000 -------
*** Bug 41214 has been marked as a duplicate of this bug. ***

------- Comment #10 From Christopher Sachs 2004-02-11 11:12:23 0000 -------
fam-2.7.0 fails while trying to build KDE 3.2 on a fresh x86 gentoo system.

Last few lines of console look like this:

g++ "{ global:" > .libs/libfam.* .libs/libfam.*
g++: { global:: No such file or directory
g++: no input files
make[2]: *** [libfam.la] Error 1
make[2]: Leaving directory '/var/tmp/portage/fam-2.7.0/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/var/tmp/portage/fam-2.7.0'
make: *** [all] Error 2

!!! ERROR: app-admin/fam-2.7.0 failed.
!!! Function src_compile, Line 410, Exitcode 2
!!! emake failed

------- Comment #11 From Chris Gianelloni 2004-02-11 11:43:37 0000 -------
foser: mind if I fix this rather than waiting around for SpanKY?

------- Comment #12 From bobo1@bocklabs.wisc.edu 2004-02-11 12:20:22 0000 -------
I don't care who fixes it. It's holding up a lot of people who want to emerge
the latest KDE version.

------- Comment #13 From Chris Gianelloni 2004-02-11 14:24:48 0000 -------
That's nice... except that I have enough respect for other devs to NOT touch
ANY package which is actively maintained by another dev without first getting
his permission... even if it IS a simple fix...

------- Comment #14 From Chris Gianelloni 2004-02-11 14:47:34 0000 -------
Sorry about that last comment... it came out quite a bit worse than I had
intended...

------- Comment #15 From Chris Gianelloni 2004-02-11 14:50:03 0000 -------
<seemant> what happened with fam?
<wolf31o2-work> just a sec and I'll pull the bug #
<wolf31o2-work> http://bugs.gentoo.org/show_bug.cgi?id=41201
<wolf31o2-work> anyway... I have a fixed local copy...
<seemant> and you can fix with having both foser's and spank's changes in it?
<seemant> if so, please do commit them
<seemant> if anyone has a problem with it, I'll take the heat

I applied the fix submitted by Molchanov Alexander <xorader@mail.ru> to the ebuild, so everything should be hunky-dory now.

------- Comment #16 From Julien Allanos (RETIRED) 2004-02-11 16:49:54 0000 -------
emerged fine just by modifying the src_unpack() function like this:

 src_unpack() { 
        unpack ${A} 
        chmod u+w ${S}/configure
#       cd ${S} 
#       libtoolize -c -f || die "libtoolize failed" 
#       aclocal || die "aclocal failed" 
#       autoconf || die "autoconf failed" 
}

now, i hope there will be a commit to cvs soon, otherwise marking this bug as fixed makes no sense.

------- Comment #17 From Chris Gianelloni 2004-02-11 17:09:26 0000 -------
The fix has already been applied to CVS when I posted my last message.

Try emerge sync and see if you have the new version.

------- Comment #18 From SpanKY 2004-02-11 17:39:36 0000 -------
alright, i'll pass libtool bugs your way next time, sorry about that

also, i hope you put a DEPEND=">libtool-1.5.2-r2" otherwise you'll might start getting people with broken fams again (libs without a .so)

but this is your package so i wont touch it again

------- Comment #19 From SpanKY 2004-02-11 17:41:36 0000 -------
err, that wouldnt work since 1.5.2 is in unstable

at any rate, that autotools code worked for stable and unstable and people who arent using latest libtool will have broken fam's again

------- Comment #20 From SpanKY 2004-02-11 21:22:06 0000 -------
*** Bug 41324 has been marked as a duplicate of this bug. ***

------- Comment #21 From Julien Allanos (RETIRED) 2004-02-12 03:30:22 0000 -------
i did a sync before posting my comment, but i think the mirror wouldn't have
been up to date. i synced this morning, the ebuild is fixed. sorry for
inconvenience.

------- Comment #22 From Caleb Tennis 2004-02-12 06:23:41 0000 -------
*** Bug 41352 has been marked as a duplicate of this bug. ***

------- Comment #23 From SpanKY 2004-02-12 10:43:57 0000 -------
*** Bug 41397 has been marked as a duplicate of this bug. ***

------- Comment #24 From foser (RETIRED) 2004-02-13 05:13:08 0000 -------
*** Bug 41436 has been marked as a duplicate of this bug. ***

------- Comment #25 From André Terpstra 2004-02-13 05:42:55 0000 -------
Fix confirmed.

------- Comment #26 From foser (RETIRED) 2004-02-13 10:08:19 0000 -------
*** Bug 41479 has been marked as a duplicate of this bug. ***

------- Comment #27 From Andres 2005-01-02 08:51:21 0000 -------
Created an attachment (id=47382) [edit]
Error compiling app-admin/fam-2.7.0-r2

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