This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: Trouble running ecosconfig under Linux/alpha
- To: Stephen Williams <steve at icarus dot com>
- Subject: Re: [ECOS] Trouble running ecosconfig under Linux/alpha
- From: Jonathan Larmour <jlarmour at cygnus dot co dot uk>
- Date: Wed, 22 Nov 2000 05:29:20 +0000
- CC: ecos-discuss at sources dot redhat dot com
- Organization: Red Hat UK Ltd.
- References: <200011220420.UAA29747@icarus.com>
Stephen Williams wrote:
>
> jlarmour@cygnus.co.uk said:
> > The reason for my doubts was that I *have* heard of successes on alpha
> > linux, so there is hope :)
>
> If there is hope, I shall keep up the fight. Especially if my questions
> keep getting answered. It would be nice, if I manage to succeed, if
> the required steps are written down somewhere so the next Linux/alpha
> user will be able to find it.
Write a FAQ entry and I'll gladly put it in.
> jlarmour@cygnus.co.uk said:
> > gcc 2.95.2 sources include libstdc++.
>
> The issue is how to make sure the right libstdc++-*.so is brought in
> at runtime by a program that is compiled by a compiler and C++ library
> installed in a non-standard place. (Whew!( This is what I must figure
> out in order to get gcc-2.95.X to coexist with my existing compiler.
I think gcc 2.95.2 only tries to build libstdc++ statically so this may be
somewhat of a non-issue (except that the resulting ecosconfig may be a bit
plump).
> This is something I should be able to handle, though. It's rather time-
> consuming and I would just like some reasonable hope that it will solve
> the problem at hand.
I can't honestly say it is a certainty - but it's one of the first things
I'd try; or at least I'd say building gcc is easier than debugging libcdl
:). I was rather hoping another Alpha linux user would pipe up though.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault