Hi Thomas,
I can’t even go past src_prepare. I have the mother of all failures multiple
autoreconfs…
* Running eautoreconf in
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0' ...
* Running libtoolize --install --copy --force --automake ...
* Running eautoreconf in
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/omalloc'
...
* Running eautoreconf in
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/gfanlib'
...
* Running eautoreconf in
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/resources'
...
* Running eautoreconf in
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/factory'
...
* Running eautoreconf in
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/libpolys'
... [ ok ]
* Running aclocal -I m4 ...
* Running libtoolize --install --copy --force --automake ...
* Running libtoolize --install --copy --force --automake ...
* Running libtoolize --install --copy --force --automake ...
* Running libtoolize --install --copy --force --automake ...
* Running libtoolize --install --copy --force --automake ...
[ ok ]
* Running aclocal -I ../m4 ...
[ ok ]
* Running aclocal -I ../m4 ...
[ ok ]
* Running aclocal -I ../m4 ...
[ ok ]
* Running aclocal -I ../m4 ...
[ ok ]
* Running aclocal -I ../m4 ...
[ ok ]
* Running autoconf ...
* Running autoconf ...
* Running autoconf ...
* Running autoconf ...
[ ok ]
* Running autoheader ...
[ ok ]
* Running autoheader ...
[ !! ]
* Failed Running autoconf !
*
* Include in your bugreport the contents of:
*
* /scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/autoconf-2.out
* ERROR: sci-mathematics/singular-4.0.0_p2::BlueFern failed (prepare phase):
* Failed Running autoconf !
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 3450: Called eautoreconf
* environment, line 1010: Called eautoconf
* environment, line 917: Called autotools_run_tool '--at-m4flags'
'autoconf'
* environment, line 749: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
*
* If you need support, post the output of `emerge --info
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`,
* the complete build log and the output of `emerge -pqv
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 195: wait: `Failed Running
autoconf !': not a pid or valid job spec
* The complete build log is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/build.log'.
* The ebuild environment file is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/environment'.
[ ok ]
* Working directory:
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0'
* S: '/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0'
[ ok ]
* Running autoheader ...
* Running automake --add-missing --copy --foreign --force-missing ...
* Running automake --add-missing --copy --foreign --force-missing ...
[ ok ]
* Running automake --add-missing --copy --foreign --force-missing ...
* Running autoconf ...
* Running autoconf ...
[ !! ]
* Failed Running automake !
*
* Include in your bugreport the contents of:
*
* /scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/automake-2.out
* ERROR: sci-mathematics/singular-4.0.0_p2::BlueFern failed (prepare phase):
* Failed Running automake !
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 3450: Called eautoreconf
* environment, line 981: Called multijob_child_init 'eautoreconf'
* environment, line 2805: Called eautoreconf
* environment, line 1012: Called eautomake
* environment, line 961: Called autotools_run_tool 'automake'
'--add-missing' '--copy' '--foreign' '--force-missing'
* environment, line 749: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
*
[ !! ]
* If you need support, post the output of `emerge --info
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`,
* Failed Running automake !
* the complete build log and the output of `emerge -pqv
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`.
*
/usr/lib64/portage/bin/isolated-functions.sh: line 195: wait: `Failed Running
automake !': not a pid or valid job spec
* The complete build log is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/build.log'.
* Include in your bugreport the contents of:
* The ebuild environment file is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/environment'.
*
* /scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/automake-3.out
* Working directory:
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/gfanlib'
* S: '/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0'
* ERROR: sci-mathematics/singular-4.0.0_p2::BlueFern failed (prepare phase):
* Failed Running automake !
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 3450: Called eautoreconf
* environment, line 981: Called multijob_child_init 'eautoreconf'
* environment, line 2805: Called eautoreconf
* environment, line 1012: Called eautomake
* environment, line 961: Called autotools_run_tool 'automake'
'--add-missing' '--copy' '--foreign' '--force-missing'
* environment, line 749: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
*
* If you need support, post the output of `emerge --info
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`,
* the complete build log and the output of `emerge -pqv
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 195: wait: `Failed Running
automake !': not a pid or valid job spec
* The complete build log is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/build.log'.
* The ebuild environment file is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/environment'.
* Working directory:
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/resources'
* S: '/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0'
/usr/lib64/portage/bin/isolated-functions.sh: line 226: kill: (23048) - No such
process
/usr/lib64/portage/bin/isolated-functions.sh: line 226: kill: (23048) - No such
process
[ ok ]
* Running autoheader ...
[ ok ]
* Running autoheader ...
[ ok ]
* Running automake --add-missing --copy --foreign --force-missing ...
* Running automake --add-missing --copy --foreign --force-missing ...
[ !! ]
* Failed Running automake !
*
* Include in your bugreport the contents of:
*
* /scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/automake-8.out
* ERROR: sci-mathematics/singular-4.0.0_p2::BlueFern failed (prepare phase):
* Failed Running automake !
*
* Call stack:
* ebuild.sh, line 93: Called src_prepare
* environment, line 3450: Called eautoreconf
* environment, line 981: Called multijob_child_init 'eautoreconf'
* environment, line 2805: Called eautoreconf
* environment, line 1012: Called eautomake
* environment, line 961: Called autotools_run_tool 'automake'
'--add-missing' '--copy' '--foreign' '--force-missing'
* environment, line 749: Called die
* The specific snippet of code:
* die "Failed Running $1 !";
*
* If you need support, post the output of `emerge --info
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`,
* the complete build log and the output of `emerge -pqv
'=sci-mathematics/singular-4.0.0_p2::BlueFern'`.
/usr/lib64/portage/bin/isolated-functions.sh: line 195: wait: `Failed Running
automake !': not a pid or valid job spec
* The complete build log is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/build.log'.
* The ebuild environment file is located at
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/temp/environment'.
* Working directory:
'/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0/libpolys'
* S: '/scratch/portage/sci-mathematics/singular-4.0.0_p2/work/singular-4.0.0’
Want the various logs?
François
On 29/04/2014, at 20:32, Thomas Kahle <[email protected]> wrote:
> Hi,
>
> I'm constantly failing at a rewrite of the ebuild for
> sci-math/singular to bump it to 4.0.0. (Current version
> attached). Singular has its own malloc implementation called
> omalloc. The configure script there can't find ar if run from
> within portage context. It does find it when run on a normal
> shell. I tried tc-export AR to no avail. Any ideas?
>
> Cheers,
> Thomas
> <singular-4.0.0_p2.ebuild>
