Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 349790 Details for
Bug 471966
=app-arch/pax-3.4.12.16 - configure.in:4: error: 'AM_CONFIG_HEADER': this macro is obsolete.
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
build.log
build.log (text/plain), 2.87 KB, created by
Jason Mours
on 2013-06-01 01:56:24 UTC
(
hide
)
Description:
build.log
Filename:
MIME Type:
Creator:
Jason Mours
Created:
2013-06-01 01:56:24 UTC
Size:
2.87 KB
patch
obsolete
>[32;01m * [39;49;00mPackage: app-arch/pax-3.4.12.16 >[32;01m * [39;49;00mRepository: gentoo >[32;01m * [39;49;00mMaintainer: maintainer-needed@gentoo.org >[32;01m * [39;49;00mUSE: abi_x86_64 amd64 elibc_glibc kernel_linux multilib userland_GNU >[32;01m * [39;49;00mFEATURES: preserve-libs sandbox splitdebug >>>> Unpacking source... >>>> Unpacking pax-3.4-12.fc16.src.rpm to /var/tmp/portage/app-arch/pax-3.4.12.16/work >>>> Unpacking ./pax-3.4.tar.bz2 to /var/tmp/portage/app-arch/pax-3.4.12.16/work >>>> Source unpacked in /var/tmp/portage/app-arch/pax-3.4.12.16/work >>>> Preparing source in /var/tmp/portage/app-arch/pax-3.4.12.16/work/pax-3.4 ... > [32;01m*[0m Applying patches from ../pax.spec ... > [32;01m*[0m Applying pax-3.0-PATHMAX.patch ... >[A[202C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying pax-3.4-abs100.patch ... >[A[202C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying pax-3.4-rdtruncate.patch ... >[A[202C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying pax-gcc46.patch ... >[A[202C [34;01m[ [32;01mok[34;01m ][0m >[A[202C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Applying pax-3.4-x32.patch ... >[A[202C [34;01m[ [32;01mok[34;01m ][0m > [32;01m*[0m Running eautoreconf in '/var/tmp/portage/app-arch/pax-3.4.12.16/work/pax-3.4' ... > [32;01m*[0m Running aclocal ... >[A[202C [34;01m[ [31;01m!![34;01m ][0m > > [31;01m*[0m Failed Running aclocal ! > [31;01m*[0m > [31;01m*[0m Include in your bugreport the contents of: > [31;01m*[0m > [31;01m*[0m /var/tmp/portage/app-arch/pax-3.4.12.16/temp/aclocal.out > > [31;01m*[0m ERROR: app-arch/pax-3.4.12.16 failed (prepare phase): > [31;01m*[0m Failed Running aclocal ! > [31;01m*[0m > [31;01m*[0m Call stack: > [31;01m*[0m ebuild.sh, line 93: Called src_prepare > [31;01m*[0m environment, line 3172: Called eautoreconf > [31;01m*[0m environment, line 909: Called eaclocal > [31;01m*[0m environment, line 812: Called autotools_run_tool '--at-m4flags' 'aclocal' > [31;01m*[0m environment, line 674: Called die > [31;01m*[0m The specific snippet of code: > [31;01m*[0m die "Failed Running $1 !"; > [31;01m*[0m > [31;01m*[0m If you need support, post the output of `emerge --info '=app-arch/pax-3.4.12.16'`, > [31;01m*[0m the complete build log and the output of `emerge -pqv '=app-arch/pax-3.4.12.16'`. >/var/tmp/portage/._portage_reinstall_.6BORYA/bin/isolated-functions.sh: line 215: wait: `Failed Running aclocal !': not a pid or valid job spec > [31;01m*[0m The complete build log is located at '/var/tmp/portage/app-arch/pax-3.4.12.16/temp/build.log'. > [31;01m*[0m The ebuild environment file is located at '/var/tmp/portage/app-arch/pax-3.4.12.16/temp/environment'. > [31;01m*[0m Working directory: '/var/tmp/portage/app-arch/pax-3.4.12.16/work/pax-3.4' > [31;01m*[0m S: '/var/tmp/portage/app-arch/pax-3.4.12.16/work/pax-3.4'
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 471966
:
349788
| 349790 |
349792