On Monday 14 December 2009 20:28:21 walt wrote: > Renat Golubchyk wrote: > > As you said, you really are confused. :-) Maybe I wasn't clear enough. > > Anyway, I've written a program, and I need it as a statically linked > > binary. In order to link statically the linker (ld) needs all the used > > libraries in static form, i.e. as a .a and not as a .so file. Since > > portage does not build static libraries by default I need a way to tell > > portage that I really do want to have .a files built. > > > > I do _not_ want to create a Gentoo package, at least not at this stage > > of development. > > Still confused :o(
Yes, I'm not surprised. you read the OPs post upside down. He does not want to *generate* static binaries, he wants to *use* them. Presumably he has written an app (that possibly must be distributed as a contained unit) that must statically link the libs it uses. Those libs would have been put there by portage, but he needs portage to build .a's, not only .so's > > Portage is for building Gentoo packages -- if you don't want to build a > Gentoo package then why is portage involved? You can compile and link > your program with any flags you want to, so as to get static binaries. OP, I'm not sure why you have a problem. A quick search on my box shows that most libs (of the small number I checked) have .a and .so Please post emerge --info and details of which libs you know at this point you do need. -- alan dot mckinnon at gmail dot com
