I don't have proper gcc installed (via brew or macports), but I think it would
make sense to first check what gcc does and supports.

On the other hand, if it's only aliases to existing options, possibly which are
enabled only on OSX, then I don't think [m]any would object, and it should
be fairly simple to add and possibly revert later.


     On Saturday, July 11, 2020, 08:09:07 AM GMT+3, Christian Jullien 
<eli...@orange.fr> wrote:  
 
 <!--#yiv4073999434 _filtered {}#yiv4073999434 #yiv4073999434 
p.yiv4073999434MsoNormal, #yiv4073999434 li.yiv4073999434MsoNormal, 
#yiv4073999434 div.yiv4073999434MsoNormal 
{margin:0in;margin-bottom:.0001pt;font-size:11.0pt;font-family:"Calibri", 
"sans-serif";}#yiv4073999434 a:link, #yiv4073999434 
span.yiv4073999434MsoHyperlink 
{color:blue;text-decoration:underline;}#yiv4073999434 a:visited, #yiv4073999434 
span.yiv4073999434MsoHyperlinkFollowed 
{color:purple;text-decoration:underline;}#yiv4073999434 
span.yiv4073999434EmailStyle17 {font-family:"Calibri", 
"sans-serif";color:windowtext;}#yiv4073999434 .yiv4073999434MsoChpDefault 
{font-family:"Calibri", "sans-serif";} _filtered {}#yiv4073999434 
div.yiv4073999434WordSection1 {}-->
Hi maintainers,

  

As often, Apple reinvent the wheel and makes things differently.

Among other, clang handles shared libs .dylib with a different set of compiler 
options.

For example, -shared is replaced by –dynamiclib etc…

  

It means that a ./configure must test if it uses clang or tcc and adapt its 
compiler options.

  

Question: with proper #if/#endif do you allow me to handle clang specific 
options on macos?

  

FYI I currently see 4/5 options to add (or at least silently drop) to support 
tcc on macos with a better compatibility with clang.

  

C.
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel
  
_______________________________________________
Tinycc-devel mailing list
Tinycc-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/tinycc-devel

Reply via email to