(I recognize your name from somewhere... maybe we have talked before? Maybe
I have some piece of software you wrote? :)
Quote:> But to get the 'thumb-elf' support into gcc-2.95.2, only the config
> files for it are necessary. So it is really stupid for a modem user
> to download the Hitachi's 100 Mbytes.
> And a little selfish from those
> having a no-cost line (someone else like the taxpayers pay the line
Well, this is America here.. broadband is cheap (I can get 640kbps DSL
unlimited access for free in my area, only have to buy the modem). People
are more and more considering the entire Internet as a kind of
speed-impaired branch of their LAN.
Quote:> I remember having taken the 'thumb-elf' config stuff from the
> eCos-1.2.1 DevTools sources (gcc-2.9-arm-1990321) or from the
> egcs-snapshots from the autumn-1999... No problems with the build,
> the 'thumb-elf'-Lego-piece seemed to fit quite well to the earlier
> gcc-2.95.2 pieces...
OK, I did not think of that one. I will try it. Thanks very much for this
suggestion. Have you successfully built eCos using this resulting set of
Quote:> There can be some minor problems with macros, but everyone who is
> not a newbie in C can solve those problems. The '99r1p1' should be
> quite near 2.95.2, so I wouldn't expect any problems...
Well, I am definitely not a newbie in C :) (I've been working fulltime in C
for ... oooh ... 10 years? more?), but I am not a guru at building and
maintaining gcc, also I am totally new to eCos.
Quote:> Of course I can email my 'thumb-elf' config stuff from my gcc-2.95.2
> sources, or snailmail a prebuilt toolset for 'thumb-elf' for Win32-
Snailmailing binaries is I think overkill for the situation... :))) Only if
it is no trouble to you, if you could mail your configure script and the two
header files you mentioned, it would be useful.
Quote:> host (Mingw-hosted, built under Linux), on a CDR against something
> else like the Hitachi-99r1p1 distribution on a CDR too (if Hitachi
> now sends their free November-2000 CDROM with the 99r1p1 sources,
> then against something else as 'big' from the net...).
Hey, if you want me to download this stuff and burn it to a CD-R for you,
that is no problem; let me know what you want and I will download it
overnight and burn the next day. CDs are cheap, bandwidth is free. I'm so
glad my employer brought me to this country :)))))))))))))) One day it will
even have a President, probably.
Quote:> How to build under Windoze is then another issue which I wouldn't
> like to touch. I can understand that some people may have big troubles
> to find any other Unix-like build environment (like Linux), than only
Hey there, I am not wedded to Windows! :) But most of my hardware
development tools (EPROM burner, other programmable IC burners, JTAG
sniffer, etc) only run in DOS (or maybe OS/2 DOS box ;). So I am basically
limited to running Win9x/ME on my development PCs. Yes, I could put dual
boot Linux on my machine, but I really don't want the maintenance and the
annoyance of having a partitioned hard drive (umsdos is slow!) etc.
Quote:> Windoze and Cygwin, but then that is the big problem, not how to build
> a toolset on the expected Unix-like system. Who has ever claimed that
Hmm? I don't think my problem stems from building inside Windows. I was also
trying the exact same build process under Red Hat Linux, it gives the same
errors. Actually I would be satisfied to get a working toolchain for Linux,
but it is preferable to get a Cygwin or mingw32 set. Cygwin is the most
preferred because it is closest to the Red Hat reference environment
(meaning that I will have to do the minimum of massage-work when some
Quote:> all Cygwin-stuff must be built under Cygwin, all DOS/DJGPP2-stuff
> under DOS, all thumb-elf stuff under a thumb-elf system etc., when
> cross-compiling has been made possible when using GCC.
I would rather not try to cross-compile Cygwin binaries on another system; I
already have enough complexity I don't understand here :)
-- Lewin A.R.W. Edwards (Embedded Engineer)
Personal http://www.larwe.com/ and http://www.zws.com/