Mail Archives: djgpp/2001/08/27/02:37:12
Will Robinson wrote:
>
> string s = "yay!";
As Andris mentioned, this should say std::string. gcc3 is much more
standards-compliant than its predecessors and has the std namespace on
by default.
> It's been a long road getting to this point, and I'd like to imagine that
> I see the finish line. I hope this isn't information overload, but I
> repeated the steps I've taken to build the cross compiler as it is
> currently, and carefully noted every little thing I did. Below is the
> sequence of steps I took (Tim, this might also help you get yours going if
> you try to build one in the near future).
And I'm sure it'll help many others as well.
> libgcc1-test: libgcc1-test.o native $(GCC_PARTS)
> @echo "Testing libgcc1. Ignore linker warning messages."
> # $(GCC_FOR_TARGET) $(GCC_CFLAGS) libgcc1-test.o -o libgcc1-test \
> # -nostartfiles -nostdlib `$(GCC_FOR_TARGET) --print-libgcc-file-name`
> touch libgcc1-test
>
> (note the #'s)
> (recommended by http://www.delorie.com/howto/djgpp/linux-x-djgpp.html)
I'm not entirely sure this is still needed; at least I don't recall
problems with this. Still, it probably doesn't hurt either.
> 24. edit getpwd.c, adding #define PATH_MAX 512 to the top.
> (got value from djgpp limits.h)
This is just a workaround - you still won't get PATH_MAX by
including <limits.h>, I think. The proper fix would be to
change gcc's version of limits.h to #include_next "limits.h"
before its final #endif (I think this is how Andris' port
does it as well, but I'm not sure). The file in question
seems to be gcc/glimits.h (which gets installed as
$prefix/lib/gcc-lib/$target/$version/include/limits.h).
- Raw text -