Mail Archives: djgpp-workers/2001/03/13/01:42:39
On Mon, 12 Mar 2001, Laurynas Biveinis wrote:
> > > Linking fails on cpp0 because target_flags (used by SUPPORTS_ONE_ONLY
> > > macro defined in the djgpp.h config file which is instantiated in
> > > cppinit.c) is defined in rtlanal.c which is not included in the
> > > link. This can be fixed by also defining target_flags in cppinit.c,
> > > though that probably isn't the right, as, as far as I can see, they
> > > are not modified anywhere.
>
> I think Mark has fixed this one, however the patch hasn't been applied yet.
I saw patch from Mark.
>
> > Tried the same and run into the trouble with building libstdc++-v3:
>
> [...things not working...]
>
> Erm, cross-compiling libstdc++-v3 isn't supported at all for now, as
> maintainers told me.
>
wrong links to newlib related header files were created only when builing
Linux to DJGPP cross-compiler. There were no such problem when I
tried to cross-build native compiler for DJGPP under Linux (I got correct
links in this situation)
> > After that I tried build under Linux gcc-3.0 20010311 as native compiler for DJGPP.
> > (I think it would be good test for cross-compiler)
>
> [...]
>
> Thanks for checking. I'll try to get things fixed when I have time
> (if you or Mark don't do it before...)
>
> > So perhaps I should look whether native compiler for DJGPP I built works at all ...
>
> Well, native C and C++ compilers did work a week ago, and libstdc++-v3 almost
> worked. But GCC bit-rots veeeery fast indeed...
Didn't really test C rather than with cross-building GCC itself, but with
C++ I had libstdc++-v3 related problems:
crashes in iostream related static constructors at program startup both
when compiled with Linux to DJGPP cross-compiler and native compiler for
DJGPP.
Andris
- Raw text -