tcl cannot build 64bit.

tcl cannot build 64bit.

[Manoj Iyer]

When I build GDB 6.1 CVS version as a 64bit binary, the tclsh fails to
build. The linker complains "skipping incompatible
/home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a when searching
for -ltcl8.4" even though libtcl8.4.a is availale in that directory.

When I force it to link with the archive I get a bunch of  undefined
reference to ".symbol" as follows: ( I am only pasting a few). And they
look like glibc symbols...

/home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a(tclIOGT.o)(.text+0x1b18):
In function `.ResultAdd':
: undefined reference to `.memcpy'
/home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a(tclResolve.o)(.text+0xb8):
In function `.Tcl_AddInterpResolvers':
: undefined reference to `.strcmp'
/home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a(tclResolve.o)(.text+0x11c):
In function `.Tcl_AddInterpResolvers':
: undefined reference to `.strlen'
/home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a(tclResolve.o)(.text+0x150):
In function `.Tcl_AddInterpResolvers':
: undefined reference to `.strcpy'
/home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a(tclResolve.o)(.text+0x230):
In function `.Tcl_GetInterpResolvers':
: undefined reference to `.strcmp'
/home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a(tclResolve.o)(.text+0x338):
In function `.Tcl_RemoveInterpResolvers':
: undefined reference to `.strcmp'
collect2: ld returned 1 exit status

Any suggestions??

--
Manoj

Re: tcl cannot build 64bit.

[Andrew Cagney]

> When I build GDB 6.1 CVS version as a 64bit binary, the tclsh fails to
> build. The linker complains "skipping incompatible
> /home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a when searching
> for -ltcl8.4" even though libtcl8.4.a is availale in that directory.
> 
> When I force it to link with the archive I get a bunch of  undefined
> reference to ".symbol" as follows: ( I am only pasting a few). And they
> look like glibc symbols...

GDB or expect?  GDB doesn't need tcl.  The expect in the repository is 
sufficiently out-of-date to be getting dangerous :-(  I'd just use "make 
all-gdb".

Andrew

Re: tcl cannot build 64bit.

[Manoj Iyer]

That is something I wondred... why build expect in the same package as
gdb??

--
Manoj


On Tue, 9 Mar 2004, Andrew Cagney wrote:

> > When I build GDB 6.1 CVS version as a 64bit binary, the tclsh fails to
> > build. The linker complains "skipping incompatible
> > /home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a when searching
> > for -ltcl8.4" even though libtcl8.4.a is availale in that directory.
> >
> > When I force it to link with the archive I get a bunch of  undefined
> > reference to ".symbol" as follows: ( I am only pasting a few). And they
> > look like glibc symbols...
>
> GDB or expect?  GDB doesn't need tcl.  The expect in the repository is
> sufficiently out-of-date to be getting dangerous :-(  I'd just use "make
> all-gdb".
>
> Andrew
>
>
>

Re: tcl cannot build 64bit.

[Andreas Schwab]

Manoj Iyer <manjo@austin.ibm.com> writes:

> That is something I wondred... why build expect in the same package as
> gdb??

It's used by dejagnu.

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."

Re: tcl cannot build 64bit.

[Andreas Schwab]

Andrew Cagney <cagney@gnu.org> writes:

>> When I build GDB 6.1 CVS version as a 64bit binary, the tclsh fails to
>> build. The linker complains "skipping incompatible
>> /home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a when searching
>> for -ltcl8.4" even though libtcl8.4.a is availale in that directory.
>> When I force it to link with the archive I get a bunch of  undefined
>> reference to ".symbol" as follows: ( I am only pasting a few). And they
>> look like glibc symbols...
>
> GDB or expect?  GDB doesn't need tcl.

Actually it does, unless you configure with --disable-gdbtk.

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."

Re: tcl cannot build 64bit.

[Andrew Cagney]

> Andrew Cagney <cagney@gnu.org> writes:
> 
> 
>>>>> When I build GDB 6.1 CVS version as a 64bit binary, the tclsh fails to
>>>>> build. The linker complains "skipping incompatible
>>>>> /home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a when searching
>>>>> for -ltcl8.4" even though libtcl8.4.a is availale in that directory.
>>>>> When I force it to link with the archive I get a bunch of  undefined
>>>>> reference to ".symbol" as follows: ( I am only pasting a few). And they
>>>>> look like glibc symbols...
>>
>>>
>>> GDB or expect?  GDB doesn't need tcl.
> 
> 
> Actually it does, unless you configure with --disable-gdbtk.

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 ignore me using ccache :-) you probably checked out the non FSF 
insight :-(

Andrew

Re: tcl cannot build 64bit.

[Andreas Schwab]

Andrew Cagney <cagney@gnu.org> writes:

>> Andrew Cagney <cagney@gnu.org> writes:
>> 
>>>>>> When I build GDB 6.1 CVS version as a 64bit binary, the tclsh fails to
>>>>>> build. The linker complains "skipping incompatible
>>>>>> /home/manjo/project/build_scripts/src/tcl/unix/libtcl8.4.a when searching
>>>>>> for -ltcl8.4" even though libtcl8.4.a is availale in that directory.
>>>>>> When I force it to link with the archive I get a bunch of  undefined
>>>>>> reference to ".symbol" as follows: ( I am only pasting a few). And they
>>>>>> look like glibc symbols...
>>>
>>>>
>>>> GDB or expect?  GDB doesn't need tcl.
>> Actually it does, unless you configure with --disable-gdbtk.
>
> 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.

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."

Re: tcl cannot build 64bit.

[Andrew Cagney]

>>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

Re: tcl cannot build 64bit.

[Manoj Iyer]

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
>
>
>

Re: tcl cannot build 64bit.

[Andreas Schwab]

Manoj Iyer <manjo@austin.ibm.com> writes:

> since I am building using CFLAGS="$CFLAGS -m64", the -m64 is not passed to

You should use CC="$CC -m64" instead.

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."

Re: tcl cannot build 64bit.

[Andreas Schwab]

Andrew Cagney <cagney@gnu.org> writes:

>>>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.

It's still there, with plenty of contents, including all branches.  If
it's not needed it should be removed from CVS.

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."

Re: tcl cannot build 64bit.

[Ian Lance Taylor]

Andreas Schwab <schwab@suse.de> writes:

> Andrew Cagney <cagney@gnu.org> writes:
> 
> >>>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.
> 
> It's still there, with plenty of contents, including all branches.  If
> it's not needed it should be removed from CVS.

The src directory is used for a number of different packages, not just
gdb.

If you 'cvs co gdb' and then avoid using 'cvs update -d' at top level,
you should be OK.

Ian

Re: tcl cannot build 64bit.

[Andreas Schwab]

Ian Lance Taylor <ian@wasabisystems.com> writes:

> The src directory is used for a number of different packages, not just
> gdb.

Yes, I know.

> If you 'cvs co gdb' and then avoid using 'cvs update -d' at top level,
> you should be OK.

Not using -d is not an option.  And the gdbtk directory even exists on the
branch.

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."

Re: tcl cannot build 64bit.

[Daniel Jacobowitz]

On Wed, Mar 10, 2004 at 05:02:22PM +0100, Andreas Schwab wrote:
> Ian Lance Taylor <ian@wasabisystems.com> writes:
> 
> > The src directory is used for a number of different packages, not just
> > gdb.
> 
> Yes, I know.
> 
> > If you 'cvs co gdb' and then avoid using 'cvs update -d' at top level,
> > you should be OK.
> 
> Not using -d is not an option.  And the gdbtk directory even exists on the
> branch.

If you don't want to end up building Insight, update by using "checkout
gdb".  Unfortunately, --disable-gdbtk doesn't fix the top level from
deciding gdb depends on tcl; that could be fixed in configure...

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer

Re: tcl cannot build 64bit.

[Manoj Iyer]

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.

Thanks
--
Manoj
On Wed, 10 Mar 2004, Daniel Jacobowitz wrote:

> On Wed, Mar 10, 2004 at 05:02:22PM +0100, Andreas Schwab wrote:
> > Ian Lance Taylor <ian@wasabisystems.com> writes:
> >
> > > The src directory is used for a number of different packages, not just
> > > gdb.
> >
> > Yes, I know.
> >
> > > If you 'cvs co gdb' and then avoid using 'cvs update -d' at top level,
> > > you should be OK.
> >
> > Not using -d is not an option.  And the gdbtk directory even exists on the
> > branch.
>
> If you don't want to end up building Insight, update by using "checkout
> gdb".  Unfortunately, --disable-gdbtk doesn't fix the top level from
> deciding gdb depends on tcl; that could be fixed in configure...
>
> --
> Daniel Jacobowitz
> MontaVista Software                         Debian GNU/Linux Developer
>

Re: tcl cannot build 64bit.

[Andreas Schwab]

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."

Re: tcl cannot build 64bit.

[Ian Lance Taylor]

Andreas Schwab <schwab@suse.de> 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.

The GNU standards require that CFLAGS be used in every command which
uses CC, including ones which simply link.

Of course, Tcl is not a GNU program.

Ian

Re: tcl cannot build 64bit.

[Manoj Iyer]

> > 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.


I am a little confused, I thought -m64 is a compiler option. Specifying
it along with LDFLAGS might fix this problem, but is that the correct?

--
Manoj Iyer

Re: tcl cannot build 64bit.

[Andrew Cagney]

> just use
> CC="$CC -m64" since it's actually a different compiler after all.

Yes, definitly.

Andrew