public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Dave Nebinger" <dnebinger@joat.com>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Pixie does not run.
Date: Fri, 02 Sep 2005 10:29:30 -0400	[thread overview]
Message-ID: <001601c5afca$bb6a7d20$3a01010a@jnetlab.lcl> (raw)
In-Reply-To: <20050901204517.2f8228a9@gentoo-00>

> If I replace
> the pixie emerged by portage does that mess up anything as far as
> portage is concerned?

Well, other than if an upgrade comes through emerge --update world would try
to overwrite what you install.

Otherwise portage will think it's in there.

> I have one more dumb question.  What man page do I read to understand
> how to use LDFLAGS?  I was thinking this was a variable in make.conf
> however I just read the man page for make.conf and I see that it is not
> documented there.  Also looked around at gentoo.org documentation, but
> didn't find anything that helps yet.

LDFLAGS typically come in the -llib and -Lpath variety and are used to
ensure that additional libraries and paths are included in the link phase.
You typically won't need to add these (which is probably why there is little
if any reference in the gentoo doc).

Obviously there are more uses for LDFLAGS, but those above are used the
most.

If you do need them you can set up your environment variables before doing
the make process.  You can also use them on the command line ala
"LDFLAGS=-llib make", etc.



-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-09-02 14:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-31 12:40 [gentoo-user] Pixie does not run Adrian
2005-08-31 13:15 ` Dave Nebinger
2005-09-01 12:21   ` Adrian
2005-09-01 12:51     ` Dave Nebinger
2005-09-02  2:45       ` Adrian
2005-09-02 14:29         ` Dave Nebinger [this message]
2005-09-04 15:48           ` Adrian

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='001601c5afca$bb6a7d20$3a01010a@jnetlab.lcl' \
    --to=dnebinger@joat.com \
    --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