New Ticket     Tickets     Wiki     Browse Source     Timeline     Roadmap     Ticket Reports     Search

Ticket #31953 (closed defect: fixed)

Opened 20 months ago

Last modified 13 months ago

vis5d: unable to infer tagged configuration

Reported by: totofg@… Owned by: takeshi@…
Priority: Normal Milestone:
Component: ports Version: 2.0.3
Keywords: Cc: ryandesign@…, ykzhou@…
Port: vis5d

Description

I can not install vis5d, I have this log file. Can you help me?

Many thanks

Attachments

main.log (76.4 KB) - added by totofg@… 20 months ago.
.log

Change History

Changed 20 months ago by totofg@…

.log

comment:1 Changed 20 months ago by ryandesign@…

  • Cc ryandesign@… added
  • Owner changed from macports-tickets@… to takeshi@…
  • Port set to vis5d
  • Summary changed from installation of vis5d to 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 20 months ago by takeshi@…

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 13 months ago by ryandesign@…

  • 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 13 months ago by takeshi@…

  • Status changed from new to closed
  • Resolution set to fixed

Committed in r93770. I needed to force update libtool (see #34564).

Note: See TracTickets for help on using tickets.