[Bug libstdc++/21549] Configure options hard to find

[egallager at gcc dot gnu.org via Gcc-bugs]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21549

--- Comment #7 from Eric Gallager  ---
(In reply to Andrew Pinski from comment #1)
> Confirmed, --with-pic being documented would be very nice even though it is
> a generic libtool 
> configure option, it is most used with libstdc++ as shown by the bug reports
> about the using static 
> libstdc++ in a shared library.

Note that documenting it has the risk of leading people to think that
--with-pic (or --without-pic) is ok to use even in situations when it's not;
e.g. x86_64 must always be PIC. If the flag is going to be documented, any such
restrictions should be documented as well.

[Bug libstdc++/21549] Configure options hard to find

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21549

Eric Gallager  changed:

   What|Removed |Added

   See Also||https://gcc.gnu.org/bugzill
   ||a/show_bug.cgi?id=82824

--- Comment #6 from Eric Gallager  ---
(In reply to Eric Gallager from comment #5)
> The issue of undocumented configure options also came up in bug 82824,
> although that was a tangent so I won't add it under "See Also" 
> 

Actually I've changed my mind; I now believe that even tangents are sufficient
for "See Also" status.

[Bug libstdc++/21549] Configure options hard to find

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21549

--- Comment #5 from Eric Gallager  ---
The issue of undocumented configure options also came up in bug 82824, although
that was a tangent so I won't add it under "See Also" 

(In reply to Benjamin Kosnik from comment #3)
> 
> As an aside, are a lot of these java config opts actually still relevant?
> 
> -benjamin

No, java has been removed.

[Bug libstdc++/21549] Configure options hard to find

[egallager at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21549

Eric Gallager  changed:

   What|Removed |Added

 CC||egallager at gcc dot gnu.org

--- Comment #4 from Eric Gallager  ---
There's always ./configure --help=recursive from the top level; the "recursive"
makes it print the help text from subdirs like libstdc++ too.

[Bug libstdc++/21549] Configure options hard to find

[bkoz at gcc dot gnu dot org]

--- Comment #3 from bkoz at gcc dot gnu dot org  2010-02-05 17:40 ---

Would love to see something standardized for all libs in gcc. My preference is
to have libstdc++ config docs linked to in gcc docs. (No duplication, just
alias.)

One thing that could be done would be to add a "C++ Specific Option" to
http://gcc.gnu.org/install/configure.html

And link to 
http://gcc.gnu.org/onlinedocs/libstdc++/manual/configure.html

Or options on that page, don't care.

As an aside, are a lot of these java config opts actually still relevant?

-benjamin


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21549

[Bug libstdc++/21549] Configure options hard to find

[paolo dot carlini at oracle dot com]

--- Comment #2 from paolo dot carlini at oracle dot com  2010-02-05 13:12 
---
Benjamin, any opinion about this issue?


-- 

paolo dot carlini at oracle dot com changed:

   What|Removed |Added

 CC||bkoz at redhat dot com


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21549

[Bug libstdc++/21549] Configure options hard to find

[pinskia at gcc dot gnu dot org]

--- Additional Comments From pinskia at gcc dot gnu dot org  2005-05-13 
18:01 ---
Confirmed, --with-pic being documented would be very nice even though it is a 
generic libtool 
configure option, it is most used with libstdc++ as shown by the bug reports 
about the using static 
libstdc++ in a shared library.

-- 
   What|Removed |Added

 Status|UNCONFIRMED |NEW
 Ever Confirmed||1
   Keywords||documentation
   Last reconfirmed|-00-00 00:00:00 |2005-05-13 18:01:45
   date||


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21549