Opened 13 years ago
Closed 12 years ago
#31953 closed defect (fixed)
vis5d: unable to infer tagged configuration
Reported by: | totofg@… | Owned by: | tenomoto (Takeshi Enomoto) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), ykzhou@… | |
Port: | vis5d |
Description
I can not install vis5d, I have this log file. Can you help me?
Many thanks
Attachments (1)
Change History (5)
Changed 13 years ago by totofg@…
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ryandesign@… added |
---|---|
Owner: | changed from macports-tickets@… to takeshi@… |
Port: | vis5d added |
Summary: | installation of vis5d → vis5d: unable to infer tagged configuration |
The relevant error in the log seems to be:
:info:build glibtool: compile: unable to infer tagged configuration :info:build glibtool: compile: unable to infer tagged configuration :info:build glibtool: compile: specify a tag with `--tag' :info:build glibtool: compile: specify a tag with `--tag'
We should be able to fix that; we've fixed this in other ports before, e.g. apache2: browser:trunk/dports/www/apache2/files/libtool-tag.diff?rev=86196
comment:2 Changed 13 years ago by tenomoto (Takeshi Enomoto)
I don't have problem on Snow Leopard. On the machines I have access, gcc-4.2 is chosen as default. In your case it appears that llvm-gcc-4.2 is chosen.
Ryan, where can I find the correspondence between Xcode version and the default value of configure.compiler (wiki page, source code)?
comment:3 Changed 12 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | ykzhou@… added |
---|
Has duplicate #34564.
Takeshi, information about the default compiler choices is documented in wiki:ProblemHotlist#compiler and in the code in browser:trunk/base/src/port1.0/portconfigure.tcl?rev=92588#L423, but that does not matter for the purposes of this error. What matters is whether the compiler being chosen to build a port now is the same compiler that was chosen to build libtool; when it's not, and a project is not using the --tag parameter when it invokes libtool, the "unable to infer tagged configuration" error results. The solution is to always use the --tag parameter when invoking libtool.
comment:4 Changed 12 years ago by tenomoto (Takeshi Enomoto)
Resolution: | → fixed |
---|---|
Status: | new → closed |
.log