Re: dbus issue
Hi, At 11:27 -0500 on 2008-4-1 Joe Schnide wrote: I completely deleted macports, did an install from scratch, installed all the deluge port dependencies and still get the error below on intel-based macs. The problem is not happening on my g4 macs, just on the intel-based macs. Is there more information that needs to be provided on this issue? Happened to me too (Intel Mac) and the solution turns out to be trivial: a `mkdir /opt/local/etc/dbus-1/session.d' does it nicely. While this is a workaround and not a port-based solution, it is too simple and too straightforward to require a second thought (in my opinion anyway) and is trivial to implement in the dbus port. Thanks Joe At 1:46 PM -0500 3/26/08, Joe Schnide wrote: Hello, Recently did the selfupdate and update installed ports. Now when I try to run deluge, X11 starts fine but I get the error: Failed to start message bus: Failed to read directory /opt/local/etc/dbus-1/session.d: No such file or directory EOF in dbus-launch reading address from bus daemon Cheers, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
GNOME launch failure
Hi, I am having a puzzling experience with the following setting: GNOME desktop with enlightenment as window manager (set using the WINDOW_MANAGER environment variable from within .xinitrc). The experience goes as follows: Everything works as advertised until I upgrade some GNOME components, namely gtk2 (from 2.12.1_0 to 2.12.2_0+x11), cairo (from 1.4.10_0 to 1.4.12_0), and glib2 (from 2.14.3_0 to 2.14.4_1). After the upgrade the GNOME desktop refuses to show up (there is a delay, then the GNOME splash screen appears briefly together with a dialogue that does not show anything, then nothing else happens). Nothing shows in the logs. A ps shows gnome-session, bonobo-activation, gconf-2, gnome-vfs, and e16. What I have done to attempt to pinpoint the problem: e16 alone works fine as desktop manager; changing the GNOME window manager from e16 to metacity or even quartz-wm does not change anything; deactivating the offending packages one by one and activating their old versions does not fix anything (unless all three are reverted to the old versions--when this happens everything begins to work all of a sudden). I am almost sure (given past experiences) that I have to rebuild some dependencies of these packages, but I cannot figure out which ones. Any hint is appreciated. Many thanks in advance, Stefan P.S. Does anybody have any experience with GNOME+enlightenment+firefox-x11 working (or not) under 10.5? I really want to upgrade but this is my production machine and I am afraid of potential issues. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: 64 bits 32 bits ports
Hi, At 17:12 +0100 on 2007-12-14 Markus Weissmann wrote: we're currently working on this; I suppose we'll make the universal builds 4-way universal (ppc, ppc64, i386, x86_64) in some future release. It would also make sense to allow for x86_64 versions only, no? I am personally not interested in universal versions, but I am mildly interested in having a 64-bit environment. Cheers, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gnome compilation problems
At 20:01 -0500 on 2007-10-24 Ryan Schmidt wrote: Nobody forces you to upgrade any port, or any other software on your machine, for that matter. You can choose to upgrade, or not. Yes it does: An automatic `port upgrade outdated' will upgrade everything. Should I then sit down every time and decide what I want to upgrade and what I don't? On what should I base my decision? There is no keyword to help me out. I was under the impression that Macports is a production system, so it should upgrade to a usable configuration automatically--if not all the time at least most of the time. That being said, new versions should be better than old ones. Precisely. GNOME in particular is consistently problematic at first when it is upgraded and it should not be. If you find problems with new versions, please file tickets. Of course, but in the meantime I would like to keep a usable installation. If I have a test machine (which I don't) I would be more than happy to live on the edge and report bugs; however whenever I am upgrading my production machine I like to have things mostly working--the DE being one important piece, I like to have it working all the time. How would splitting the ports tree into stable and unstable help? Specifically, if we declare our current ports tree unstable, by what mechanism does software get to the stable branch? Who decides what is stable and when? We currently have no information about how many of our ports even build currently, and of course that varies by OS and platform. That's an excellent point. I guess the maintainer could decide on the matter. What I would like to see is actually versioning (Gentoo style), tagged with a stable/unstable keywords. If I want to keep a stable system, I can keep within the stable versions; if I want to live on the edge, I can go to development; if I am tired of living on the edge I can reset my keyword and re-upgrade (port upgrade will then need to be capable of downgrading too); if I want to live in the edge only for a portion of the tree, then I should be able to unmask ports individually. Right now I don't even know what I did when the system broke--there are no longs so I cannot go back in time even manually unless I write down the list of ports being upgraded before I issue the upgrade command. But then I might be the only one who could use this, so do not take my comments more seriously than they are worth. Cheers, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gnome compilation problems
Hi, Daniel J. Luke wrote: Macports is run entirely by volunteers, none of whom get paid to do it. I know, of course; I am myself involved in free software. If you want some new functionality, the best way to get it is to work on it and offer it to the community. As soon as I have the time to learn TCL and the innards of the Macports system (I am working on it). Still, I hope you don't mind if I comment on features and whatnot--if only developers can comment on these then please say so. By the way, if I offended somebody I do apologize, as this was not my intention whatsoever. If we had a test-build system of some sort set up, it would be possible to at least tag ports as building successfully or not (hint hint). Unfortunately I have only one Mac OS machine, which is not permanently on line (it is my day to day laptop). You could upgrade with -dv and redirect the output to a file so you could go back and look at it later. That's an excellent suggestion, thank you very much. Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gnome compilation problems
Hi, Barry Schiffman wrote: 1. gedit: I get down to compiling gedit-languages-manager.o and the following is reported: gedit-languages-manager.c:115: error: conflicting types for 'gdk_color_to_string' /opt/local/include/gtk-2.0/gdk/gdkcolor.h:137: error: previous declaration of 'gdk_color_to_string' was here I get this one too, no idea how to go around. 2. gnome-applets -- an undeclared variable on 'make all' -- what's missing? The volume control applet cannot be compiled for some reason (did not have time to actually find the reason), I solved this temporarily by not compiling the said applet (I changed into the working directory, I replaced the makefile of the offending applet with a dummy one, and I re-issued the install command which completed successfully). 3. seahorse fails compiling seahorse-secure-memory.o I have seahorse @1.0_1 installed but I have not had a chance to upgrade this one. 4. This one may be covered by ticket #10880 gnome-desktop-suite: gedit fails to compile (see below), and I get this: Error: The following dependencies failed to build: gedit gnome-applets seahorse This is caused by the above three failures. What amazes me is that every time GNOME is being updated a whole bunch of problems appear. For one thing dependencies need to be recompiled quite often (doable by hand only!). Some compilation errors are also invariably present. I am wondering why do I need to upgrade a stable GNOME installation to what always turns out to be an unstable GNOME, not ready for prime time. I would not do that personally, except that the port system asks me to do so. At least in this respect a branching into stable and development is sorely needed, as is a dependency rebuild utility. Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: gnome-session launch errors
paul beard wrote: On 10/17/07, Stefan Bruda [EMAIL PROTECTED] wrote: Hi, paul beard wrote: Looks like something needs updating? Link (dyld) error: Library not loaded: /opt/local/lib/libgnomecanvas-2.0.dylib Referenced from: /opt/local/lib/libgnome-desktop-2.2.dylib Reason: Incompatible library version: libgnome-desktop-2.2.dylib requires version 2001.0.0 or later, but libgnomecanvas-2.0.dylib provides version 1999.0.0 When I see an incompatible version like this I first look for which port owns the not loaded library: godel:~ port provides /opt/local/lib/libgnomecanvas-2.0.dylib /opt/local/lib/libgnomecanvas-2.0.dylib is provided by: libgnomecanvas and then I rebuild the respective package (libgnomecanvas in this case). Yeah, I did that. Didn't work. That's why I was curious about the problem. Oops, I am sorry, my mistake, what need to be rebuild is the dependent, not the dependency: godel:~ port provides /opt/local/lib/libgnome-desktop-2.2.dylib /opt/local/lib/libgnome-desktop-2.2.dylib is provided by: gnome-desktop Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Firefox-x11 and file chooser dialogue
Hi, My firefox-x11 (2.0.0.7, on an Macbook Pro Core 2 Duo, Mac OS X 10.4.10) refuses to open any file chooser dialogues (noted in the print to file dialogue and Browse... buttons on various Web pages). Is this a known issue (and if so how do I fix it) or should I file a bug report? Many thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Printing and plugins for firefox-x11
Hi, Stefan Bruda wrote: Now, is there any trick I need to do in order to be capable to print from the application? I am getting only a default printer which does not seem to produce any print job by default. Just to update myself, It looks like printing works after all, though only the default printer shows in the drop-down list (other printers can be set up using Properties and then the -P option or lpr). It would be nice however to be able to choose a printer from the drop-down list. Is this a good cause for a bug report? Secondly, is there any way to install plugins (such as media or flash plugins) under firefox-x11? I tried to link to the ones on the MacOS side (not sure if it works at all though), but I cannot find them. So nobody tried to set up plugins?? Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Printing and plugins for firefox-x11
Hi, Finally Firefox works under X11 on my machine (Macbook Pro) so I could not be happier. Thank you so much to whomever is responsible for this. Now, is there any trick I need to do in order to be capable to print from the application? I am getting only a default printer which does not seem to produce any print job by default. Secondly, is there any way to install plugins (such as media or flash plugins) under firefox-x11? I tried to link to the ones on the MacOS side (not sure if it works at all though), but I cannot find them. Any pointer on the matter is appreciated. Many thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
poppler and xpdf
Hi, Poppler and xpdf conflict with each other in some executable names. godel:~ port activate poppler @0.6_0 --- Activating poppler 0.6_0 Error: port activate failed: Image error: /opt/local/bin/pdffonts is being used by the active xpdf port. Please deactivate this port first, or use the -f flag to force the activation. However, evince and gimp2 depend on poppler (so it needs to be there) and I use xpdf all the time (so I need it). How does one get around this problem? Many thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: poppler and xpdf
Yves de Champlain wrote: Poppler and xpdf conflict with each other in some executable names. godel:~ port activate poppler @0.6_0 --- Activating poppler 0.6_0 Error: port activate failed: Image error: /opt/local/bin/pdffonts is being used by the active xpdf port. Please deactivate this port first, or use the -f flag to force the activation. However, evince and gimp2 depend on poppler (so it needs to be there) and I use xpdf all the time (so I need it). How does one get around this problem? xpdf has a variant for this case port install xpdf +with_poppler Thank you very much, that does it nicely. Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Getting new Gutenprint 5.1.3 to Macports
Hi, Thorsten Zoerner wrote: An idea from some forum was to upgrade Gutenprint from 5.0.1 to 5.1.3. Okay, but this version does not seem to be available for Macports yet. Or is it? Have you tried using Print with Gutenprint instead of Print? Works very well for me with gutenprint-5.0.1: godel:~ port list gutenprint gutenprint @5.0.1 print/gutenprint godel:~ port list gimp2 gimp2 @2.4.0-rc1 graphics/gimp2 Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: xfig crashes
Hi, Jörg Frauendiener wrote: I installed xfig-3.2.5_1 via macports and it crashes when I click on a menu button (File,Edit,View,...). Pulling up a dialog box by a keyboard sequence (e.g. M-o to open) seems to work OK, though. Any suggestions? I just came across this thread and was wondering whether the issue concerning Xaw3d has been resolved. Since I am having the same problem as described above it would be nice if there was a clean solution. I am aware of the workaround given in other threads. Clearly, this cannot be considered a 'solution'? By clean solution do you mean the #define XAW3D1_5E thing? I tried it once and it did not work for me. The only solution I found so far is not to use the Xaw3D toolkit. This works well; true, I loose some eye candy but not much and xfig is an ugly (and useful) thing anyway--that's why I like it in the first place. Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Gimp and gimp-print (and other Gimp issues)
Hi, Yves de Champlain wrote: Le 07-09-16 à 22:54, Stefan Bruda a écrit : gimp-print is deprecated. gutenprint is the new version (and new name) of gimp-print, so you should uninstall it. I kind of figured it out for myself by now. The Print menu however should cease to offer a gimp-print-based entry in this case. The print plugin you see is gimp's own, not gimp-print's. Agreed. It does not work either, so it should be either fixed or eliminated. libopenjpeg-2.1.2.0.dylib (compatibility version 0.0.0, current version 0.0.0) The problem is here. My gues is that you have to upgrade openjpeg to revision 1 which fixed this exact problem. This alone did not work (did it a while ago), but rebuilding gimp-jp2 after the openjpeg upgrade does fix the issue. Seeing the other (apparently similar) gettext issue floating around makes me believe that Macports needs an equivalent to Gentoo's revdep-rebuild quite badly. Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Gimp and gimp-print (and other Gimp issues)
Hi, Yves de Champlain wrote: First of all, thanks for your comments. Gimp will soon hit 2.4.0 and if anything is wrong, now is the time to find it. Well, thank *you* for getting back to me. Gimp is one of my daily routine so I appreciate when it works right (and when it does not I appreciate when somebody takes the trouble to find out what is wrong). At 22:10 -0400 on 2007-9-13 Yves de Champlain wrote: The latest Gimp (2.4.1) does not seem to go along well with gimp- print. Whenever I attempt to print something I get a bus error in /opt/local/lib/gimp/2.0/plug-ins/print. Last time I checked (with Gimp 2.2.17) printing was no problem at all. Is there any trick I am missing? How does one print? Could it be that this all happens because the newest Gimp port if for a release candidate? I'm not sure about this. Do you have gimp-print installed ? Yes. Works well with gimp 2.2.17. gimp-print is deprecated. gutenprint is the new version (and new name) of gimp-print, so you should uninstall it. I kind of figured it out for myself by now. The Print menu however should cease to offer a gimp-print-based entry in this case. Now that I am looking at it, I also note that the jp2 plugin has problems: dyld: Library not loaded: libopenjpeg-2.1.2.0.dylib Referenced from: /opt/local/lib/gimp/2.0/plug-ins/jp2 Reason: image not found although libopenjpeg-2.1.2.0.dylib does exist: godel:~ ll /opt/local/lib/libopenjpeg-2.1.2.0.dylib -rwxr-xr-x 2 root wheel 130592 Aug 11 12:59 /opt/local/lib/ libopenjpeg-2.1.2.0.dylib* This looks like a problem I thought was fixed ... can you send me the output of otool -L /opt/local/lib/gimp/2.0/plug-ins/jp2 Sure thing, here it is. /opt/local/lib/gimp/2.0/plug-ins/jp2: /opt/local/lib/libgimpui-2.0.0.dylib (compatibility version 201.0.0, current version 201.17.0) /opt/local/lib/libgimpwidgets-2.0.0.dylib (compatibility version 201.0.0, current version 201.17.0) /opt/local/lib/libgimpmodule-2.0.0.dylib (compatibility version 201.0.0, current version 201.17.0) /opt/local/lib/libgimp-2.0.0.dylib (compatibility version 201.0.0, current version 201.17.0) /opt/local/lib/libgimpmath-2.0.0.dylib (compatibility version 201.0.0, current version 201.17.0) /opt/local/lib/libgimpcolor-2.0.0.dylib (compatibility version 201.0.0, current version 201.17.0) /opt/local/lib/libgimpbase-2.0.0.dylib (compatibility version 201.0.0, current version 201.17.0) /opt/local/lib/libgtk-x11-2.0.0.dylib (compatibility version 1001.0.0, current version 1001.13.0) /opt/local/lib/libgdk-x11-2.0.0.dylib (compatibility version 1001.0.0, current version 1001.13.0) /opt/local/lib/libatk-1.0.0.dylib (compatibility version 1810.0.0, current version 1810.1.0) /opt/local/lib/libgdk_pixbuf-2.0.0.dylib (compatibility version 1001.0.0, current version 1001.13.0) /opt/local/lib/libtiff.3.dylib (compatibility version 12.0.0, current version 12.2.0) /opt/local/lib/libjpeg.62.dylib (compatibility version 63.0.0, current version 63.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.9) /opt/local/lib/libpangocairo-1.0.0.dylib (compatibility version 1601.0.0, current version 1601.4.0) /opt/local/lib/libpango-1.0.0.dylib (compatibility version 1601.0.0, current version 1601.4.0) /opt/local/lib/libcairo.2.dylib (compatibility version 14.0.0, current version 14.5.0) /usr/X11R6/lib/libSM.6.dylib (compatibility version 6.0.0, current version 6.0.0) /usr/X11R6/lib/libICE.6.dylib (compatibility version 6.3.0, current version 6.3.0) /opt/local/lib/libgobject-2.0.0.dylib (compatibility version 1201.0.0, current version 1201.13.0) /opt/local/lib/libgmodule-2.0.0.dylib (compatibility version 1201.0.0, current version 1201.13.0) /opt/local/lib/libglib-2.0.0.dylib (compatibility version 1201.0.0, current version 1201.13.0) /opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.1.0) /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /opt/local/lib/libfreetype.6.dylib (compatibility version 10.0.0, current version 10.16.0) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /opt/local/lib/libfontconfig.1.dylib (compatibility version 4.0.0, current version 4.0.0) /opt/local/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0) /opt/local/lib/libpng12.0.dylib (compatibility version 19.0.0, current version 19.0.0) /opt/local/lib/libXrender.1.dylib (compatibility version 5.0.0, current version 5.0.0) /usr/X11R6/lib/libX11.6.dylib (compatibility version 6.2.0, current version 6.2.0) libopenjpeg-2.1.2.0.dylib (compatibility version 0.0.0, current version 0.0.0) Finally, I also note that my
Re: Gimp and gimp-print (and other Gimp issues)
Hi, At 22:10 -0400 on 2007-9-13 Yves de Champlain wrote: The latest Gimp (2.4.1) does not seem to go along well with gimp- print. Whenever I attempt to print something I get a bus error in /opt/local/lib/gimp/2.0/plug-ins/print. Last time I checked (with Gimp 2.2.17) printing was no problem at all. Is there any trick I am missing? How does one print? Could it be that this all happens because the newest Gimp port if for a release candidate? I'm not sure about this. Do you have gimp-print installed ? Yes. Works well with gimp 2.2.17. The print plugin is part of gimp itself. It would be easier if I had some output of this. I am not sure what kind of output to provide. The print plugin just segfaults: /opt/local/lib/gimp/2.0/plug-ins/print: fatal error: Bus error In the logs I get a somewhat longish description of what looks like a good ol' segmentation violation (log included below). I have rebuilt gimp-print by the way, just to make sure that there is no library confusion. Now that I am looking at it, I also note that the jp2 plugin has problems: dyld: Library not loaded: libopenjpeg-2.1.2.0.dylib Referenced from: /opt/local/lib/gimp/2.0/plug-ins/jp2 Reason: image not found although libopenjpeg-2.1.2.0.dylib does exist: godel:~ ll /opt/local/lib/libopenjpeg-2.1.2.0.dylib -rwxr-xr-x 2 root wheel 130592 Aug 11 12:59 /opt/local/lib/libopenjpeg-2.1.2.0.dylib* Now that I further look at it, I note too that I can open the dialog of Print with Gutenprint (haven't tried to actually print with it yet but it will probably work). Finally, I also note that my Python-fu menu is gone (although gimp2 is indeed compiled with +python) and Script-fu contains few entries (only the four plugins that I added manually, the stock ones are gone). Is this normal? In any event, thank you for taking the time to look into it. Here is the crash log for the print plugin: Host Name: godel Date/Time: 2007-09-14 09:09:31.496 -0400 OS Version: 10.4.10 (Build 8R2218) Report Version: 4 Command: print Path:/opt/local/lib/gimp/2.0/plug-ins/print Parent: gimp-2.4 [20315] Version: ??? (???) PID:20331 Thread: 0 Exception: EXC_BAD_ACCESS (0x0001) Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x000c Thread 0 Crashed: 0 libgtk-x11-2.0.0.dylib 0x01157303 gtk_page_setup_get_paper_width + 9 1 libgtk-x11-2.0.0.dylib 0x011573b7 gtk_page_setup_get_page_width + 25 2 print 0x2ea6 print_size_info_get_page_dimensions + 102 3 print 0x2ef0 gimp_size_info_get_max_offsets + 42 4 print 0x2f6f print_size_info_update_offsets + 31 5 print 0x3d5a print_offset_frame + 2500 6 print 0x5a1f print_page_layout_gui + 3765 7 libgtk-x11-2.0.0.dylib 0x01127d8a _gtk_marshal_OBJECT__VOID + 207 8 libgobject-2.0.0.dylib 0x006ac70b g_closure_invoke + 524 9 libgobject-2.0.0.dylib 0x006bda29 signal_emit_unlocked_R + 3391 10 libgobject-2.0.0.dylib 0x006be963 g_signal_emit_valist + 1175 11 libgobject-2.0.0.dylib 0x006c24eb g_signal_emit_by_name + 238 12 libgtk-x11-2.0.0.dylib 0x012b8ec5 get_print_dialog + 190 13 libgtk-x11-2.0.0.dylib 0x012b981a _gtk_print_operation_platform_backend_run_dialog + 90 14 libgtk-x11-2.0.0.dylib 0x01167364 gtk_print_operation_run + 646 15 print 0x280e run + 840 16 libgimp-2.0.0.dylib 0x000408e8 gimp_main + 1774 17 print 0x2402 main + 40 18 print 0x23be _start + 216 19 print 0x22e5 start + 41 Thread 0 crashed with X86 Thread State (32-bit): eax: 0x ebx: 0x2ed4 ecx: 0xbfffe9a0 edx: 0x02115f50 edi: 0x esi: 0x80a0 ebp: 0xbfffe918 esp: 0xbfffe8f0 ss: 0x001f efl: 0x00010286 eip: 0x01157303 cs: 0x0017 ds: 0x001f es: 0x001f fs: 0x gs: 0x0037 Binary Images Description: 0x1000 - 0x7fff print /opt/local/lib/gimp/2.0/plug-ins/print 0x1f000 -0x31fff libgimpui-2.0.0.dylib /opt/local/lib/libgimpui-2.0.0.dylib 0x3e000 -0x5efff libgimp-2.0.0.dylib /opt/local/lib/libgimp-2.0.0.dylib 0x71000 -0x72fff libgimpmodule-2.0.0.dylib /opt/local/lib/libgimpmodule-2.0.0.dylib 0x77000 -0x7efff libgimpconfig-2.0.0.dylib /opt/local/lib/libgimpconfig-2.0.0.dylib 0x85000 -0x87fff libgimpmath-2.0.0.dylib /opt/local/lib/libgimpmath-2.0.0.dylib 0x8c000 -0x93fff libgimpcolor-2.0.0.dylib /opt/local/lib/libgimpcolor-2.0.0.dylib 0x99000 -0xa4fff libgimpbase-2.0.0.dylib /opt/local/lib/libgimpbase-2.0.0.dylib 0xaf000 -0xc7fff libatk-1.0.0.dylib /opt/local/lib/libatk-1.0.0.dylib 0xd5000 -0xd9fff libpangocairo-1.0.0.dylib
Gimp and gimp-print
Hi, The latest Gimp (2.4.1) does not seem to go along well with gimp-print. Whenever I attempt to print something I get a bus error in /opt/local/lib/gimp/2.0/plug-ins/print. Last time I checked (with Gimp 2.2.17) printing was no problem at all. Is there any trick I am missing? How does one print? Could it be that this all happens because the newest Gimp port if for a release candidate? Thanks in advance, Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: X issues
Hi, Keith J. Schultz wrote: What version of the X11 App are you using. do you have the latest update installed. Mac OS X 10.4.10 (Intel Macbook Pro C2D), X11 1.1.3, Xcode 2.4, all up to date according to Apple's Software Update. I have a Powerbook G4, X11 1.1.3, gnome and things work for me. Seems to be the same here (except that I am on an Intel box). GNOME works mostly fine, with some glitches though as detailed earlier. What WM are you using? What does your .xinitrc look like? Are you using the quarz-wm in proxy mode? Stereo turned on? Yes, I am using quarz-wm in proxy mode. I am not sure what you mean by stereo being turned on. .xinitrc looks like this: source ~/.profile export XDG_DATA_DIRS=/opt/local/share export XDG_DATA_HOME=/opt/local/share export XDG_CONFIG_DIRS=/opt/local/etc/xdg quartz-wm --only-proxy e16 gkrellm esd -noterminate -nobeeps exec dbus-launch gnome-session Thanks again, Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
X issues
Hi, I am having some minor problems with Apple-supplied X, in that transitory effects (I am not sure how to call them, but they include the save progress bar in Openoffice or the window outlines in technical or box window movement in E16) do not appear. This becomes aggravating when doing image rotation with the Gimp, when the grid lines do not show up. In (probably) the same line or thought, the pager in E16 looks good, except for the desktop currently in front, which shows full white in the pager. In some other minor annoyance, as soon as I use a window manager other than Apple's (tested with E16 and Metacity), I can no longer bring X windows in front of Aqua windows. I would use the Apple WM, except that then I cannnot seem to persuade the windows to appear in GNOME's window list (they get minimized in the dock instead, and although they do appear in the window list when unminimized, one cannot interact with them from there). In all, here are my questions: Is there any possibility to convince those transitory effects I was mentioning to appear? I believe that this is an X issue, and I also notice that an XFree86 port is available. Has anybody tried it, and is it better (at least in this respect) than Apple's X server? Is replacing the X server even recommended? If so, are there any caveats or special procedures on the matter? What WM do you guys use? I really like E16, but I would switch to something else if I can convince X windows to live in peace with Aqua windows (but I would also like to use the GNOME window list). Thank you in advance for any information. Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: xfig crashes
Hi, Jonathan Stickel wrote: Searching the list is always useful, as this has just been discussed, see http://lists.macosforge.org/pipermail/macports-users/2007-July/004596.html http://lists.macosforge.org/pipermail/macports-users/2007-July/004620.html Fair enough. Google searching didn't show anything, but next time I'll search the macports bugs and the mailing list. Is the mailing list searchable somewhere, or do I need to look through the archives? Umm, it actually sounded harsher than I meant, sorry. As for searching, I do so googling for something like 'xfig site:lists.macosforge.org' (as I am not aware of any other way of doing it). I have been using gentoo for a long time, and I am stilling getting used to macports. In gentoo, if something like this popped up, the port would be removed in favor of an earlier version that worked; that is until the port was fixed. I feel for you, I come from Gentoo as well and I miss portage a lot on this machine of mine. Is there an earlier version readily available? I'm guessing not by the thread referred to above. In that case, what is a typical time frame for a bug like this to be fixed? There are no multiple versions for a port, unless a previous version has been installed (case in which it remains installed until you explicitly uninstall it). The xfig issue is a long standing one to boot. I can only guess that people do not use xfig (wich is a pitty if you ask me). Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: liboil build failure
Ryan Schmidt wrote: Err, sorry, I meant the other way around (the upgrade is from 0.3.10_2 to 0.3.12_0). Then I'm not sure. Perhaps try deactivating the 0.3.10_2 version first, then install the 0.3.12_0 version. Thank you for the suggestion, but I must confess I did not expect it to work (the problem is undefined symbols during linking) and indeed it does not. The same issue is by the way signalled in another recent post http://lists.macosforge.org/pipermail/macports-users/2007-July/004616.html. Anybody knows at least where are composite_in_* symbold supposed to come from? Thanks again, Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: failed to build ports ocaml, xfig
Hi, Dimitri Hendriks wrote: Thanks a lot for you help so far. Unfortunately, the commands you give seem not work for me. Possibly, I have overlooked something. It's me who I overlooked two things actually. The first one is that all the commands I mentioned shoudl be given as root. So you are correct in putting the sudos in front. First, a question: if I do sudo port -v extract xfig I get no message or whatsoever, just a new prompt; is that OK? That's probably the second thing I forgot to mention, you need to uninstall and clean the xfig first, and thisis probably the reason that the above command does nothing. So try a sudo port uninstall xfig sudo port clean xfig I hope it works now. Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: failed to build ports ocaml, xfig
Ryan Schmidt wrote: I tried this and xfig then installs fine, but I now get the same problem as reported earlier: http://lists.macosforge.org/pipermail/macports-users/2007-April/ 002746.html and: http://lists.macosforge.org/pipermail/macports-users/2007-June/ 003917.html In the same thread it is suggested to build xfig without Xaw3d. Is this a good idea? Yes, or at least works for me. If so, can someone tell me how to do that or add some explanantion to: You should find out which configure flag for building xfig is required to disable the use of Xaw3d (is xfig using configure or still imake/xmkmf?) and add it to configure-args.append. There does not seem to be possible to use the portfile for this purpose, though a patch could be written and applied by the portfile. Being lazy and lacking time, what I did instead is: port -v extract xfig cd `port dir xfig`/work/xfig.3.2.5/ vi Imakefile # search for: #define XAW3D # comment (XCOMM) the just found line port -v install xfig I also edited the port: vi `port file xfig` and I eliminated the dependency of port:Xaw3d. This is not theoretically necessary but is correct given that I just eliminated the actual Xaw3d dependency. BY the way, did anybody notice that upgrading Xaw3d to 1.5E_1 breaks quite badly other things such as xemacs and gv? Any suggestions on what could be done about this one? This sounds like a matter for the maintainer of the xfig port, whom I'm Cc'ing on this email. I believe that Xaw3D is the overall culprit, so the dependency should be removed (and the Imakefile patched accordingly) until the issue is fixed. Cheers, Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
ffmpeg build failure
Hi, I am trying to upgrade ffmpeg from 0.4.9-pre1_1 to 0.4.9-pre1_2 and I am getting in return: make -C libavformat all gcc -dynamiclib -Wl,-single_module -Wl,-install_name,/opt/local/lib/libavformat.dylib,-current_version,51.1.0,-compatibility_version,51.1.0 -Wl,-read_only_relocs,suppress -Wl,-dynamic,-search_paths_first -L/opt/local/lib -o libavformat.51.dylib utils.o cutils.o os_support.o allformats.o framehook.o avio.o aviobuf.o raw.o adtsenc.o aiff.o riff.o amr.o apc.o asf.o asf-enc.o au.o avidec.o avienc.o avs.o vocdec.o voc.o bethsoftvid.o c93.o crc.o daud.o dsicin.o dv.o dvenc.o dxa.o electronicarts.o ffm.o flic.o flvdec.o flvenc.o 4xm.o gif.o gifdec.o gxf.o gxfenc.o idcin.o img2.o ipmovie.o matroska.o mm.o mmf.o mov.o isom.o movenc.o mp3.o mpc.o mpeg.o mpegts.o mpegtsenc.o mpjpeg.o mtv.o mxf.o nsvdec.o nutdec.o nuv.o ogg2.o oggparsevorbis.o oggparsetheora.o oggparseflac.o oggparseogm.o ogg.o rtsp.o rm.o idroq.o rtp.o rtp_h264.o segafilm.o smacker.o sol.o psxstr.o swf.o thp.o tiertexseq.o tta.o txd.o sierravmd.o vocenc.o wav.o wc3movie.o westwood.o wv.o yuv4mpeg.o file.o http.o rtpproto.o tcp.o udp.o -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavutil -lavutil -lavcodec -L/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_multimedia_ffmpeg/work/trunk/libavcodec -lz -logg -lxvidcore -lx264 -lfaac ld: Undefined symbols: _ff_mpa_decode_header /usr/bin/libtool: internal link edit command failed make[1]: *** [libavformat.51.dylib] Error 1 make: *** [lib] Error 2 Any idea what is the cause of this? Thanks in advance, Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Gkrellm 2.3.0_0's mailcheck does not like SSL
Hi, I have been using for a while now gkrellm 2.2.10_0 and I just upgraded to 2.3.0_0. Everything seems to work fine, except for mailcheck. In 2.3.0 for some reason it starts to dislike imap-ssl connections. When such a thing is present, mailcheck fails to retrieve anything from the server. Note that imap-ssl worked fine in 2.2.10 and works fine with my email client. I don't even know how to diagnose it any further, so any pointer is indeed appreciated (especially given that I access all my mailboxes over imap-ssl). Many thanks in advance, Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: error building python24 on mac os x
Hi, First of all, sorry for the delay in responding (I have been away from my machine). paul beard wrote: On May 10, 2007, at 2:11 PM, Stefan Bruda wrote: Somebody wants a python.exe... make a link to python in the same directory and see what that gets you. I think that resolves it, though why it happens in the first place is a mystery. This fixes it alright. It might be that the build process gets confused by the filesystem (I am using case-sensitive HFS). Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: Firefox 2.0?
Ryan Schmidt wrote: Why wouldn't we want to just update firefox-x11 to 2.0.0.3? I would personally not mind it. Problem is, the current firefox-x11 does not work (at least on Intel Macs, it is an issue somebody is working on as far as I know) and the same goes for 2.0.0.x. SO just updating the version won't solve anything. I am certainly hoping that firefox-x11 will be available, this is currently my most significant usability issue (I am using Mac OS firefox but Aqua does not play well with my X11 window manager so I would be ecstatic to have an X11 application instead). Stefan ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: installing old port version
Hi, At 23:24 +0200 on 2007-4-21
Re: fltk problems
Hi, Apologies for the delayed response. At 01:01 -0400 on 2007-4-11 Yves de Champlain wrote: The new fltk does not work for me too well. The fluid issue has already been noted, and I also note the following problem: flstring.h:29:28: error: FL/Fl_Export.H: No such file or directory Maybe it is something I am doing wrong, I have not checked things thoroughly yet (but I will do so and I will write back if I will find something notable). This issue disappeared magically in the new version (1.1.1.7_2) so there is no need for any ticket on the matter. Still on bugs, am I the only one for whom the JPEG handling is broken in FLTK? I am using only one FLTK application (flPhoto), but I had to replace or eliminate all the code for (a) JPEG generation, and (b) EXIF data readout. Otherwise I would get a bus error every time such a code was being executed. In any case, is it terribly difficult to have an X11 fltk (as a variant maybe)? I would be ecstatic to have all my applications working under X (I like the UI semantics much better) and fltk-based applications (I am actually using only one, but anyway...) are one significant breakage of this desired state (for me). It may be not terribly difficult to have a Mac/X11 fltk build, but it surely is a significant undertaking, IMHO. Any clue where to start from? I am not sure what libraries and includes re necessary to do this, and so my attempts always end up with undefined symbols at link time. Thanks, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: libidl build failure
Hi, Andreas Wuest wrote: Do you have port libidl1 installed? This port seems to conflict with libidl. Yes indeed, that (uninstalling libidl1 that is) does it nicely. In the meantime I also found a bug report in this respect http://trac.macports.org/projects/macports/ticket/11570. Thanks for the tip. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: fltk problems
Hi, At 01:10 -0400 on 2007-4-10 Yves de Champlain wrote: fltk was in a dire state. rev 1 should be much better, just commited The new fltk does not work for me too well. The fluid issue has already been noted, and I also note the following problem: flstring.h:29:28: error: FL/Fl_Export.H: No such file or directory Maybe it is something I am doing wrong, I have not checked things thoroughly yet (but I will do so and I will write back if I will find something notable). In any case, is it terribly difficult to have an X11 fltk (as a variant maybe)? I would be ecstatic to have all my applications working under X (I like the UI semantics much better) and fltk-based applications (I am actually using only one, but anyway...) are one significant breakage of this desired state (for me). Many thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
ESD loads the system on idle
Hi, The following problem started to pop up recently, though I am not sure what I did (probably upgraded the outdated packages including some GNOME ones): ESD launches fine, plays the sounds fine, but during idle moments it doesn't just sit there, but sits there loading the system (to 99% or thereabouts). Interestingly enough, the load goes down when ESD actually play sounds, the load is high only when idle. Is there any known cause of this, or any way of debugging the matter further. Thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
libidl build failure
Hi, During the normal upgrade I get the following failure for libidl. Any idea how to fix it? Thanks in advance. godel:~ port -v upgrade libidl --- Fetching libidl --- Verifying checksum(s) for libidl --- Checksumming libIDL-0.8.8.tar.bz2 --- Extracting libidl --- Extracting libIDL-0.8.8.tar.bz2 --- Configuring libidl normal configuration output deleted libIDL 0.8.8 configuration complete C Preprocessor: gcc -E Standard input supported. --- Building libidl with target all bison -y -d -v 2/dev/null ./parser.y touch stamp-parser test -f y.tab.h mv -f y.tab.h parser.h || touch parser.h flex -8 -t ./lexer.l | sed -e 's/yy/__IDL_/g' lexer.c test -f y.tab.c mv -f y.tab.c parser.c || touch parser.c make all-recursive Making all in include Making all in libIDL make all-am make[4]: Nothing to be done for `all-am'. make[3]: Nothing to be done for `all-am'. test -f y.tab.c mv -f y.tab.c parser.c || touch parser.c if /bin/sh ./libtool --mode=compile gcc -DPACKAGE_NAME=\libIDL\ -DPACKAGE_TARNAME=\libIDL\ -DPACKAGE_VERSION=\0.8.8\ -DPACKAGE_STRING=\libIDL\ 0.8.8\ -DPACKAGE_BUGREPORT=\http://bugzilla.gnome.org/enter_bug.cgi\?product=libIDL\; -DLIBIDL_VERSION=\0.8.8\ -DHAVE_CPP_PIPE_STDIN=1 -DCPP_NOSTDINC=\-I-\ -DCPP_PROGRAM=\gcc\ -E\ -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -DHAVE_STDDEF_H=1 -DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1 -DHAVE_POPEN=1 -DHAVE_SYMLINK=1 -DHAVE_ACCESS=1 -DSIZEOF_LONG_LONG=8 -I. -I. -DYYDEBUG=1 -DYYERROR_VERBOSE=1 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I./include -DG_LOG_DOMAIN=\libIDL\ -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations-no-cpp-precomp -MT parser.lo -MD -MP -MF .deps/parser.Tpo \ -c -o parser.lo `test -f 'parser.c' || echo './'`parser.c; \ then mv -f .deps/parser.Tpo .deps/parser.Plo; \ else rm -f .deps/parser.Tpo; exit 1; \ fi mkdir .libs gcc -DPACKAGE_NAME=\libIDL\ -DPACKAGE_TARNAME=\libIDL\ -DPACKAGE_VERSION=\0.8.8\ -DPACKAGE_STRING=\libIDL 0.8.8\ -DPACKAGE_BUGREPORT=\http://bugzilla.gnome.org/enter_bug.cgi?product=libIDL\; -DLIBIDL_VERSION=\0.8.8\ -DHAVE_CPP_PIPE_STDIN=1 -DCPP_NOSTDINC=\-I-\ -DCPP_PROGRAM=\gcc -E\ -DYYTEXT_POINTER=1 -DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 -DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_DLFCN_H=1 -DSTDC_HEADERS=1 -DHAVE_STDDEF_H=1 -DHAVE_UNISTD_H=1 -DHAVE_WCHAR_H=1 -DHAVE_POPEN=1 -DHAVE_SYMLINK=1 -DHAVE_ACCESS=1 -DSIZEOF_LONG_LONG=8 -I. -I. -DYYDEBUG=1 -DYYERROR_VERBOSE=1 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include -I/opt/local/include -I./include -DG_LOG_DOMAIN=\libIDL\ -Wall -Wunused -Wmissing-prototypes -Wmissing-declarations -no-cpp-precomp -MT parser.lo -MD -MP -MF .deps/parser.Tpo -c parser.c -fno-common -DPIC -o .libs/p arser.o In file included from util.h:36, from ./parser.y:33: /opt/local/include/libIDL/IDL.h:43:1: warning: LIBIDL_VERSION redefined command line:1:1: warning: this is the location of the previous definition ./parser.y: In function '__IDL_parse': ./parser.y:396: error: 'IDLF_DECLSPEC_PIDL' undeclared (first use in this function) ./parser.y:396: error: (Each undeclared identifier is reported only once ./parser.y:396: error: for each function it appears in.) ./parser.y: In function 'IDL_parse_declspec': ./parser.y:1731: error: 'IDLF_DECLSPEC_PIDL' undeclared (first use in this function) ./parser.y: At top level: ./parser.y:1739: error: conflicting types for 'IDL_file_set' /opt/local/include/libIDL/IDL.h:735: error: previous declaration of 'IDL_file_set' was here ./parser.y: In function 'IDL_file_set': ./parser.y:1772: error: 'IDLF_SRCFILES' undeclared (first use in this function) ./parser.y:1775: warning: implicit declaration of function 'IDL_srcfile_new' ./parser.y:1775: warning: assignment makes pointer from integer without a cast make[2]: *** [parser.lo] Error 1 make[1]: *** [all-recursive] Error 1 make: *** [all] Error 2 Error: Target com.apple.build returned: shell command cd /opt/local/var/db/dports/build/_opt_local_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_devel_libidl/work/libIDL-0.8.8 make all returned error 2 ... and then the build process continues stumbling once more upon the same issue. -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: ESD loads the system on idle
Hi, At 18:40 -0500 on 2007-3-24 Ryan Schmidt wrote: On Mar 24, 2007, at 09:22, Stefan Bruda wrote: The following problem started to pop up recently, though I am not sure what I did (probably upgraded the outdated packages including some GNOME ones): ESD launches fine, plays the sounds fine, but during idle moments it doesn't just sit there, but sits there loading the system (to 99% or thereabouts). Interestingly enough, the load goes down when ESD actually play sounds, the load is high only when idle. Is there any known cause of this, or any way of debugging the matter further. I wouldn't think that would have anything to do with MacPorts. You may want to ask the developers of EDS. It's ESD actually, and I was using GNOME terminology; the actual port is audio/esound. It runs happily on all the Linux boxes I have around (plus on this one when I boot Linux on it) so I am not quite sure whether its an upstream problem. On the other hand... I just noticed that I must have upgraded the thing on this box as I have two versions installed. Deactivating the newer version and activating the old one eliminates the problem, so maybe it's an upstream issue after all (I don't have the old port so I don't know if anything changed in there). I would have checked the EDS portfile to see if it's doing anything weird, but I can find no port called EDS, so I don't know what port you're talking about. Then again I don't know anything about Gnome so maybe this will be self-explanatory to someone who does. The port does not do anything out of ordinary as far as I can see. I will attempt to eliminate the patches maybe this will help since they alter a timeout value (= a reson for things to behave differently while waiting for stuff to happen). In any event, I hereby note that esound @0.2.37_0 exhibits the mentioned behaviour, while esound @0.2.36_0 does not. Thanks for the answer, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
jpeg (?) troubles (flphoto, eog)
Hi, I am having what I believe to be problems with the jpeg package. They manifest themselves most notably in FLTK applications (only one realy, flPhoto) but I also believe that they are the cause of eog crashes. It goes like this: fltk builds fine as is, but fluid crashes upon startup and so does flphoto (probably other fltk applications too, but I have not tried anything else). I then built fltk with --disable-shared and I thus get both fluid and flphoto to run. flphoto however dies with JPEG parameter struct mismatch: library thinks size is 356, caller expects 372 the moment it tries to write a JPEG image (reading seems fine). Reading EXIF data from JPEG photos results in bus errors (are these the segfaults of BSD, bu the way?). Googling this resulted in the most encountered conclusion that the jpeg headers and binaries come from two different versions, or that integer size or allignment are different from one binary to another. I tried playing around with -malign-double (in both fltk and flphoto). The mismatch values change (library thinks size is 360, caller expects 376) but they are off by the same amount. I thus conclude that the first cause (mismatching between headers and binaries in the jpeg package) are the culprit. Problem is, I am not aware of any duplicate installation. Actually I have only two jpeglib.h, one from MacPorts and another from a Gentoo prefixed installation (whose paths are I believe not included anywhere). Same goes for libjpeg.dylib. In possibly incidental matter, eog crashes upon startup, I have no idea how to dig for the cause (is there any way to build programs with debugging on short of hacking each and every port?). It might be unrelated, but I would really appreciate any hint about this how unrelated this might be. Interestingly enough the Gimp runs just fine... For the moment I hacked flphoto and I replaced all its attempts to write JPEGS with calls to Imagemagick utilities (they work fine too), and I simply suppressed everything that deals with EXIF data. In all, I am reasonably happy as far as flphoto is concerned. However, I miss eog and I would generaly take a good solution instead of my hack at any time of day. I am running Mac OS 10.4.9 (all of this happened in 10.4.8 too) and MacPOrts 1.32 on a Core 2 Duo Macbook Pro. I am good at hacking but I am just beginning to get hold of MacPorts (I come however from Gentoo Linux so I am reasonably comfortable with the idea). So any advice, however technical, is appreciated. I am not sure what other information to include so please ask for anything that I missed here. Thanks in advance, Stefan -- If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
Re: jpeg (?) troubles (flphoto, eog)
Randall Wood wrote: eog dies quite consistently here, what do you mean by not being able to reproduce the problem? eog consistently crashes, but nothing else seems to have this problem. Oh, I see, sorry for the confusion. Stefan If it was so, it might be; and if it were so, it would be; but as it isn't, it ain't. That's logic. --Lewis Carroll, Through the Looking-Glass ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
