| View previous topic :: View next topic |
| Author |
Message |
geraint0923
n00b
Joined: 28 Jan 2011
Posts: 31
|
 Posted: Mon Jul 04, 2011 8:29 am Post subject: [SOLVED]emerged codeblocks-9999 failed |
 |
|
Today when tried to emerge codeblocks-9999 ,it told me "Failed Running aclocal"
| Code: |
localhost gy # emerge -av codeblocks
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild N *] dev-util/codeblocks-9999 USE="contrib -debug -pch -static-libs" 0 kB
Total: 1 package (1 new), Size of downloads: 0 kB
Would you like to merge these packages? [Yes/No] y
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) dev-util/codeblocks-9999
* Package: dev-util/codeblocks-9999
* Repository: gentoo
* Maintainer: wxwidgets@gentoo.org
* USE: amd64 contrib elibc_glibc kernel_linux multilib userland_GNU
* FEATURES: ccache sandbox
>>> Unpacking source...
>>> Source unpacked in /var/tmp/portage/dev-util/codeblocks-9999/work
>>> Preparing source in /var/tmp/portage/dev-util/codeblocks-9999/work ...
svn: '.' is not a working copy
* Running eautoreconf in '/var/tmp/portage/dev-util/codeblocks-9999/work' ...
* Running aclocal ... [ !! ]
* Failed Running aclocal !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/dev-util/codeblocks-9999/temp/aclocal.out
* ERROR: dev-util/codeblocks-9999 failed (prepare phase):
* Failed Running aclocal !
*
* Call stack:
* ebuild.sh, line 56: Called src_prepare
* environment, line 3298: Called eautoreconf
* environment, line 1053: Called eaclocal
* environment, line 986: Called autotools_run_tool 'aclocal'
* environment, line 550: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
*
* If you need support, post the output of 'emerge --info =dev-util/codeblocks-9999',
* the complete build log and the output of 'emerge -pqv =dev-util/codeblocks-9999'.
* The complete build log is located at '/var/tmp/portage/dev-util/codeblocks-9999/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/codeblocks-9999/temp/environment'.
* S: '/var/tmp/portage/dev-util/codeblocks-9999/work/codeblocks-9999'
>>> Failed to emerge dev-util/codeblocks-9999, Log file:
>>> '/var/tmp/portage/dev-util/codeblocks-9999/temp/build.log'
* Messages for package dev-util/codeblocks-9999:
* Failed Running aclocal !
*
* Include in your bugreport the contents of:
*
* /var/tmp/portage/dev-util/codeblocks-9999/temp/aclocal.out
* ERROR: dev-util/codeblocks-9999 failed (prepare phase):
* Failed Running aclocal !
*
* Call stack:
* ebuild.sh, line 56: Called src_prepare
* environment, line 3298: Called eautoreconf
* environment, line 1053: Called eaclocal
* environment, line 986: Called autotools_run_tool 'aclocal'
* environment, line 550: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
*
* If you need support, post the output of 'emerge --info =dev-util/codeblocks-9999',
* the complete build log and the output of 'emerge -pqv =dev-util/codeblocks-9999'.
* The complete build log is located at '/var/tmp/portage/dev-util/codeblocks-9999/temp/build.log'.
* The ebuild environment file is located at '/var/tmp/portage/dev-util/codeblocks-9999/temp/environment'.
* S: '/var/tmp/portage/dev-util/codeblocks-9999/work/codeblocks-9999'
|
I have ever emerged codeblocks-9999 on another computer ,and it svn the source code from svn server and then compiled the source code. But this time, I was working on my new laptop, and failed. 
I tried emerge codeblocks on another computer ,however ,it told me that:
| Code: |
localhost usbdisk # emerge codeblocks
Calculating dependencies... done!
>>> Verifying ebuild manifests
>>> Emerging (1 of 1) dev-util/codeblocks-9999
* Package: dev-util/codeblocks-9999
* Repository: gentoo
* Maintainer: wxwidgets@gentoo.org
* USE: amd64 elibc_glibc kernel_linux multilib pch userland_GNU
* FEATURES: ccache sandbox
>>> Unpacking source...
* subversion update start -->
* repository: svn://svn.berlios.de/codeblocks/trunk
|
And I have subversion installed on both two computers with the same USEs,and portage of two computers have the same version and USEs.
Is there any operation I can do to fix my portage?
Thanks in advance.
aclocal.out:
| Code: |
***** aclocal *****
***** PWD: /var/tmp/portage/dev-util/codeblocks-9999/work
***** aclocal
aclocal-1.11: `configure.ac' or `configure.in' is required
|
Last edited by geraint0923 on Fri Jul 08, 2011 11:52 am; edited 3 times in total |
|
| Back to top |
|
 |
