[MacPorts] #34564: vis5d: unable to infer tagged configuration (was: port vis5d returned: command execution failed)

MacPorts noreply at macports.org
Mon May 21 12:49:18 PDT 2012


#34564: vis5d: unable to infer tagged configuration
------------------------------+---------------------------------------------
 Reporter:  ykzhou@…          |       Owner:  takeshi@…           
     Type:  defect            |      Status:  new                 
 Priority:  Normal            |   Milestone:                      
Component:  ports             |     Version:  2.1.1               
 Keywords:                    |        Port:  vis5d               
------------------------------+---------------------------------------------
Changes (by ryandesign@…):

 * cc: ryandesign@… (added)
  * owner:  macports-tickets@… => takeshi@…
  * port:  => vis5d


Old description:

> --->  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

New description:

 {{{
 --->  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
 }}}

--

Comment:

 The actual relevant error from the log is:
 {{{
 unable to infer tagged configuration
 }}}

 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.

-- 
Ticket URL: <https://trac.macports.org/ticket/34564#comment:1>
MacPorts <http://www.macports.org/>
Ports system for Mac OS


More information about the macports-tickets mailing list