[jira] Commented: (STDCXX-1052) Hardcoded linker options (`-lm' & `-lc') cause problems when configuring with a different compiler than `gcc'

["Martin Sebor (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/STDCXX-1052?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003064#comment-13003064 ] 

Martin Sebor commented on STDCXX-1052:
--------------------------------------

I don't see a patch...

{{-lc}} should never be necessary. It's there only to make specifying {{-lm}} easier. We should be able to unset {{lib}} and avoid passing {{-l$lib}} when it's unset. {{-lm}} is usually necessary, though.

But neither should be hardcoded in either place. We should either autodetect it or let the user specify it in a config file.

The wrinkle is that we use the name of the library in the name of the macro (such as {{_RWSTD_NO_MBRTOWC_IN_LIBC}} or {{_RWSTD_NO_CBRTF_IN_LIBM}}).

> Hardcoded linker options (`-lm' & `-lc') cause problems when configuring with a different compiler than `gcc'

> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: STDCXX-1052
>                 URL: https://issues.apache.org/jira/browse/STDCXX-1052
>             Project: C++ Standard Library
>          Issue Type: Improvement
>         Environment: Linux and Embedded 
>            Reporter: Wojciech Meyer
>
> We are having problems with the configuration scripts. Our compiler
> refuses to accept `-lm' & `-lc' GNU style command line switches to
> denote linking with a standard library. They are hardcoded in
> `libc_decl.sh' and `makefile.common'.  We propose introducing a special
> `Makefile' variable `WITHOUT_BASE_LIBS' that excludes generating them
> for compilation of configuration files during the configure step.
> Patch is against trunk.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira