public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Allan Gottlieb <gottlieb@nyu.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user]  Re: Building static libraries
Date: Mon, 14 Dec 2009 15:19:02 -0500	[thread overview]
Message-ID: <yu9my1lpavd.fsf@nyu.edu> (raw)
In-Reply-To: <hg5vuq$f9p$1@ger.gmane.org> (walt's message of "Mon, 14 Dec 2009 10:28:21 -0800")

At Mon, 14 Dec 2009 10:28:21 -0800 walt <w41ter@gmail.com> 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(
>
> 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.

Portage is also for (indeed, is primarily used for) fetching and
installing Gentoo packages.  The OP wants portage to install the
statically linked version of libraries for which it currently installs
only the dynamically linked versions.

allan



  reply	other threads:[~2009-12-14 22:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-13 19:18 [gentoo-user] Building static libraries Renat Golubchyk
2009-12-13 20:40 ` Albert Hopkins
2009-12-14  0:27   ` Renat Golubchyk
2009-12-13 22:47 ` [gentoo-user] " walt
2009-12-14  0:27   ` Renat Golubchyk
2009-12-14  1:53     ` Albert Hopkins
2009-12-14  2:19       ` Renat Golubchyk
2009-12-14 18:28     ` walt
2009-12-14 20:19       ` Allan Gottlieb [this message]
2009-12-14 20:25       ` Alan McKinnon
2009-12-15  6:53         ` Renat Golubchyk
2009-12-14 21:16       ` Renat Golubchyk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=yu9my1lpavd.fsf@nyu.edu \
    --to=gottlieb@nyu.edu \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox