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

llvm-ld warns when linking against shared libraries #1674

Closed
llvmbot opened this issue Apr 4, 2007 · 2 comments
Closed

llvm-ld warns when linking against shared libraries #1674

llvmbot opened this issue Apr 4, 2007 · 2 comments
Labels
bugzilla Issues migrated from bugzilla code-cleanup llvm-tools All llvm tools that do not have corresponding tag

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Apr 4, 2007

Bugzilla Link 1302
Resolution FIXED
Resolved on Mar 06, 2010 14:00
Version trunk
OS All
Reporter LLVM Bugzilla Contributor

Extended Description

When creating a native executable with llvm-ld and linking against a shared
(.so) library, using the -l option, llvm-ld generates the following warning:

llvm-ld: warning: Supposed library 'name_of_lib' isn't a library.

However, the produced executable seems to work fine, and seems to find
libname_of_lib.so through LD_LIBRARY_PATH just fine. Reid Spencer advised that
this is most likely a code cleanup bug.
@llvmbot
Copy link
Collaborator Author

llvmbot commented Apr 4, 2007

This is pretty easy. The IdentifyFileType method sys::Path is simply not
identifying native object file types. I'm augmenting it to recognize COFF, ELF
and Mach-O files (should cover most of our bases for a while) for a variety of
targets we support. If the object file/shared lib is not recognized, the warning
message will still be produced and it will still link (assuming its valid) but
in that case I think the warning message is justified (i.e. its telling us to
update the object file recognition in LLVM).

This should be fixed shortly.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Apr 4, 2007

Fixed with these patches:

http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070402/046781.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070402/046782.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070402/046783.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070402/046784.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070402/046785.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20070402/046786.html

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
troelsbjerre pushed a commit to troelsbjerre/llvm-project that referenced this issue Jan 10, 2024
@shahmishal
Merge pull request llvm#1674 from JDevlieghere/🍒/bastille/7208cb1ac43…
08b9379 
…e4be806bcb91c622fc1f8641e010b

[lldb] Remove XFAIL from now passing TestPtrRefs/TestPtreRefsObjC
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla code-cleanup llvm-tools All llvm tools that do not have corresponding tag
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@llvmbot