#40183 closed defect (invalid)
compiler_blacklist_versions-1.0: cannot detect llvm-gcc-4.2 version with Xcode 5
| Reported by: | joel.esler@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.2.0 |
| Keywords: | Cc: | drkp (Dan Ports), ryandesign (Ryan Carsten Schmidt), jeremyhu (Jeremy Huddleston Sequoia) | |
| Port: |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
sudo port install latex2html
---> Computing dependencies for latex2html
Error: Dependency 'texlive-bin' not found.
To report a bug, follow the instructions in the guide:
http://guide.macports.org/#project.tickets
Error: Processing of port latex2html failed
Attachments (1)
Change History (16)
comment:1 Changed 11 years ago by joel.esler@…
| Cc: | joel.esler@… added |
|---|
comment:2 follow-up: 3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | dports@… added; joel.esler@… removed |
|---|---|
| Description: | modified (diff) |
| Summary: | dependancies for latex2html not found → latex2html: Error: Dependency 'texlive-bin' not found |
Well, the texlive-bin port should exist. I wonder why it doesn't on your system.
Try running selfupdate verbosely and saving the output to a file. If texlive-bin still doesn't exist after doing that, attach the log here.
sudo port -v selfupdate 2>&1 | tee selfupdate.log
comment:3 Changed 11 years ago by joel.esler@…
Replying to ryandesign@…:
Well, the texlive-bin port should exist. I wonder why it doesn't on your system.
Try running selfupdate verbosely and saving the output to a file. If texlive-bin still doesn't exist after doing that, attach the log here.
sudo port -v selfupdate 2>&1 | tee selfupdate.log
Attached selfupdate.log
Changed 11 years ago by joel.esler@…
| Attachment: | selfupdate.log added |
|---|
comment:4 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
Aha, so several ports including texlive-bin failed to be indexed because:
Failed to parse file tex/texlive-bin/Portfile: can't set "compiler.blacklist": couldn't determine build number of compiler "llvm-gcc-4.2"
This suggests your llvm-gcc-4.2 compiler is faulty. What happens when you run:
/usr/bin/llvm-gcc-4.2 -v
Assuming the result is an error message, reinstall the Xcode command line tools.
comment:5 follow-up: 6 Changed 11 years ago by joel.esler@…
/usr/bin/llvm-gcc-4.2 -v Apple LLVM version 5.0 (clang-500.1.65) (based on LLVM 3.3svn) Target: x86_64-apple-darwin13.0.0 Thread model: posix
comment:6 follow-up: 7 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to joel.esler@…:
/usr/bin/llvm-gcc-4.2 -v Apple LLVM version 5.0 (clang-500.1.65) (based on LLVM 3.3svn) Target: x86_64-apple-darwin13.0.0 Thread model: posix
So you’re running Xcode 5 DP on Mavericks. You could have mentioned that sooner.
comment:7 Changed 11 years ago by larryv (Lawrence Velázquez)
| Cc: | jeremyhu@… added |
|---|---|
| Summary: | latex2html: Error: Dependency 'texlive-bin' not found → compiler_blacklist_versions-1.0: cannot detect llvm-gcc-4.2 version with Xcode 5 |
We should probably just ignore llvm-gcc-4.2 under Xcode 5.
comment:9 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
I'm confused. Apple stated in the Xcode release notes that "Xcode 4.6 is the last release to include the LLVM-GCC compiler". Then why does /usr/bin/llvm-gcc-4.2 exist in Xcode 5? Is it a symlink to clang or something? Because that looks like the kind of output clang would produce, not the kind of output llvm-gcc-4.2 would produce.
I think what I'd like to do is improve the compiler_blacklist_versions portgroup so that if it cannot find the version number string, then it considers the compiler blacklisted instead of throwing an error.
comment:10 follow-up: 11 Changed 11 years ago by joel.esler@…
It's a symlink. Unfortunate result of another hack used to get another port working.
comment:11 Changed 11 years ago by larryv (Lawrence Velázquez)
Replying to joel.esler@…:
It's a symlink. Unfortunate result of another hack used to get another port working.
Remove it and paste the output of port info texlive-bin, please.
comment:12 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:13 Changed 11 years ago by joel.esler@…
Paste of the end of the output. (After removing the symlink)
Failed to parse file tex/texlive-bin/Portfile: can't set "compiler.blacklist": couldn't determine build number of compiler "llvm-gcc-4.2" Adding port x11/xchm Total number of ports parsed: 89 Ports successfully parsed: 80 Ports failed: 9 Up-to-date ports skipped: 17371 hostname:~ name$ port info texlive-bin Error: Port texlive-bin not found
comment:14 follow-up: 15 Changed 11 years ago by jeremyhu (Jeremy Huddleston Sequoia)
You should fix your 'Ports failed: 9'
comment:15 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Replying to jeremyhu@…:
You should fix your 'Ports failed: 9'
As the already-attached log says, the reason they failed is "can't set "compiler.blacklist": couldn't determine build number of compiler "llvm-gcc-4.2"".
If a given compiler does not exist, the compiler_blacklist_versions portgroup ignores it and moves on. The fact that it didn't ignore it and move on proves that the compiler still exists.
On my Mountain Lion system, the llvm-gcc-4.2 that MacPorts tests turns out not to be /usr/bin/llvm-gcc-4.2 but rather /Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2. Does that still exist? What does it say:
/Applications/Xcode.app/Contents/Developer/usr/bin/llvm-gcc-4.2 -v
Cc Me!