Opened 13 years ago
Closed 13 years ago
#32612 closed defect (duplicate)
Openjade fails to build on OSX Lion 10.7.2
Reported by: | mamiano@… | Owned by: | drkp (Dan Ports) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.0.3 |
Keywords: | Cc: | ||
Port: | openjade |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
Tried with XCode 4.2 , i686-apple-darwin11-llvm-g++-4.2 (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build 2336.1.00)
Also tried -universal, and configure.compiler=apple-gcc-4.2 configure.cxx=g++-apple-4.2 , per suggestions of a Lion page on this site, and bug report fixes, without success.
This was against a clean install of MacPorts made today (Dec 20, 2011). Cleaning and a new install attempt gives:
EC_01: sudo /opt/local/bin/port install openjade ---> Computing dependencies for openjade ---> Fetching archive for openjade ---> Attempting to fetch openjade-1.3.2_3.darwin_11.x86_64.tbz2 from http://packages.macports.org/openjade ---> Building openjade Error: Target org.macports.build returned: shell command failed (see log for details) Log for openjade is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_textproc_openjade/openjade/main.log Error: Status 1 encountered during processing. To report a bug, see <http://guide.macports.org/#project.tickets>
Will attach the main.log.
Is there a combination of tools/settings that works under Lion for building openjade ?
Attachments (3)
Change History (6)
Changed 13 years ago by mamiano@…
comment:1 Changed 13 years ago by drkp (Dan Ports)
Owner: | changed from macports-tickets@… to dports@… |
---|---|
Port: | openjade added |
Status: | new → assigned |
This might be a duplicate of #31777 (although I'm not sure the error message is the same...)
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|
comment:3 Changed 13 years ago by drkp (Dan Ports)
Resolution: | → duplicate |
---|---|
Status: | assigned → closed |
Yes, let's call this a duplicate and track at #31777.
Note: See
TracTickets for help on using
tickets.
main.log