Wasn't able to tell if this was already happening. So this could be a non-issue. <

This flag gets set in the llvm-compilers feedstock, see the <a href="https://github.co

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Adding -headerpad_max_install_names to LDFLAGS on macOS about aggregate HOT 5 CLOSED

anacondarecipes commented on July 23, 2024

Adding -headerpad_max_install_names to LDFLAGS on macOS

from aggregate.

Comments (5)

msarahan commented on July 23, 2024

please refer to the Dropbox Paper document for the conda-forge compiler meeting on Nov. 11 last year. We've had this flag in place longer than it has been in toolchain.

https://paper.dropbox.com/doc/2017-11-16-2018-02-20-meeting-notes-compiler-1lYaDIP93JRzzQZBlicxg

from aggregate.

jjhelmus commented on July 23, 2024

This flag gets set in the llvm-compilers feedstock, see the conda_build_config.macOS_10.9.yaml

from aggregate.

msarahan commented on July 23, 2024

@jjhelmus, I am pretty sure that is vestigial. These need to be set in an activation script package, which we split off from the actual compiler packages.

I think the right link is https://github.com/AnacondaRecipes/aggregate/blob/master/clang/build.sh

This is in the Dropbox did I linked above.

from aggregate.

jakirkham commented on July 23, 2024

So I think this is highlighting the same confusion that caused me to raise this issue. Where do we look for how the compiler works? Ideally one doesn't want to rely on meetings docs from ~6mos ago (who knows if that is current), looking at the code for this sort of stuff is far more preferable, but it is not obvious where to look. Does it make sense for the compilers to live in their own repo so this is easier to see?

from aggregate.

msarahan commented on July 23, 2024

https://conda.io/docs/user-guide/tasks/build-packages/compiler-tools.html#customizing-the-compilers We need the similar docs for Linux and win. Compilers in their own repo is reasonable. Having them as plain folders in the aggregate repo does make them hard to find. I'd say though that the clang docs really should be easily findable, and I'd like to understand what you looked for so that maybe we can add words to the docs that would help Google find them.

…

On Sat, Apr 21, 2018, 15:11 jakirkham ***@***.***> wrote: So I think this is highlighting the same confusion that caused me to raise this issue. Where do we look for how the compiler works? Ideally one doesn't want to rely on meetings docs from ~6mos ago (who knows if that is current), looking at the code for this sort of stuff is far more preferable, but it is not obvious where to look. Does it make sense for the compilers to live in their own repo so this is easier to see? — You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub <#45 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AACV-TdDJARgMlh2X9JlLzJvrHhdekMjks5tq5KHgaJpZM4TeIis> .

from aggregate.

Adding -headerpad_max_install_names to LDFLAGS on macOS about aggregate HOT 5 CLOSED

Comments (5)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent