Comments on uClibc++
Rob Landley
rob at landley.net
Tue Nov 4 03:41:34 UTC 2008
I had to remove -Wl,-z,defs from your LDFLAGS, otherwise the link died. Why
is that in there at all?
I realize I have to set CROSS= to the cross compiler prefix during the make,
but why does having it set to a strange unrelated value cause "make
defconfig" and "make install" to spit out a page of error messages? They
don't try to cross-compile anything, do they? (In case you're wondering, iin
my build script it's the destination path to install the cross compiler files
at. Most packages seem to use CROSS_COMPILE= as their prefix variable.)
The stuff in Rules.mak to filter out multiple trailing / doesn't seem needed,
because a path like "/usr//include" doesn't normally cause problems. The
Linux kernel treats zero length path components as synonymous with "." (as
does $PATH, by the way).
Having both PREFIX and UCLIBCXX_RUNTIME_PREFIX is A) unnecessary, B) a royal
pain to rip out to get it to actually install where I asked it to. Could you
just make PREFIX default to /usr/local if it hasn't been set like everybody
else does, and rip out the RUNTIME_PREFIX thing? (Unless it serves some
subtle non-obvious purpose?)
Rob
P.S. The wrapper unconditionally adds -lm after -lstdc++... Is that actually
needed? (Maybe it should be linked with --as-needed? I dunno this area...)
More information about the uClibc
mailing list