New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OS X ld warning with weird paths #5418

Closed
andriytyurnikov opened this Issue Aug 24, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@andriytyurnikov

andriytyurnikov commented Aug 24, 2018

When building from master on OS X, there is a weird warning:

[100%] Linking CXX executable nodeos
ld: warning: text-based stub file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd and library file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation are out of sync. Falling back to library file for linking.
ld: warning: text-based stub file /System/Library/Frameworks//Security.framework/Security.tbd and library file /System/Library/Frameworks//Security.framework/Security are out of sync. Falling back to library file for linking.
ld: warning: text-based stub file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd and library file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation are out of sync. Falling back to library file for linking.
ld: warning: text-based stub file /System/Library/Frameworks//Security.framework/Security.tbd and library file /System/Library/Frameworks//Security.framework/Security are out of sync. Falling back to library file for linking.

You may see double slash in every path
/System/Library/Frameworks//...
Which is weird

@jgiszczak

This comment has been minimized.

Show comment
Hide comment
@jgiszczak

jgiszczak Aug 24, 2018

Contributor

This is caused by either a lack of an update in the XCode command-line tools or a bug in its installer. You may ignore it if you like. It is benign. If you prefer to eliminate it, you get to manually correct the situation with your choice of horrible hacks. Both options amount to reinstalling the XCode command-line tools.

Option 1:

sudo mv /Library/Developer/CommandLineTools /Library/Developer/CommandLineTools.old
xcode-select --install
sudo rm -rf /Library/Developer/CommandLineTools.old

Option 2:

touch /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress;
PROD=$(softwareupdate -l |
  grep "\*.*Command Line" |
  head -n 1 | awk -F"*" '{print $2}' |
  sed -e 's/^ *//' |
  tr -d '\n')
softwareupdate -i "$PROD" --verbose;
rm /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress;

Option 2 has the benefit of working even without a logged in UI and without any scary/slightly dangerous rm -rfs. Option 1 has the benefit of being simpler. The choice is yours.

Contributor

jgiszczak commented Aug 24, 2018

This is caused by either a lack of an update in the XCode command-line tools or a bug in its installer. You may ignore it if you like. It is benign. If you prefer to eliminate it, you get to manually correct the situation with your choice of horrible hacks. Both options amount to reinstalling the XCode command-line tools.

Option 1:

sudo mv /Library/Developer/CommandLineTools /Library/Developer/CommandLineTools.old
xcode-select --install
sudo rm -rf /Library/Developer/CommandLineTools.old

Option 2:

touch /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress;
PROD=$(softwareupdate -l |
  grep "\*.*Command Line" |
  head -n 1 | awk -F"*" '{print $2}' |
  sed -e 's/^ *//' |
  tr -d '\n')
softwareupdate -i "$PROD" --verbose;
rm /tmp/.com.apple.dt.CommandLineTools.installondemand.in-progress;

Option 2 has the benefit of working even without a logged in UI and without any scary/slightly dangerous rm -rfs. Option 1 has the benefit of being simpler. The choice is yours.

@gaochunmeng

This comment has been minimized.

Show comment
Hide comment
@gaochunmeng

gaochunmeng Oct 1, 2018

Download the current version of the system reinstall to solve this problem, data will not be lost. I have solved this problem.

gaochunmeng commented Oct 1, 2018

Download the current version of the system reinstall to solve this problem, data will not be lost. I have solved this problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment