From: Manoj Iyer <manjo@austin.ibm.com>
To: Andrew Cagney <cagney@gnu.org>
Cc: Andreas Schwab <schwab@suse.de>, gdb@sources.redhat.com
Subject: Re: tcl cannot build 64bit.
Date: Wed, 10 Mar 2004 05:46:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.58.0403100604500.11150@lazy> (raw)
In-Reply-To: <404E70B2.4010607@gnu.org>
Andrew,
Well the problem is in the Makefile.in file in the tcl/unix directory.
tclsh: ${TCLSH_OBJS} ${TCL_LIB_FILE}
${CC} ${LDFLAGS} ${TCLSH_OBJS} @TCL_BUILD_LIB_SPEC@ ${LIBS} \
${CC_SEARCH_FLAGS} -o tclsh
add ${CFLAGS} to the above fixes the unresolved symbols problem, and tclsh
builds like a charm :-) so the code should look like this...
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
since I am building using CFLAGS="$CFLAGS -m64", the -m64 is not passed to
this step, and the linker tries to link 32bit & 64bit binaries to gether
and the build fails.
Sorry I dont have a FSF approval currently to submit this as a patch. But
I will be getting one sometime this month. I can send you the patch then
or you can patch this for me :-)
Thanks
Manoj Iyer
On Tue, 9 Mar 2004, Andrew Cagney wrote:
> >>Er, no, here's my link line:
> >>>
> >>> /usr/pkg/bin/ccache gcc -g -O -o gdbtui tui-main.o libgdb.a
> >>> ../sim/ppc/libsim.a ../bfd/libbfd.a ../readline/libreadline.a
> >>> ../opcodes/libopcodes.a ./../intl/libintl.a ../libiberty/libiberty.a -lm
> >>> -lcurses ../libiberty/libiberty.a
> >
> >
> > Ok, it's not gdb itself, but there is the gdbtk subdirectory.
>
> Sounds like you did the dreaded `cvs update -d`. Just remove the
> directory, it isn't needed.
>
> Andrew
>
>
>
next prev parent reply other threads:[~2004-03-10 5:46 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 [this message]
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
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=Pine.LNX.4.58.0403100604500.11150@lazy \
--to=manjo@austin.ibm.com \
--cc=cagney@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=schwab@suse.de \
/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