Opened 14 years ago
Last modified 14 years ago
#26630 closed defect
db46 fails to build — at Version 1
Reported by: | ed.hawes@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.1 |
Keywords: | Cc: | ||
Port: | db46 |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
---> Computing dependencies for wine-devel ---> Dependencies to be installed: mesa xorg-libXfixes xorg-libX11 xorg-libxcb python26 db46 gdbm openssl sqlite3 xorg-libpthread-stubs xorg-xcb-proto xorg-util-macros xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto xorg-xtrans xorg-libXi xorg-libXext xorg-libXmu xorg-libXt xorg-libsm xorg-libice xorg-libXcomposite xorg-compositeproto xorg-libXcursor xorg-renderproto xrender xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto xorg-libXxf86vm xorg-xf86vidmodeproto ---> Building db46 Error: Target org.macports.build returned: shell command failed Log for db46 is at: /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_db46/main.log Error: The following dependencies failed to build: mesa xorg-libXfixes xorg-libX11 xorg-libxcb python26 db46 gdbm openssl sqlite3 xorg-libpthread-stubs xorg-xcb-proto xorg-util-macros xorg-xcmiscproto xorg-xextproto xorg-xf86bigfontproto xorg-xtrans xorg-libXi xorg-libXext xorg-libXmu xorg-libXt xorg-libsm xorg-libice xorg-libXcomposite xorg-compositeproto xorg-libXcursor xorg-renderproto xrender xorg-libXinerama xorg-xineramaproto xorg-libXrandr xorg-randrproto xorg-libXxf86vm xorg-xf86vidmodeproto Error: Status 1 encountered during processing.
Change History (1)
comment:1 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Port: | db46 added |
Summary: | Error: Target org.macports.build returned: shell command failed → db46 fails to build |
Note: See
TracTickets for help on using
tickets.
We'll have no idea what the problem is until you attach the main.log file, whose location should have been printed in the error message.