Re: builing mono fails on 10.5.8
On 25/11/13 12:59 AM, Ryan Schmidt wrote: 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. Thanks. I have cleaned it, got a usable logfile, and filed a bug report now. Thomas ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: xorg-server as non-root
On Nov 24, 2013, at 16:12, Gino Van Hauwermeiren wrote: > I installed macports locally as non-root. (when I configured it I gave > ./configure these options : --with-applications-dir= > --with-no-root-privileges --with-shared-directory --with-install-user= username> > I can install most other ports without problem, not using sudo. SO this seems > to be ok. > > But when I install xorg-server I get this error: > MacPorts requires root privileges for this action > Error: Failed to install xinit > > ( I work on Mavericks OS X 10.9) > > My questions: > 1) can xinit (and thus xorg-server) be installed as non-root? If yes, what do > I do wrong? Is there somewhere more documentation about this? Doesn’t look like you’re doing anything wrong. The xinit portfile explicitly requests to be installed as root (it contains the line “install.asroot yes”). > 2) if this can't be done, can I simply install XQuartz instead of xorg-server? Yes. > And will all apps from macports needing X11 server also work? (this apps > having a dependency on xorg-server) No apps depend on xorg-server. xorg-server only provides X11.app, which would only be used by you, not by another port. ___ 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
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 Sun, Nov 24, 2013 at 6:11 PM, Thomas Ruedas 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 copy&paste 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 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 copy&paste 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 portbuil
xorg-server as non-root
Hi, I installed macports locally as non-root. (when I configured it I gave ./configure these options : --with-applications-dir= --with-no-root-privileges --with-shared-directory --with-install-user= I can install most other ports without problem, not using sudo. SO this seems to be ok. But when I install xorg-server I get this error: MacPorts requires root privileges for this action Error: Failed to install xinit ( I work on Mavericks OS X 10.9) My questions: 1) can xinit (and thus xorg-server) be installed as non-root? If yes, what do I do wrong? Is there somewhere more documentation about this? 2) if this can't be done, can I simply install XQuartz instead of xorg-server? And will all apps from macports needing X11 server also work? (this apps having a dependency on xorg-server) Thanks, Best regards, Gino ___ 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 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
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: Links - Graphics not enabled when compiling
On Sun, Nov 24, 2013 at 9:31 AM, Ádám Juhász wrote: > I might have messed up the terms/names. > > By the “virtual terminal” I was referring the interface that you can > access with ⌃⌥F1-6. That is not using X11, and I don’t have any clue how I > pulled it off or how I figured that it could be possible with Links, but it > didn’t worked out in the end. (I wanted to use that in > Oh, Linux framebuffer console. Even less portable than X11 mode; OS X hasn't given you (easy) direct access to the console since 10.6 or thenabouts and the API doesn't look anything like the Linux framebuffer. You also can't use it concurrently with graphics (no virtual console support). There might be support in the PureDarwin community if there still is one and it hasn't completely bitrotted. -- 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: Links - Graphics not enabled when compiling
I might have messed up the terms/names. By the “virtual terminal” I was referring the interface that you can access with ⌃⌥F1-6. That is not using X11, and I don’t have any clue how I pulled it off or how I figured that it could be possible with Links, but it didn’t worked out in the end. (I wanted to use that in case if I broke my X11 to still be able to browse the web relatively comfortably.) I could open a image viewer in those terminal, and before that once run my SDL program as root (which was a mistake since it still had a segmentation fault in it, and crashed my system). I also almost run Battle for Wesnoth in the ⌃⌥F1 terminal but it failed loading the mouse, which I didn’t bothered. But it’s all off-topic tough. From: Brandon Allbery Date: 2013. november 24., vasárnap 15:19 To: Ádám Juhász Cc: Jeff Friedman , MacPorts Users Subject: Re: Links - Graphics not enabled when compiling On Sun, Nov 24, 2013 at 9:11 AM, Ádám Juhász wrote: > If I remember right, when I tried to use graphics with Links I tried it on > openSUSE and on it’s virtual terminal (bypassing X11) with no success. However > this isn’t possible on a Mac anyways, because it does not have a virtual > terminal. I have no idea what you are trying to say here; OS X has functionally the same pty support as Linux. And you are not bypassing X11 if you are seeing graphics at all, you are *using* it; the X11 video driver needs to at least be told what area of the screen to not update itself (for things like OpenGL or v4l2 on Linux), or must be doing the update itself under control of the X11 server. -- 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: Links - Graphics not enabled when compiling
On Sun, Nov 24, 2013 at 9:11 AM, Ádám Juhász wrote: > If I remember right, when I tried to use graphics with Links I tried it on > openSUSE and on it’s virtual terminal (bypassing X11) with no success. > However this isn’t possible on a Mac anyways, because it does not have a > virtual terminal. I have no idea what you are trying to say here; OS X has functionally the same pty support as Linux. And you are not bypassing X11 if you are seeing graphics at all, you are *using* it; the X11 video driver needs to at least be told what area of the screen to not update itself (for things like OpenGL or v4l2 on Linux), or must be doing the update itself under control of the X11 server. -- 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: Links - Graphics not enabled when compiling
OK, Adam. I think I will leave things as they are for the time being. :) Jeff On Sun, Nov 24, 2013 at 2:11 PM, Ádám Juhász wrote: > If I remember right, when I tried to use graphics with Links I tried it on > openSUSE and on it’s virtual terminal (bypassing X11) with no success. > However this isn’t possible on a Mac anyways, because it does not have a > virtual terminal. > > On the other hand iTerm—as far as I know—does not support graphics beyond > font selection and more finer tweaking of it. > I’m sorry, I didn’t wanted to plant false hope, I just thought I share > this feature of iTerm, and also I believe it is a great Terminal emulator > and so it is worthwhile to be mentioned. > > The closest bet I could give is to use the X11 variant and run it with > XQuartz. > > From: Jeff Friedman > Date: 2013. november 24., vasárnap 14:32 > To: Ádám Juhász > Cc: MacPorts Users , Brandon Allbery > > Subject: Re: Links - Graphics not enabled when compiling > > Thanks, Juhasz. I installed iTerm2 and it works perfectly with the > mouse. > > Any ideas on how to compile with graphics support? > > Jeff. > > > On Sun, Nov 24, 2013 at 1:24 PM, Juhász Ádám wrote: > >> iTerm supports mouse input which is available ín the MacPorts. >> > > ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Links - Graphics not enabled when compiling
If I remember right, when I tried to use graphics with Links I tried it on openSUSE and on it¹s virtual terminal (bypassing X11) with no success. However this isn¹t possible on a Mac anyways, because it does not have a virtual terminal. On the other hand iTermas far as I knowdoes not support graphics beyond font selection and more finer tweaking of it. I¹m sorry, I didn¹t wanted to plant false hope, I just thought I share this feature of iTerm, and also I believe it is a great Terminal emulator and so it is worthwhile to be mentioned. The closest bet I could give is to use the X11 variant and run it with XQuartz. From: Jeff Friedman Date: 2013. november 24., vasárnap 14:32 To: Ádám Juhász Cc: MacPorts Users , Brandon Allbery Subject: Re: Links - Graphics not enabled when compiling Thanks, Juhasz. I installed iTerm2 and it works perfectly with the mouse. Any ideas on how to compile with graphics support? Jeff. On Sun, Nov 24, 2013 at 1:24 PM, Juhász Ádám wrote: > > iTerm supports mouse input which is available ín the MacPorts. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Links - Graphics not enabled when compiling
On Sun, Nov 24, 2013 at 8:32 AM, Jeff Friedman wrote: > Any ideas on how to compile with graphics support? > You would need an implementation which uses Core Graphics instead of X11 to draw graphics (none exists that I know of) *and* that the terminal exports a window handle to programs running in it (as xterm and several other X11 terminal emulators do, as $WINDOWID). Remember that X11.app/XQuartz.app cannot see native graphics windows at all, only X11 windows. -- 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: Links - Graphics not enabled when compiling
Thanks, Juhasz. I installed iTerm2 and it works perfectly with the mouse. Any ideas on how to compile with graphics support? Jeff. On Sun, Nov 24, 2013 at 1:24 PM, Juhász Ádám wrote: > iTerm supports mouse input which is available ín the MacPorts. > ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
Re: Links - Graphics not enabled when compiling
iTerm supports mouse input which is available ín the MacPorts. ___ macports-users mailing list macports-users@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-users
