octave-patch-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-patch-tracker] [patch #8919] Start of patch to enable visibility


From: Markus Mützel
Subject: [Octave-patch-tracker] [patch #8919] Start of patch to enable visibility attributes for GCC in build system
Date: Fri, 1 Jan 2021 11:24:48 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.88 Safari/537.36 Edg/87.0.664.66

Follow-up Comment #27, patch #8919 (project octave):

When I started working on this again, I was expecting (or hoping) that Windows
would be the only "odd-ball" here. I hoped that the other platforms would
behave quite uniformly.
It turns out this is not the case: Even different compilers (gcc and clang)
for the same platform (Linux) interpret the visibility attributes
differently.

Maybe we should use visibility more conservatively or make it optional. But it
is also possible to wait for users on different platforms (darwin?) to report
if they see issues.

Meanwhile, I pushed a partial fix for compiling with clang here:
https://hg.savannah.gnu.org/hgweb/octave/rev/f207504ae98d

This still won't lead to a successful build with clang. But the linker will
complain about less missing symbols...

It takes some time to find something that works with gcc and with clang and
doesn't break the Windows build. And sometimes it is not clear to me why
something breaks. So, I'll try and push smaller changes that seem to be
working...

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/patch/?8919>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]