public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: RE: [gentoo-user] [OT] Open Office USE flags
Date: Sun, 28 Aug 2005 20:28:17 +1200	[thread overview]
Message-ID: <1125217697.11507.11.camel@sf.rout.dyndns.org> (raw)
In-Reply-To: <026801c5ab9b$b323b6f0$0501a8c0@croatus>

If you really want to know what a USE flag does on a particular ebuild
you have to:

1, read the ebuild and find what the USE flag switches on or off.
2, understand, from your knowledge of the package, what switching that
option on or off does.

for example, in openoffice:

nick@sf ~/mediatemp $ grep
hardened /usr/portage/app-office/openoffice/openoffice-1.1.4-r1.ebuild
IUSE="curl hardened java kde nptl zlib"
        #GCC 3.4 fixes, also needed for hardened
        #Fixes for hardened
        if use hardened; then
                epatch ${FILESDIR}/${PV}/hardened-link.patch

this shows that the effect (and the only effect) of using the hardened
flag is to patch the source with the file
${FILESDIR}/${PV}/hardened-link.patch

Translating, ${FILESDIR} is the files directory
under /usr/portage/app-office/openoffice

${PV} is "package version", ie in the case of openoffice-1.1.4 is 1.1.4

so the file is:

nick@sf ~/mediatemp $
cat /usr/portage/app-office/openoffice/files/1.1.4/hardened-link.patch
diff -ur solenv.orig/inc/unxlngi4.mk solenv/inc/unxlngi4.mk
--- solenv.orig/inc/unxlngi4.mk 2004-10-23 20:09:29.344518376 +0200
+++ solenv/inc/unxlngi4.mk      2004-10-23 20:09:43.084429592 +0200
@@ -156,8 +156,8 @@
 LINKFLAGS=-Wl,-z,combreloc $(LINKFLAGSDEFS) $(LINKFLAGSRUNPATH)

 # linker flags for linking applications
-LINKFLAGSAPPGUI= -Wl,-export-dynamic
-LINKFLAGSAPPCUI= -Wl,-export-dynamic
+LINKFLAGSAPPGUI= -Wl,-export-dynamic -Wl,-z,execheap
+LINKFLAGSAPPCUI= -Wl,-export-dynamic -Wl,-z,execheap

 # linker flags for linking shared libraries
 LINKFLAGSSHLGUI= -shared

you'll have to work out for yourself what this actually does. the
Changelog file might have a clue, or bugs.gentoo.org





On Sun, 2005-08-28 at 02:42 -0400, John Dangler wrote:
> Wilie~
> Thanks for the reply.  I did leave it out.  I kept reading and couldn't find
> anywhere except portage (and the hardened docs) where it would be necessary
> for anything in 'daily life'.  And, the references I did find for it were
> all linked to PIE.  The USE flags I quoted were from portage.  Looking at
> the package and selecting USE flags.  I've taken to looking at all of the
> information about a package before emerging -- it saves a lot of backstrokes
> in the long run, and I keep notes about which flags I've added to make.conf
> for which packages, along with the defaults that are already there...
> 
> John D
> 

> 
-- 
Nick Rout <nick@rout.co.nz>

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2005-08-28  8:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-28  3:07 [gentoo-user] [OT] Open Office USE flags John Dangler
2005-08-28  6:06 ` Willie Wong
2005-08-28  6:42   ` John Dangler
2005-08-28  8:28     ` Nick Rout [this message]
2005-08-28 13:43       ` John Dangler

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=1125217697.11507.11.camel@sf.rout.dyndns.org \
    --to=nick@rout.co.nz \
    --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