Opened 12 years ago
Last modified 12 years ago
#34564 closed defect
vis5d: unable to infer tagged configuration — at Version 1
| Reported by: | ykzhou@… | Owned by: | takeshi@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.1 |
| Keywords: | Cc: | ryandesign@… | |
| Port: | vis5d |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
---> Computing dependencies for vis5d
---> Building vis5d
Error: org.macports.build for port vis5d returned: command execution failed
Please see the log file for port vis5d for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_science_vis5d/vis5d/main.log
Error: Processing of port vis5d failed
Change History (2)
Changed 12 years ago by ykzhou@…
comment:1 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Description: | modified (diff) |
| Owner: | changed from macports-tickets@… to takeshi@… |
| Port: | vis5d added |
| Summary: | port vis5d returned: command execution failed → vis5d: unable to infer tagged configuration |
Note: See
TracTickets for help on using
tickets.
The actual relevant error from the log is:
Since this project appears to be dead, no newer version having been released in the past ten years, we will need to patch vis5d to specify the --tag parameter every time it invokes the libtool program. We've fixed this in several other ports you can look at for examples, such as the apache2 port. Or maybe another distribution has already written such a patch for vis5d that we could use.
FYI, this problem only appears if the compiler you are using now is not the same compiler that was used to build your libtool. So if you do not see the error normally, you can simulate it by specifying an alternate configure.compiler.