public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Michael Orlitzky <michael@orlitzky.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] Questions about building from source tarball
Date: Tue, 30 Oct 2012 13:24:43 -0400	[thread overview]
Message-ID: <50900D5B.6030409@orlitzky.com> (raw)
In-Reply-To: <20121030085650.GB7402@waltdnes.org>

On 10/30/2012 04:56 AM, Walter Dnes wrote:
>   Several years ago, back in the days of Mozilla 0.9x and Phoenix, I
> used to build Mozilla and/or Pheonix from the source tarball.  I've been
> using Gentoo for years, and I've forgotten a lot about building manually
> from source.  I asked this question on mozillazine.org, but no answers
> yet.  Hopefully, I can get some help here.  I'm looking at
> https://developer.mozilla.org/en-US/docs/Simple_SeaMonkey_build and I
> have a few questions...
> 
> 1) What options do I need to set to make Seamonkey (or Firefox) build
> in, and run from, a local dir, e.g. "${HOME}/seamonkey"?  Something to
> do with "prefix" and "exec-prefix"?  I'd prefer to avoid jumping to root
> for the install.  And throwing in files in /usr that portage doesn't
> know about, is begging for trouble.
> 

Most of the configuration directives reference the PREFIX by default.
This is from GNU tar, but FF is probably the same:

  Installation directories:
  --prefix=PREFIX         ... [/usr/local]
  --exec-prefix=EPREFIX   ... [PREFIX]

  Fine tuning of the installation directories:
    --bindir=DIR            ... [EPREFIX/bin]
    --sbindir=DIR           ... [EPREFIX/sbin]
    ...

So by default, everything eventually references PREFIX, which defaults
to /usr/local. You can change PREFIX to be e.g. ~/local/ and the rest
should wind up in subdirectories of that. Just double check to make sure
all of the FF defaults refer back to PREFIX.


> 2) I read the instructions on how to pass the "O2" flag to the make and
> compile process. What about the rest of the CFLAGS line?  My CFLAGS are
> 

I use this in my ~/.bashrc:

  # Grab CFLAGS, etc. from make.conf.
  . /etc/portage/make.conf

  # LDFLAGS comes from.. somewhere else.
  LDFLAGS="-Wl,-O1 -Wl,--as-needed"

  # Portage does this for us.
  MAKE="make ${MAKEOPTS}"

If anyone knows of a slicker way to do LDFLAGS, I'd like to know.


  reply	other threads:[~2012-10-30 17:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30  8:56 [gentoo-user] [OT] Questions about building from source tarball Walter Dnes
2012-10-30 17:24 ` Michael Orlitzky [this message]
2012-10-31  0:26 ` [gentoo-user] " walt
2012-11-01  0:29   ` Walter Dnes
2012-11-02  3:33     ` David Relson
2012-11-02  9:14       ` Neil Bothwick

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=50900D5B.6030409@orlitzky.com \
    --to=michael@orlitzky.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