builing mono fails on 10.5.8
Hi, I am trying to build mono under OS 10.5.8 and get this rather useless error: --- Computing dependencies for mono --- Building mono Error: org.macports.build for port mono returned: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port mono failed I have tried to find some information about build failures but didn't get very far; I don't even know where to look for more detailed error messages, as the content of /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_mono/mono/main.log is also rather unconspicuous. Any ideas? Should I file a bug right away? Thomas ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: builing mono fails on 10.5.8
On Sun, Nov 24, 2013 at 1:17 PM, Thomas Ruedas trg...@gmail.com wrote: I have tried to find some information about build failures but didn't get very far; I don't even know where to look for more detailed error messages, as the content of /opt/local/var/macports/logs/_opt_local_var_macports_ sources_rsync.macports.org_release_ports_devel_mono/mono/main.log is also rather unconspicuous. Any ideas? Should I file a bug You might put that logfile somewhere where others can look at it (or if it's small enough, gzip it and attach it to email, but web/dropbox/etc. is better). -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: builing mono fails on 10.5.8
On 24/11/13 8:53 PM, Brandon Allbery wrote: You might put that logfile somewhere where others can look at it (or if it's small enough, gzip it and attach it to email, but web/dropbox/etc. is better). Sorry, I can't post it anywhere, so I'll just have to copypaste it below; so that's /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_mono/mono/main.log It's the only logfile I found that looked as if it had to do with it. Rather than using the macports release I had thought I wouldn't bother and install the packaged version provided by the developers, but the installer doesn't work (it begins to install and then claims it doesn't have permission to install in /). Anyway... version:1 :debug:main epoch: in tree: 0 installed: 0 :debug:main pkgconfig 0.28_0 exists in the ports tree :debug:main pkgconfig 0.28_0 is the latest installed :debug:main pkgconfig 0.28_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/pkgconfig :debug:main OS darwin/9.8.0 (Mac OS X 10.5) arch i386 :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf :debug:main Running callback portconfigure::add_automatic_compiler_dependencies :debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies :debug:main Running callback portbuild::add_automatic_buildsystem_dependencies :debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies :debug:main No need to upgrade! pkgconfig 0.28_0 = pkgconfig 0.28_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main libiconv 1.14_0 exists in the ports tree :debug:main libiconv 1.14_0 is the latest installed :debug:main libiconv 1.14_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/textproc/libiconv :debug:main OS darwin/9.8.0 (Mac OS X 10.5) arch i386 :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main Running callback portconfigure::add_automatic_compiler_dependencies :debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies :debug:main Running callback portbuild::add_automatic_buildsystem_dependencies :debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies :debug:main No need to upgrade! libiconv 1.14_0 = libiconv 1.14_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main gawk 4.1.0_0 exists in the ports tree :debug:main gawk 4.1.0_0 is the latest installed :debug:main gawk 4.1.0_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/gawk :debug:main OS darwin/9.8.0 (Mac OS X 10.5) arch i386 :debug:main adding the default universal variant :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf :debug:main Running callback portconfigure::add_automatic_compiler_dependencies :debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies :debug:main Running callback portbuild::add_automatic_buildsystem_dependencies :debug:main Finished running callback portbuild::add_automatic_buildsystem_dependencies :debug:main No need to upgrade! gawk 4.1.0_0 = gawk 4.1.0_0 :debug:main epoch: in tree: 0 installed: 0 :debug:main readline 6.2.000_0 exists in the ports tree :debug:main readline 6.2.000_0 is the latest installed :debug:main readline 6.2.000_0 is active :debug:main Merging existing variants '' into variants :debug:main new fully merged portvariants: :debug:main Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/devel/readline :debug:main OS darwin/9.8.0 (Mac OS X 10.5) arch i386 :debug:main Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf :debug:main universal variant already exists, so not adding the default one :debug:main Running callback portconfigure::add_automatic_compiler_dependencies :debug:main Finished running callback portconfigure::add_automatic_compiler_dependencies :debug:main Running callback portbuild::add_automatic_buildsystem_dependencies :debug:main Finished running callback
Re: builing mono fails on 10.5.8
On Sun, Nov 24, 2013 at 6:11 PM, Thomas Ruedas trg...@gmail.com wrote: On 24/11/13 8:53 PM, Brandon Allbery wrote: You might put that logfile somewhere where others can look at it (or if it's small enough, gzip it and attach it to email, but web/dropbox/etc. is better). Sorry, I can't post it anywhere, so I'll just have to copypaste it below; so that's /opt/local/var/macports/logs/_opt_local_var_macports_ sources_rsync.macports.org_release_ports_devel_mono/mono/main.log It's the only logfile I found that looked as if it had to do with it. That log shows a successful install from a prebuilt package, not a build failure. -- brandon s allbery kf8nh sine nomine associates allber...@gmail.com ballb...@sinenomine.net unix, openafs, kerberos, infrastructure, xmonadhttp://sinenomine.net ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: builing mono fails on 10.5.8
On 25/11/13 12:20 AM, Brandon Allbery wrote: That log shows a successful install from a prebuilt package, not a build failure. Exactly, that's why I don't understand why the stdout output of the macports run tells me that the build fails. Below I post a bit more of the stdout output. The only thing I notice is that the xextproto stuff doesn't appear in the logfile, the last thing being logged there is the libpixman build, which seems to have been successful. Any other files I should look for? --- Activating libpixman @0.32.4_0 --- Cleaning libpixman --- Fetching distfiles for xorg-xextproto --- Attempting to fetch xextproto-7.2.99.901.tar.bz2 from http://lil.fr.distfiles.macports.org/xorg-xextproto --- Verifying checksums for xorg-xextproto --- Extracting xorg-xextproto --- Configuring xorg-xextproto --- Building xorg-xextproto --- Staging xorg-xextproto into destroot --- Installing xorg-xextproto @7.2.99.901_0 --- Cleaning xorg-xextproto --- Deactivating xorg-xextproto @7.2.1_0 --- Cleaning xorg-xextproto --- Activating xorg-xextproto @7.2.99.901_0 --- Cleaning xorg-xextproto --- Computing dependencies for mono --- Building mono Error: org.macports.build for port mono returned: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: Processing of port mono failed ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: builing mono fails on 10.5.8
On Nov 24, 2013, at 17:30, Thomas Ruedas wrote: On 25/11/13 12:20 AM, Brandon Allbery wrote: That log shows a successful install from a prebuilt package, not a build failure. Exactly, that's why I don't understand why the stdout output of the macports run tells me that the build fails. The build of mono did fail. The log showed a successful libpixman install. There is a bug in MacPorts base where sometimes the wrong port’s log gets written to the file: https://trac.macports.org/ticket/37093 I’d love to get that fixed but haven’t a clue how. Until it’s fixed, you’ll have to clean mono and try again to get a new log for mono. Then file a ticket in the issue tracker and attach the (possibly compressed) log, assuming no ticket for this problem already exists. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
