This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: [PATCH] Problem compiling host tools with different TCLversion
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: epilog at netvisao dot pt
- Cc: ecos-discuss at sources dot redhat dot com
- Date: Tue, 25 Feb 2003 05:34:30 +0000
- Subject: Re: [ECOS] [PATCH] Problem compiling host tools with different TCLversion
- References: <200302240646.46866.epilog@netvisao.pt>
Epilog wrote:
Hi I'm running debian and I have different dirs for tcl development files
/usr/include/tcl8.4
/usr/lib/tcl8.4
for 8.4 tcl and
/usr/include/tcl8.3
/usr/lib/tcl8.3
for 8.3 tcl
So here's a quick patch, maybe it could be in cvs or a better way could be
implemented. It took me a lot of time until I found a solution for
tclConfig.sh not being found.
I believe the thing to do in this situation is to specify
--with-tcl-version=8.4 when you configure since you can't determine what
TCL version to use. Your patch would obviously not work for TCL 8.0, 8.3,
8.5, or whatever :-). So it isn't really a viable solution.
Also I'm going to build a new set of toolchains for a arm-elf (AEB-1). I have
a 2.95 set working but want to test 3.2 branch.
Will I get any problems/improvements with 3.2 branch? Should I stick with
2.95?
We have updated eCos CVS and the upcoming beta release to work with 3.2.1
or later. Plain 3.2 won't work.
Do I need to patch 3.2 gcc like old 2.95 instructions in ecos site?
Nope. There are some other differences when building too. Search the
mailing list archives for when this has been discussed before (link
below). Searching for "newlib libgloss gcc" will probably do it.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[ can rejoice because thorns have roses." -Lincoln ]-- Opinions==mine
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss