Summary: | ncurses-5.4-r6 fails compile - make_keys not found - makefile glitch | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robin Johnson <robbat2> |
Component: | [OLD] Core system | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED NEEDINFO | ||
Severity: | critical | CC: | mgorny |
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robin Johnson
![]() ![]() ![]() ![]() Do you have an environment variable BUILD_EXEEXT=no ? At least setting that reproduces it. BUILD_EXEEXT should be ".exe" for Windows targets, otherwise empty. no, but tracing the config.site stuff I was working on, I do see that it's picked up "ac_cv_exeext=${ac_cv_exeext=no}" from somewhere, and the bug goes away when the 'no' is taken out of that line. anyway, such a bug should still be fixed in the sources. The problem is the upstream provided configure script. The affected macro AC_EXEEXT of Gentoo looks sane to me. We should regenerate configure out of configure.in Was not able to do that, most likely some minor changes in configure.in needed. Or should be updated to autoconf 2.59 level .. both are valid issues ... the Makefile should actually have $(BUILD_EXEEXT) and it shouldnt matter :) does `env -i PATH=/usr/bin emerge ncurses` work ? Responding to comment #2, it sounds as if the configure script's been regenerated using a different version of autoconf (which probably would not work). please post a full build log ... `emerge ncurses >& log` |