From: Andreas Schwab <schwab@suse.de>
To: Manoj Iyer <manjo@austin.ibm.com>
Cc: Daniel Jacobowitz <drow@false.org>,
Ian Lance Taylor <ian@wasabisystems.com>,
Andrew Cagney <cagney@gnu.org>,
gdb@sources.redhat.com
Subject: Re: tcl cannot build 64bit.
Date: Wed, 10 Mar 2004 17:22:00 -0000 [thread overview]
Message-ID: <jellm8sjl1.fsf@sykes.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0403101636530.15162@lazy> (Manoj Iyer's message of "Wed, 10 Mar 2004 16:40:39 +0100 (CET)")
Manoj Iyer <manjo@austin.ibm.com> writes:
> I think I emailed the fix to the problem wrt to building tcl 64bit. All
> it requires is a one line fix in Makefile.in.
>
> src/tcl/unix/Makefile.in:479
>
> tclsh: ${TCLSH_OBJS} ${TCL_LIB_FILE}
> ${CC} ${CFLAGS} ${LDFLAGS} ${TCLSH_OBJS} @TCL_BUILD_LIB_SPEC@
> ${LIBS} ${CC_SEARCH_FLAGS} -o tclsh
>
>
> It is missing the ${CFLAGS} in the cc line.
It shouldn't be needed, since it's a link command, not a compile command.
If you need -m64 for linking you must add it to LDFLAGS. Or just use
CC="$CC -m64" since it's actually a different compiler after all.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2004-03-10 17:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-09 21:10 Manoj Iyer
2004-03-09 21:20 ` Andrew Cagney
2004-03-09 21:34 ` Manoj Iyer
2004-03-09 22:03 ` Andreas Schwab
2004-03-09 22:05 ` Andreas Schwab
2004-03-09 22:27 ` Andrew Cagney
2004-03-09 22:55 ` Andreas Schwab
2004-03-10 1:34 ` Andrew Cagney
2004-03-10 5:46 ` Manoj Iyer
2004-03-10 9:13 ` Andreas Schwab
2004-03-10 9:12 ` Andreas Schwab
2004-03-10 15:25 ` Ian Lance Taylor
2004-03-10 16:02 ` Andreas Schwab
2004-03-10 16:05 ` Daniel Jacobowitz
2004-03-10 16:11 ` Manoj Iyer
2004-03-10 17:22 ` Andreas Schwab [this message]
2004-03-10 17:30 ` Ian Lance Taylor
2004-03-12 22:26 ` Manoj Iyer
2004-03-16 23:50 ` Andrew Cagney
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=jellm8sjl1.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=ian@wasabisystems.com \
--cc=manjo@austin.ibm.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