This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
build/2041: gdb 6.3 - readline's 'configure' fails if cross-compiling
- From: naren at ccpu dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 1 Dec 2005 22:47:52 -0000
- Subject: build/2041: gdb 6.3 - readline's 'configure' fails if cross-compiling
- Reply-to: naren at ccpu dot com
>Number: 2041
>Category: build
>Synopsis: gdb 6.3 - readline's 'configure' fails if cross-compiling
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Thu Dec 01 22:48:01 GMT 2005
>Closed-Date:
>Last-Modified:
>Originator: naren@ccpu.com
>Release: 6.3
>Organization:
>Environment:
host=target=mips-linux, build=i386-linux
>Description:
Hi,
I am trying to build a gdb 6.3 that can run on a mips-linux target; using crosscompile toolchain on x86.
'configure' fails in readline subdirectory; with this output:
checking for mbsrtowcs... yes
checking for wcwidth... yes
checking for mbstate_t... configure: error: cannot run test program while cross compiling
See `config.log' for more details.
make: *** [configure-readline] Error 1
In readline/configure I found this gem:
echo "$as_me:$LINENO: checking for mbstate_t" >&5
echo $ECHO_N "checking for mbstate_t... $ECHO_C" >&6
if test "${bash_cv_have_mbstate_t+set}" = set; then
echo $ECHO_N "(cached) $ECHO_C" >&6
else
if test "$cross_compiling" = yes; then
{ { echo "$as_me:$LINENO: error: cannot run test program while cross compiling
See \`config.log' for more details." >&5
echo "$as_me: error: cannot run test program while cross compiling
See \`config.log' for more details." >&2;}
{ (exit 1); exit 1; }; }
else
cat >conftest.$ac_ext <<_ACEOF
#line $LINENO "configure"
/* confdefs.h. */
_ACEOF
....
Does this mean that readline is never meant to be cross-compiled? In other places, cross-compiling lets you off with a warning only.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: