On Tue, Apr 29, 2014 at 11:32 AM, Thomas Kahle <[email protected]> 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)
