Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[solved] AMD64 fails all emerges in chroot during install
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Duplicate Threads
View previous topic :: View next topic  
Author Message
schmeggahead
Guru
Guru


Joined: 25 Feb 2003
Posts: 314
Location: Columbus, Ohio

PostPosted: Sat Jan 09, 2010 6:37 pm    Post subject: [solved] AMD64 fails all emerges in chroot during install Reply with quote

I need a minimum of lvm2 to emerge during the chroot to bring the system configuration up.

Here is the error (happens no matter what I emerge)

Code:
>>> Failed to emerge sys-fs/lvm2-2.02.56-r2, Log file:

>>>  '/var/tmp/portage/sys-fs/lvm2-2.02.56-r2/temp/build.log'

 * Messages for package sys-fs/lvm2-2.02.56-r2:

 * Warning, we no longer overwrite /sbin/lvm and /sbin/dmsetup with
 * their static versions. If you need the static binaries,
 * you must append .static the filename!
 * Failed Running autoconf !
 *
 * Include in your bugreport the contents of:
 *
 *   /var/tmp/portage/sys-fs/lvm2-2.02.56-r2/temp/autoconf.out
 *
 * ERROR: sys-fs/lvm2-2.02.56-r2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_prepare
 *             environment, line 2898:  Called eautoreconf
 *             environment, line  899:  Called eautoconf
 *             environment, line  841:  Called autotools_run_tool 'autoconf'
 *             environment, line  383:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 *  The die message:
 *   Failed Running autoconf !
 *
 * 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/sys-fs/lvm2-2.02.56-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-fs/lvm2-2.02.56-r2/temp/environment'.
 *


I am using the current AMD64 (non hardened) stage and gentoo-sources

I have seen others who solved this by booting in the new environment because chroot caused errors with syslog-ng
I get it on all emerges and cannot boot without LVM

:cry:

The ebuild log:

Code:
***** autoconf *****
***** PWD: /var/tmp/portage/sys-fs/lvm2-2.02.56-r2/work/LVM2.2.02.56
***** autoconf

configure.in:85: error: possibly undefined macro: AC_CHECK_HEADERS
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.in:138: error: possibly undefined macro: AC_MSG_RESULT


Last edited by schmeggahead on Sat Jan 09, 2010 6:43 pm; edited 1 time in total
Back to top
View user's profile Send private message
schmeggahead
Guru
Guru


Joined: 25 Feb 2003
Posts: 314
Location: Columbus, Ohio

PostPosted: Sat Jan 09, 2010 6:42 pm    Post subject: Reply with quote

found a solution here:

https://forums.gentoo.org/viewtopic-t-809553-highlight-accheckheaders.html

trying it now.
Back to top
View user's profile Send private message
schmeggahead
Guru
Guru


Joined: 25 Feb 2003
Posts: 314
Location: Columbus, Ohio

PostPosted: Sat Jan 09, 2010 6:45 pm    Post subject: Reply with quote

solved the problem.

emerges work.
this was reported 1/3/2010.

How do I determine if a bug was actually filed so developers know of the bug?
Back to top
View user's profile Send private message
pilla
Administrator
Administrator


Joined: 07 Aug 2002
Posts: 7216
Location: Pelotas, BR

PostPosted: Sun Jan 10, 2010 12:32 am    Post subject: Reply with quote

schmeggahead wrote:

How do I determine if a bug was actually filed so developers know of the bug?


Search for the bug in the bugzilla, if it is not there yet, you may report it yourself.

Please continue discussion in the other thread. Moved to Dups.
_________________
"I'm just very selective about the reality I choose to accept." -- Calvin
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Duplicate Threads All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum