public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Uberbaum tree broken for m68k-elf
@ 2003-01-28  3:29 Peter Barada
  2003-01-28 19:52 ` Graham Stott
  0 siblings, 1 reply; 3+ messages in thread
From: Peter Barada @ 2003-01-28  3:29 UTC (permalink / raw)
  To: gcc


For about the last week, the uberbaum tree has failed to build from
scratch when configured with --target=m68k-elf

The bukld fails int the tix/unix directory looking for a tk8.4 subdir
that isn't there.

make[1]: Entering directory `/home/peter/work/cvs-gnu/obj/tix'
make[2]: Entering directory `/home/peter/work/cvs-gnu/obj/tix/unix'
/bin/sh: cd: tk8.4: No such file or directory
make[2]: *** [all] Error 1
make[2]: Leaving directory `/home/peter/work/cvs-gnu/obj/tix/unix'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/peter/work/cvs-gnu/obj/tix'
make: *** [all-tix] Error 2

Appearently configure is coming up with a TCL_VERSION of 8.4:

[peter@baradas obj]$ grep -r TCL_VERSION t*
./tcl/unix/config.status:s%@TCL_VERSION@%8.4%g
./tcl/unix/dltest/Makefile:TCL_VERSION=		8.4
./tcl/unix/tclConfig.sh:TCL_VERSION='8.4'
./tk/unix/config.status:s%@TCL_VERSION@%8.4%g

Has anyone else had any luck building the uberbaum tree on RH7.3?

-- 
Peter Barada
peter@baradas.org

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Uberbaum tree broken for m68k-elf
  2003-01-28  3:29 Uberbaum tree broken for m68k-elf Peter Barada
@ 2003-01-28 19:52 ` Graham Stott
  2003-01-29  8:06   ` Christopher Faylor
  0 siblings, 1 reply; 3+ messages in thread
From: Graham Stott @ 2003-01-28 19:52 UTC (permalink / raw)
  To: Peter Barada; +Cc: gcc

Peter,

Peter Barada wrote:
> For about the last week, the uberbaum tree has failed to build from
> scratch when configured with --target=m68k-elf
> 
> The bukld fails int the tix/unix directory looking for a tk8.4 subdir
> that isn't there.
> 
[snip]
> Has anyone else had any luck building the uberbaum tree on RH7.3?
> 

I got the same problem which isn't m68k-elf specific it occurs for all
uberbaum toolchains.

I've hacked it locally by cloning the tix/unix/tk8.3 directory into a
new tix/unix/tk8.4 directory. I then modified tk8.4/Makefile.in and
changed a $(TCL_BIN_DIR)/tclsh8.3 reference into $(TCL_BIN_DIR)/tclsh8.4

This allowed me to build a complete toolchain but I haven't tried installing
or running the testsuites.

Cheers
Graham

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Uberbaum tree broken for m68k-elf
  2003-01-28 19:52 ` Graham Stott
@ 2003-01-29  8:06   ` Christopher Faylor
  0 siblings, 0 replies; 3+ messages in thread
From: Christopher Faylor @ 2003-01-29  8:06 UTC (permalink / raw)
  To: Graham Stott; +Cc: Peter Barada, gcc

On Tue, Jan 28, 2003 at 06:47:05PM +0000, Graham Stott wrote:
>Peter,
>
>Peter Barada wrote:
>>For about the last week, the uberbaum tree has failed to build from
>>scratch when configured with --target=m68k-elf
>>
>>The bukld fails int the tix/unix directory looking for a tk8.4 subdir
>>that isn't there.
>>
>[snip]
>>Has anyone else had any luck building the uberbaum tree on RH7.3?
>>
>
>I got the same problem which isn't m68k-elf specific it occurs for all
>uberbaum toolchains.
>
>I've hacked it locally by cloning the tix/unix/tk8.3 directory into a
>new tix/unix/tk8.4 directory. I then modified tk8.4/Makefile.in and
>changed a $(TCL_BIN_DIR)/tclsh8.3 reference into $(TCL_BIN_DIR)/tclsh8.4
>
>This allowed me to build a complete toolchain but I haven't tried installing
>or running the testsuites.

Actually, the right solution is to just delete the tix directory.  It is no
longer required for gdb and no longer builds with tcl8.4.  It should probably
be cvs removed.

cgf

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2003-01-29  4:09 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-01-28  3:29 Uberbaum tree broken for m68k-elf Peter Barada
2003-01-28 19:52 ` Graham Stott
2003-01-29  8:06   ` Christopher Faylor

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