Raptor85
Apprentice
Joined: 29 Dec 2007
Posts: 208
|
| Posted: Tue Jul 05, 2011 10:46 pm Post subject: |
|
|
| Quote: | * Include in your bugreport the contents of:
*
* /var/tmp/portage/dev-util/codeblocks-9999/temp/aclocal.out |
might want to post this too, off the top of my head though only thing i can think of is autotools being broken |
|
| Back to top |
|
|
geraint0923
n00b
Joined: 28 Jan 2011
Posts: 31
|
| Posted: Wed Jul 06, 2011 11:12 am Post subject: |
|
|
| Raptor85 wrote: | | Quote: | * Include in your bugreport the contents of:
*
* /var/tmp/portage/dev-util/codeblocks-9999/temp/aclocal.out |
might want to post this too, off the top of my head though only thing i can think of is autotools being broken |
I post the aclocal.out above just now.
I think the problem may not be on aclocal, I can emerge other packages without any problem.
The portage should have checkout the source code from server before aclocal ,but it didn't. |
|
| Back to top |
|
|
Raptor85
Apprentice
Joined: 29 Dec 2007
Posts: 208
|
| Posted: Wed Jul 06, 2011 8:29 pm Post subject: |
|
|
*facepalm* i guess i mentally skipped over that line
Check if there's an existing directory in /var/tmp/portage/ for the codeblocks source, delete it and remerge if there is, also check under the distfiles directory. You can also open the ebuild itself and test checking out the sources using the SVN path there.
Could be a problem with the SVN checkout command in the ebuild also, but i'd think it would be unlikely in a major package like codeblocks |
|
| Back to top |
|
|
keenblade
Veteran
Joined: 03 Oct 2004
Posts: 1087
|
| Posted: Wed Jul 06, 2011 9:14 pm Post subject: |
|
|
It seems to be a bug or a change in portage. If you put this before src_prepare(), it will work:
| Code: |
src_unpack() {
subversion_src_unpack
}
|
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1" |
|
| Back to top |
|
|
geraint0923
n00b
Joined: 28 Jan 2011
Posts: 31
|
| Posted: Thu Jul 07, 2011 1:47 am Post subject: |
|
|
| Raptor85 wrote: | *facepalm* i guess i mentally skipped over that line
Check if there's an existing directory in /var/tmp/portage/ for the codeblocks source, delete it and remerge if there is, also check under the distfiles directory. You can also open the ebuild itself and test checking out the sources using the SVN path there.
Could be a problem with the SVN checkout command in the ebuild also, but i'd think it would be unlikely in a major package like codeblocks |
I tried to clean up /var/tmp/portage/* ,but it didn't seem to work.
And I can checkout svn://svn.berlios.de/codeblocks/trunk using "svn checkout svn://svn.berlios.de/codeblocks/trunk" and then make it. But I don't want to checkout the source code by myself every time when I emerge using svn.
Yesterday ,I installed gnome3 from gnome overlay and it seemed to be alright when portage working with git. |
|
| Back to top |
|
|
Hu
Administrator
Joined: 06 Mar 2007
Posts: 22088
|
| Posted: Thu Jul 07, 2011 1:55 am Post subject: |
|
|
| keenblade wrote: | It seems to be a bug or a change in portage. If you put this before src_prepare(), it will work:
| Code: |
src_unpack() {
subversion_src_unpack
}
|
|
If the above definition works, that suggests that a different src_unpack (other than the one from subversion.eclass) is being used by default. |
|
| Back to top |
|
|
keenblade
Veteran
Joined: 03 Oct 2004
Posts: 1087
|
| Posted: Thu Jul 07, 2011 2:19 am Post subject: |
|
|
| Hu wrote: | | keenblade wrote: | It seems to be a bug or a change in portage. If you put this before src_prepare(), it will work:
| Code: |
src_unpack() {
subversion_src_unpack
}
|
|
If the above definition works, that suggests that a different src_unpack (other than the one from subversion.eclass) is being used by default. |
That definition works. That's why I think it is a portage bug. Without that definition, no sources are checked out and are unpacked, thus emerge fails.
This seems to affect only subversion vcs, but not all of them. For ex. mplayer-9999 from svn works.
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1" |
|
| Back to top |
|
|
geraint0923
n00b
Joined: 28 Jan 2011
Posts: 31
|
| Posted: Thu Jul 07, 2011 2:56 am Post subject: |
|
|
| keenblade wrote: | It seems to be a bug or a change in portage. If you put this before src_prepare(), it will work:
| Code: |
src_unpack() {
subversion_src_unpack
}
|
|
It works! I can emerge it after I add the definition.
Thank you very much!
But why can I emerge codeblocks without modifying the ebuild on another computer which has the same version and USEs portage as this computer? |
|
| Back to top |
|
|
keenblade
Veteran
Joined: 03 Oct 2004
Posts: 1087
|
| Posted: Thu Jul 07, 2011 10:14 am Post subject: |
|
|
| geraint0923 wrote: |
It works! I can emerge it after I add the definition.
Thank you very much!
But why can I emerge codeblocks without modifying the ebuild on another computer which has the same version and USEs portage as this computer? |
Nice, that worked for you, too.
Could you file a bug report at b.g.o .
_________________
Anyway it's all the same at the end...
Need help to get it working: "x-fi surround 5.1" |
|
| Back to top |
|
|
geraint0923
n00b
Joined: 28 Jan 2011
Posts: 31
|
| Posted: Fri Jul 08, 2011 12:01 pm Post subject: |
|
|
| keenblade wrote: | | geraint0923 wrote: |
It works! I can emerge it after I add the definition.
Thank you very much!
But why can I emerge codeblocks without modifying the ebuild on another computer which has the same version and USEs portage as this computer? |
Nice, that worked for you, too.
Could you file a bug report at b.g.o . |
Absolutely I will.
Thanks again for your great help! |
|
| Back to top |
|
|
|
Portage & Programming
