public inbox for gentoo-science@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-science] Locating ar
@ 2014-04-29  8:32 Thomas Kahle
  2014-04-29 11:23 ` François Bissey
  2014-04-29 11:36 ` Panagiotis Christopoulos
  0 siblings, 2 replies; 7+ messages in thread
From: Thomas Kahle @ 2014-04-29  8:32 UTC (permalink / raw
  To: gentoo-science


[-- Attachment #1.1: Type: text/plain, Size: 384 bytes --]

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

[-- Attachment #1.2: singular-4.0.0_p2.ebuild --]
[-- Type: text/plain, Size: 4046 bytes --]

# Copyright 1999-2012 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/sci-mathematics/singular/singular-3.1.4-r1.ebuild,v 1.4 2012/06/23 10:50:20 xarthisius Exp $

EAPI=5

inherit autotools eutils elisp-common flag-o-matic multilib prefix versionator

MY_PN=Singular
MY_PV=$(replace_all_version_separators '.')
# Consistency is different...
MY_DIR2=$(get_version_component_range 1-3 ${PV})
MY_DIR=$(replace_all_version_separators '-' ${MY_DIR2})

DESCRIPTION="Computer algebra system for polynomial computations"
HOMEPAGE="http://www.singular.uni-kl.de/"
SRC_URI="http://www.mathematik.uni-kl.de/ftp/pub/Math/${MY_PN}/SOURCES/${MY_DIR}/${PN}-${MY_PV}.tar.gz"

LICENSE="GPL-2"
SLOT="0"
KEYWORDS="~amd64 ~ppc ~x86 ~x86-linux ~x86-macos"
IUSE="boost doc emacs examples python +readline"

RDEPEND="dev-libs/gmp
	>=dev-libs/ntl-5.5.1
	emacs? ( >=virtual/emacs-22 )"

DEPEND="${RDEPEND}
	dev-lang/perl
	boost? ( dev-libs/boost )
	readline? ( sys-libs/readline )"

SITEFILE=60${PN}-gentoo.el

S="${WORKDIR}/${PN}-${MY_DIR2}"

pkg_setup() {
	append-flags "-fPIC"
	append-ldflags "-fPIC"
	tc-export AR CC CPP CXX

	# Ensure that >=emacs-22 is selected
	if use emacs; then
		elisp-need-emacs 22 || die "Emacs version too low"
	fi
}

src_prepare () {
	# Need to do something about resources later...
	# epatch "${FILESDIR}"/${PN}-4.0.0-gentoo.patch

	# cd "${S}"/Singular || die "failed to cd into Singular/"
	eautoreconf
}

src_configure() {
	econf \
#		--prefix="${S}"/build \
#		--exec-prefix="${S}"/build \
#		--bindir="${S}"/build/bin \
#		--libdir="${S}"/build/lib \
#		--libexecdir="${S}"/build/lib \
#		--includedir="${S}"/build/include \
		--with-gmp="${EPREFIX}"/usr \
		--with-ntl \
		--disable-debug \
		--disable-doc \
		--enable-factory \
		--enable-libfac \
		--enable-IntegerProgramming \
#		--enable-Singular \
		$(use_with python python embed) \
		$(use_with boost Boost) \
		$(use_enable emacs) \
		$(use_with readline) || die "configure failed"
}

src_compile() {
	emake || die "emake failed"

	if use emacs; then
		cd "${WORKDIR}"/${MY_PN}/${MY_SHARE_DIR}/emacs/
		elisp-compile *.el || die "elisp-compile failed"
	fi
}

src_test() {
	emake test || die "tests failed"
}

# src_install () {
# 	dodoc README
# 	# execs and libraries
# 	cd "${S}"/build/bin
# 	dobin ${MY_PN}* gen_test change_cost solve_IP toric_ideal LLL \
# 		|| die "failed to install binaries"
# 	insinto /usr/$(get_libdir)/${PN}
# 	doins *.so || die "failed to install libraries"
#
# 	dosym ${MY_PN}-${MY_DIR} /usr/bin/${MY_PN} \
# 		|| die "failed to create symbolic link"
#
# 	# stuff from the share tar ball
# 	cd "${WORKDIR}"/${MY_PN}/${MY_SHARE_DIR}
# 	insinto /usr/share/${PN}
# 	doins -r LIB  || die "failed to install lib files"
# 	if use examples; then
# 		insinto /usr/share/doc/${PF}
# 		doins -r examples || die "failed to install examples"
# 	fi
# 	if use doc; then
# 		dohtml -r html/* || die "failed to install html docs"
# 		insinto /usr/share/${PN}
# 		doins doc/singular.idx || die "failed to install idx file"
# 		cp info/${PN}.hlp info/${PN}.info &&
# 		doinfo info/${PN}.info \
# 			|| die "failed to install info files"
# 	fi
# 	if use emacs; then
# 		elisp-install ${PN} emacs/*.el emacs/*.elc emacs/.emacs* \
# 			|| die "elisp-install failed"
# 		elisp-site-file-install "${FILESDIR}/${SITEFILE}"
# 	fi
# }

pkg_postinst() {
	einfo "The authors ask you to register as a SINGULAR user."
	einfo "Please check the license file for details."

	if use emacs; then
		echo
		ewarn "Please note that the ESingular emacs wrapper has been"
		ewarn "removed in favor of full fledged singular support within"
		ewarn "Gentoo's emacs infrastructure; i.e. just fire up emacs"
		ewarn "and you should be good to go! See bug #193411 for more info."
		echo
	fi

	use emacs && elisp-site-regen
}

pkg_postrm() {
	use emacs && elisp-site-regen
}

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-science] Locating ar
  2014-04-29  8:32 [gentoo-science] Locating ar Thomas Kahle
@ 2014-04-29 11:23 ` François Bissey
  2014-04-29 11:33   ` Thomas Kahle
  2014-04-29 11:36 ` Panagiotis Christopoulos
  1 sibling, 1 reply; 7+ messages in thread
From: François Bissey @ 2014-04-29 11:23 UTC (permalink / raw
  To: gentoo-science

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 <tomka@gentoo.org> 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>



^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-science] Locating ar
  2014-04-29 11:23 ` François Bissey
@ 2014-04-29 11:33   ` Thomas Kahle
  0 siblings, 0 replies; 7+ messages in thread
From: Thomas Kahle @ 2014-04-29 11:33 UTC (permalink / raw
  To: gentoo-science

[-- Attachment #1: Type: text/plain, Size: 11573 bytes --]

Err, ja.  This eautoreconf should be an eautoconf, I guess.

On 29.04.2014 13:23, François Bissey wrote:
> 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 <tomka@gentoo.org> 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>
> 
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-science] Locating ar
  2014-04-29  8:32 [gentoo-science] Locating ar Thomas Kahle
  2014-04-29 11:23 ` François Bissey
@ 2014-04-29 11:36 ` Panagiotis Christopoulos
  2014-04-29 11:44   ` Panagiotis Christopoulos
  1 sibling, 1 reply; 7+ messages in thread
From: Panagiotis Christopoulos @ 2014-04-29 11:36 UTC (permalink / raw
  To: gentoo-science

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

On Tue, Apr 29, 2014 at 11:32 AM, Thomas Kahle <tomka@gentoo.org> wrote:

> Hi,
>

Hi Thomas,


>
> 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?
>

if you open the original sources (without eautoreconf), and go inside
omalloc folder, you'll find the cause in line 120 of configure.ac and/or
12977 of configure. It's hardcoded there that the script should fail if
$ac_cv_prog_AR is not "ar". Here, portage already passes (even without your
tc-exports etc.) the correct environment to singular's build system but
"x86_64-pc-linux-gnu-ar" is not "ar". You could remove that check at all
but I'm not a toolchain expert and don't know why the check is there in
first place. On my box ar just links to x86_64-pc-linux-gnu-ar so no big
deal.


Panagiotis (pchrist)

[-- Attachment #2: Type: text/html, Size: 1718 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-science] Locating ar
  2014-04-29 11:36 ` Panagiotis Christopoulos
@ 2014-04-29 11:44   ` Panagiotis Christopoulos
  2014-04-29 11:48     ` Thomas Kahle
  0 siblings, 1 reply; 7+ messages in thread
From: Panagiotis Christopoulos @ 2014-04-29 11:44 UTC (permalink / raw
  To: gentoo-science

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

On Tue, Apr 29, 2014 at 2:36 PM, Panagiotis Christopoulos
<pxrist@gmail.com>wrote:

> ...
>
> if you open the original sources (without eautoreconf), and go inside
> omalloc folder, you'll find the cause in line 120 of configure.ac and/or
> 12977 of configure. It's hardcoded there that the script should fail if
> $ac_cv_prog_AR is not "ar". Here, portage already passes (even without your
> tc-exports etc.) the correct environment to singular's build system but
> "x86_64-pc-linux-gnu-ar" is not "ar". You could remove that check at all
> but I'm not a toolchain expert and don't know why the check is there in
> first place. On my box ar just links to x86_64-pc-linux-gnu-ar so no big
> deal.
>

of course , name changes may affect program behariour ($0) so ar might have
different results if you invoke it as "ar" than "x86_64-pc-linux-gnu-ar".
I would remove or replace the configure check and would do some testing to
see what happens. Was omalloc and that test included on previous versions
too?

[-- Attachment #2: Type: text/html, Size: 1584 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-science] Locating ar
  2014-04-29 11:44   ` Panagiotis Christopoulos
@ 2014-04-29 11:48     ` Thomas Kahle
  2014-04-29 17:13       ` Panagiotis Christopoulos
  0 siblings, 1 reply; 7+ messages in thread
From: Thomas Kahle @ 2014-04-29 11:48 UTC (permalink / raw
  To: gentoo-science

[-- Attachment #1: Type: text/plain, Size: 1640 bytes --]

On 29.04.2014 13:44, Panagiotis Christopoulos wrote:
> On Tue, Apr 29, 2014 at 2:36 PM, Panagiotis Christopoulos
> <pxrist@gmail.com <mailto:pxrist@gmail.com>> wrote:
> 
>     ...
> 
>     if you open the original sources (without eautoreconf), and go
>     inside omalloc folder, you'll find the cause in line 120 of
>     configure.ac <http://configure.ac> and/or 12977 of configure. It's
>     hardcoded there that the script should fail if $ac_cv_prog_AR is not
>     "ar". Here, portage already passes (even without your tc-exports
>     etc.) the correct environment to singular's build system but
>     "x86_64-pc-linux-gnu-ar" is not "ar". You could remove that check at
>     all but I'm not a toolchain expert and don't know why the check is
>     there in first place. On my box ar just links to
>     x86_64-pc-linux-gnu-ar so no big deal.
> 
> 
> of course , name changes may affect program behariour ($0) so ar might
> have different results if you invoke it as "ar" than
> "x86_64-pc-linux-gnu-ar".  I would remove or replace the configure check
> and would do some testing to see what happens. Was omalloc and that test
> included on previous versions too?

OK, thanks for coming up with this.  We did not use omalloc
before, but I thought maybe we should because Singular upstream
told me that using system malloc is bad (I don't remember if it
was just performance or also other problems).

The omalloc build system seems to be old, so maybe it was back in
the old days that some other ar on some esoteric platform failed
on them and it was band-aided with this check?

Cheers,
Thomas


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 555 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [gentoo-science] Locating ar
  2014-04-29 11:48     ` Thomas Kahle
@ 2014-04-29 17:13       ` Panagiotis Christopoulos
  0 siblings, 0 replies; 7+ messages in thread
From: Panagiotis Christopoulos @ 2014-04-29 17:13 UTC (permalink / raw
  To: gentoo-science

[-- Attachment #1: Type: text/plain, Size: 386 bytes --]

On Tue, Apr 29, 2014 at 2:48 PM, Thomas Kahle <tomka@gentoo.org> wrote:

> The omalloc build system seems to be old, so maybe it was back in
> the old days that some other ar on some esoteric platform failed
> on them and it was band-aided with this check?
>

If you talk to them, you could ask them for the check, it's there since
1999, I suppose there is no good reason now for this.

[-- Attachment #2: Type: text/html, Size: 708 bytes --]

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2014-04-29 17:13 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-04-29  8:32 [gentoo-science] Locating ar Thomas Kahle
2014-04-29 11:23 ` François Bissey
2014-04-29 11:33   ` Thomas Kahle
2014-04-29 11:36 ` Panagiotis Christopoulos
2014-04-29 11:44   ` Panagiotis Christopoulos
2014-04-29 11:48     ` Thomas Kahle
2014-04-29 17:13       ` Panagiotis Christopoulos

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox