[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Results of test runs
From: |
Ralf Wildenhues |
Subject: |
Re: Results of test runs |
Date: |
Tue, 17 Jan 2006 15:03:35 +0100 |
User-agent: |
Mutt/1.5.11 |
Hi Leif,
* Leif Ekblad wrote on Tue, Jan 17, 2006 at 11:47:18AM CET:
> > This test has $host and $build i686-pc-linux-gnu, but we would like to
> > see how it fares on RDOS. So if RDOS is a cross-target, you would use
> > something similar to
> > configure --host=i686-rdos-whatever
> > (adjust to the appropriate value/your toolchain prefix) and possibly
> > specify some of them also manually (CC, LD, AR, ..)
>
> It says "checking host system type... Invalid configuration 'rdos' : machine
> not recognized"
Oh, yes, I guess you should incorporate your changes to config.guess and
config.log into libtool's copy of those files. Libtool imports those
files just as GCC does. (And no, I do not know how you named your
toolchain; please fill in the correct values yourself).
For the next failure you are likely to encounter, please provide a bit
more information: excerpts from config.log are usually helpful.
> > and if you can build natively on RDOS, just do that, it's bound to be
> > simpler.
>
> No, that is not possible. It might be some day, but not right now.
OK.
> > I'm not sure what your goal is; your recent question indicates that you
> > need the libtool changes in order to be able to create a GCC that
> > targets RDOS. Is that correct?
>
> Yes. GCC uses the libtool.m4 file, and I need RDOS to be defined
> there.
OK.
> > Have you managed to either get them
> > to apply your libtool-related changes, and/or have you maybe managed
> > to just apply the yourself to a local GCC source tree and build from
> > that, including regeneration of the generated files.
>
> I've added them manually to GCCs libtool.m4, and then the build
> process of GCC + libstdc++-v3 works just fine. I'm trying to get
> the patches accepted for GCC.
As far as I know, libtool patches are ok for GCC as soon as we apply
them to our CVS tree. I have already done that, because your patches
were very simple and it was virtually impossible for them to do harm
(please gently ignore my forward-porting brown paper bag..)
So from their standpoint, the patches should be acceptable.
You may be able to do better, though: we may be able to find out more
about your system by running libtool's test suite on it, and thus
improve libtool's RDOS support.
> > (Note I don't
> > know exactly how that works within the GCC source tree, but I guess
> > they have some documentation that explains how to do this?)
>
> A guy refered me to the libtool project, so I assumed it was done in
> a similiar way as config.sub and config.guess, some files being imported
> to GCC, but it doesn't seem like this is how it works.
AFAIK that is how it works.
> It turns out there are significant differences between the GCC and
> libtool version of libtool.m4.
For what you are trying to achieve, the differences are not significant.
A bit of work, maybe, but not much.
Cheers,
Ralf
- Re: FYI: [PATCH] RDOS support for libtool, (continued)
- Re: FYI: [PATCH] RDOS support for libtool, Ralf Wildenhues, 2006/01/13
- Re: FYI: [PATCH] RDOS support for libtool, Leif Ekblad, 2006/01/13
- Re: FYI: [PATCH] RDOS support for libtool, Ralf Wildenhues, 2006/01/13
- Re: FYI: [PATCH] RDOS support for libtool, Peter O'Gorman, 2006/01/13
- Re: FYI: [PATCH] RDOS support for libtool, Leif Ekblad, 2006/01/13
- Re: FYI: [PATCH] RDOS support for libtool, Ralf Wildenhues, 2006/01/13
- Re: FYI: [PATCH] RDOS support for libtool, Leif Ekblad, 2006/01/13
- Results of test runs, Leif Ekblad, 2006/01/17
- Re: Results of test runs, Ralf Wildenhues, 2006/01/17
- Re: Results of test runs, Leif Ekblad, 2006/01/17
- Re: Results of test runs,
Ralf Wildenhues <=
- Re: Results of test runs, Leif Ekblad, 2006/01/17
- Re: Results of test runs, Ralf Wildenhues, 2006/01/17
- Re: Results of test runs, Peter O'Gorman, 2006/01/17