public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: zinosat@tiscali.it
To: insight-gnats@sources.redhat.com
Subject: insight/350: Build failure due to unset RC variable
Date: Sun, 16 May 2010 20:13:00 -0000 [thread overview]
Message-ID: <20100516200459.1829.qmail@sourceware.org> (raw)
>Number: 350
>Category: insight
>Synopsis: Build failure due to unset RC variable
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sun May 16 20:13:02 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator: zinosat@tiscali.it
>Release: unknown-1.0
>Organization:
>Environment:
>Description:
While trying to cross-compile insight on a Debian Lenny i386 host with the mingw32 compiler, compilation fails with the following error:
i586-mingw32msvc-gcc -c -g -O2 -D__USE_MINGW_ACCESS -Wall -Wconversion -I"../../../../insight-6.8-111/\
tcl/win/../generic" -I"../../../../insight-6.8-111/tcl/win" -mwin32 -DPACKAGE_NAME=\"\" -DPACKAGE_TARN\
AME=\"\" -DPACKAGE_VERSION=\"\" -DPACKAGE_STRING=\"\" -DPACKAGE_BUGREPORT=\"\" -DHAVE_NO_SEH=1 -DEXCEPT\
ION_DISPOSITION=int -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_\
STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1\
-DBUILD_tcl ../../../../insight-6.8-111/tcl/win/../compat/strtoull.c -o strtoull.o
o tcl.res.o --include "../../../../insight-6.8-111/tcl/win/../generic" --include "../../../../insight\
-6.8-111/tcl/win" ../../../../insight-6.8-111/tcl/win/tcl.rc
/bin/sh: o: command not found
make[3]: [tcl.res.o] Error 127 (ignored)
>How-To-Repeat:
>Fix:
It turns out that the RC variable in tcl/win/Makefile is not set. Forcing RC to "i586-mingw32msvc-windres" fixes the problem. The very same error occurs on tk/win/Makefile
Tried to gather some debugging traces in the "configure" script:
+ set dummy windres
+ ac_word=windres
+ echo 'configure:2885: checking for windres'
+ echo -n 'checking for windres... '
checking for windres... + test '' = set
+ test -n ''
+ as_save_IFS='
'
+ IFS=:
+ for as_dir in '$PATH'
+ IFS='
'
+ test -z /usr/local/bin
+ for ac_exec_ext in ''\'''\''' '$ac_executable_extensions'
+ test -f /usr/local/bin/windres
+ for as_dir in '$PATH'
+ IFS='
'
+ test -z /usr/bin
+ for ac_exec_ext in ''\'''\''' '$ac_executable_extensions'
+ test -f /usr/bin/windres
+ for as_dir in '$PATH'
+ IFS='
'
+ test -z /bin
+ for ac_exec_ext in ''\'''\''' '$ac_executable_extensions'
+ test -f /bin/windres
+ for as_dir in '$PATH'
+ IFS='
'
+ test -z /usr/games
+ for ac_exec_ext in ''\'''\''' '$ac_executable_extensions'
+ test -f /usr/games/windres
+ IFS='
>Release-Note:
>Audit-Trail:
>Unformatted:
reply other threads:[~2010-05-16 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100516200459.1829.qmail@sourceware.org \
--to=zinosat@tiscali.it \
--cc=insight-gnats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).