From: Daniel.Thibault@drdc-rddc.gc.ca (Thibault, Daniel)
Subject: [lttng-dev] The disable-libtool-linkdep-fixup configure option
Date: Tue, 29 Jan 2013 12:20:59 -0500 [thread overview]
Message-ID: <3CA1A65C03C1A34C81BBC6272782E6969BDD0C@valcartierex01.valcartier.drdc-rddc.gc.ca> (raw)
> > The default value of the option is 'yes' (re: configure.ac), which means the fixup is applied. Setting the option to another value, such as 'no', means the fixup is not applied.
> > Why then is the option named *disable*-libtool-linkdep-fixup? Shouldn't it be named *enable*-libtool-linkdep-fixup instead?
>
>Because the option is enabled by default on all systems. This is to facilitate cross-compilation on Debian/Ubuntu systems.
>
> Christian
If you had to compare the following two command lines, which one would you say disabled the fixup?
./configure --disable-libtool-linkdep-fixup=yes
./configure --disable-libtool-linkdep-fixup=no
The first line is the current default, and it leaves the fixup enabled (right?). That's why I suspect enable-libtool-linkdep-fixup would be a more meaningful name.
Daniel U. Thibault
R & D pour la d?fense Canada - Valcartier (RDDC Valcartier) / Defence R&D Canada - Valcartier (DRDC Valcartier)
Cyber s?curit? pour les missions essentielles (CME) / Mission Critical Cyber Security (MCCS)
Protection des syst?mes et contremesures (PSC) / Systems Protection & Countermeasures (SPC)
2459 route de la Bravoure
Qu?bec, QC G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada / Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>
next reply other threads:[~2013-01-29 17:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-29 17:20 Thibault, Daniel [this message]
2013-01-29 17:32 ` Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2013-01-29 16:34 Thibault, Daniel
2013-01-29 16:54 ` Christian Babeux
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=3CA1A65C03C1A34C81BBC6272782E6969BDD0C@valcartierex01.valcartier.drdc-rddc.gc.ca \
--to=daniel.thibault@drdc-rddc.gc.ca \
/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