Skip to content
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.

Sign up for GitHub

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

Jump to bottom

run libtool command more explicitly #396

Open
GoogleCodeExporter opened this issue Apr 19, 2015 · 1 comment
Open

run libtool command more explicitly #396

GoogleCodeExporter opened this issue Apr 19, 2015 · 1 comment
Labels
auto-migrated Type-Patch

Comments

@GoogleCodeExporter
Copy link 

See below trace:
libtool: unrecognized option `-static'
libtool: Try `libtool --help' for more information.
I think we need a more explicit path for libtool, do you think so?
Indeed it should be a stuff in gyp, but what I do maybe helps some people like 
me do less confusing, why not?

Original issue reported on code.google.com by l900422m...@gmail.com on 14 Dec 2013 at 9:23

Attachments:
@GoogleCodeExporter
Copy link
Author 

anyone updates?

Original comment by yorkiefi...@gmail.com on 20 Nov 2014 at 10:11

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Type-Patch
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter