On 08/29/11 20:33, Mike Frysinger wrote:
On Monday, August 29, 2011 23:09:07 Bryan Ischo wrote:
It is possible that what I am trying to do is invalid (use a static
libc.a when creating a dynamic libgcc_s.so), but nobody has said that
explicitly yet
it is wrong and really makes no sense. you're bleeding glibc symbols
(public and private) into a completely unrelated library.
I realize that this may make no sense for a final version of the
toolchain, but this is just an intermediate step where I don't mind
bending some rules to get things to work. That being said, I certiainly
would not expect the build system to support doing things beyond the
scope of what is correct so if what I am trying to do is not going to be
supported by the toolchain for that reason, then I'm happy to give up on
that approach.