Compile Octave with GraphicsMagick patched
Hi all, I'm not able to use 'imread()' with the octave version provided with ports since it uses GraphicsMagick unpatched (the patch I'm talking about concerns a widespread problem and can be found here http://savannah.gnu.org/bugs/?29474). More generally, is there a way to patch a port before building it? Or, is there a way to tell ports to use an already existing dependency lib instead of fetching and configuring their own?___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
RE: How do I get etherape to work in OS X 10.6.6?
As I understand it you don't need to do that since ultimately gcc4.5 gets built by gcc4.5. Russell From: macports-users-boun...@lists.macosforge.org [macports-users-boun...@lists.macosforge.org] on behalf of Zack Perry [zack.pe...@sbcglobal.net] Sent: 08 March 2011 01:56 To: Ryan Schmidt Cc: macports-users@lists.macosforge.org Subject: Re: How do I get etherape to work in OS X 10.6.6? Hi Ryan, I will just use the gcc 4.4 in the ports to bootstrap gcc 4.5.2, avoiding the older gcc that Apple provides. I used to do a lot builds and packaging of GNU and other free software in Sun Solaris (SPARC/UltraSPARC hosts mostly) for the company I worked for, so I am used to this kind of activities. Since I am at it, I might as well do it all way, building the compiler first and every other library that etherape depends. I know it's tedious, and see this as a last resort but if I need to, I will do it (built etherape from scratch in Solaris before and it worked) Best, -- Zack Certainly if you wish to install gcc45 for other purposes you can do so, but I'm not sure what this has to do with etherape. The etherape port does not have a dependency on gcc45, and will not use it even if it is present; it will use the gcc provided in Apple's Xcode, just like most other ports do. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Multiple ports error on upgrade
On 3 Mar, 2011, at 3:30 pm, Ryan Schmidt wrote: On Mar 3, 2011, at 09:20, Philip Hudson wrote: On 2 Mar, 2011, at 4:02 pm, Ryan Schmidt wrote: Sounds like you have a rogue dlfcn.h header, either in /usr/local/ include or /opt/local/include, which should be removed. If it's in /usr/local, remove it, and anything else you may have in /usr/ local; having things in /usr/local is a great way to cause problems for MacPorts. If it's in /opt/local, use port provides to find out what port provided it; if it's not provided by a port, remove it; if it is, let us know what port so we can investigate. I did indeed have a file /usr/local/include/dlfcn.h; I deleted it, re-ran port upgrade, and got exactly the same error and log. Clean the affected port and try again. (sudo port clean) sudo find /opt -name dlfcn.h reveals 4 files (3 distinct according to diff) under /opt/local/var/macports/build, two each for xulrunner and Python 2.7.1. Each is not provided by a MacPorts port according to port provides. Correct, things in /opt/local/var/macports/ aren't registered to ports; that's ok and not a problem, and having dlfcn.h or other files there is not a problem. It's only a problem if the file is in a path that's searched for include files. Those paths are at least / usr/include, /usr/local/include, /opt/local/include. Thanks for that. Did a sudo port clean --all all, then upgrade produced the following again: --- Computing dependencies for openssl --- Building opensslError: Target org.macports.build returned: shell command failed (see log for details)Log for openssl is at: / opt/local/var/macports/logs/ _opt_local_var_macports_sources_rsync .macports.org_release_ports_devel_openssl/main.log Error: Unable to upgrade port: 1 Cited log file tail: :info:build making all in crypto/dso... :info:build /usr/bin/gcc-4.0 -I.. -I../.. -I../asn1 -I../evp -I../../ include -fPIC -fno-common -DOPENSSL_PI C -DZLIB -DOPENSSL_THREADS -D_REENTRANT -DDSO_DLFCN -DHAVE_DLFCN_H - arch ppc -O3 -DB_ENDIAN -Wa,-force_cpusu btype_ALL -c -o dso_dlfcn.o dso_dlfcn.c :info:build dso_dlfcn.c:84:20: error: dlfcn.h: No such file or directory :info:build dso_dlfcn.c: In function 'dlfcn_load': :info:build dso_dlfcn.c:170: error: 'RTLD_NOW' undeclared (first use in this function) :info:build dso_dlfcn.c:170: error: (Each undeclared identifier is reported only once :info:build dso_dlfcn.c:170: error: for each function it appears in.) :info:build dso_dlfcn.c:182: warning: assignment makes pointer from integer without a cast :info:build dso_dlfcn.c: In function 'dlfcn_bind_var': :info:build dso_dlfcn.c:250: warning: assignment makes pointer from integer without a cast :info:build dso_dlfcn.c: In function 'dlfcn_bind_func': :info:build dso_dlfcn.c:284: warning: assignment makes pointer from integer without a cast :info:build dso_dlfcn.c: In function 'dlfcn_pathbyaddr': :info:build dso_dlfcn.c:445: error: 'Dl_info' undeclared (first use in this function) :info:build dso_dlfcn.c:445: error: syntax error before 'dli' :info:build dso_dlfcn.c:455: error: 'dli' undeclared (first use in this function) :info:build dso_dlfcn.c: In function 'dlfcn_globallookup': :info:build dso_dlfcn.c:472: error: 'RTLD_LAZY' undeclared (first use in this function) :info:build dso_dlfcn.c:472: warning: initialization makes pointer from integer without a cast :info:build dso_dlfcn.c:476: warning: assignment makes pointer from integer without a cast :info:build make[2]: *** [dso_dlfcn.o] Error 1 :info:build make[1]: *** [subdirs] Error 1 :info:build make: *** [build_crypto] Error 1 :info:build shell command cd /opt/local/var/macports/build/ _opt_local_var_macports_sources_rsync.macports .org_release_ports_devel_openssl/work/openssl-1.0.0d /usr/bin/ make all returned error 2 :error:build Target org.macports.build returned: shell command failed (see log for details) :debug:build Backtrace: shell command failed (see log for details) while executing command_exec build (procedure portbuild::build_main line 8) invoked from within $procedure $targetname :info:build Warning: the following items did not execute (for openssl): org.macports.destroot org.macports.b uild :notice:build Log for openssl is at: /opt/local/var/macports/logs/ _opt_local_var_macports_sources_rsync.macp orts.org_release_ports_devel_openssl/main.log What now? -- Phil Hudson http://hudson-it.no-ip.biz @UWascalWabbit PGP/GnuPG ID: 0x887DCA63 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: perl5, perl5.* changes
Arno Hautala arno at alum.wpi.edu writes: I think a cleaner transition would have been to add the 5.8 variant, set it as default (essentially no change from the previous behavior), and then wait some number of weeks before changing the default variant to 5.12. This way, most users would already be on the 5.8 variant and would not be affected by the change in defaults. Personally, I'm not sure I'm ready to move to 5.12 (I need to recompile all my installed p5 modules and test a few scripts), so I've resolved things on my side by correcting my broken perl5 install with perl5+perl5_8. At least, that's my take. I ran into this problem with upgrading my installed packages. I had previously been running Perl 5.8. I ended up with Perl 5.12 which doesn't interoperate well will some of the software I use everyday. I started trying to revert back to Perl 5.8, was completely stumped by the process, and uninstalled quite a large number of ports to get back to no Perl from MacPorts at all. I started trying to install Perl 5.8 by perl5 +perl5_8, and here were my results: bash-3.2# port install perl5 +perl5_8 --- Computing dependencies for perl5 --- Fetching perl5 --- Verifying checksum(s) for perl5 --- Extracting perl5 --- Configuring perl5 --- Building perl5 --- Staging perl5 into destroot --- Installing perl5 @5.12.3_1+perl5_8 --- Activating perl5 @5.12.3_1+perl5_8 --- Cleaning perl5 Why am I getting Perl 5.12.3_1 when I clearly want Perl 5.8? --Dave Aiello ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: perl5, perl5.* changes
On Tue, Mar 8, 2011 at 11:38 AM, Dave Aiello d...@daveaiello.com wrote: I started trying to install Perl 5.8 by perl5 +perl5_8, and here were my results: bash-3.2# port install perl5 +perl5_8 --- Computing dependencies for perl5 --- Fetching perl5 --- Verifying checksum(s) for perl5 --- Extracting perl5 --- Configuring perl5 --- Building perl5 --- Staging perl5 into destroot --- Installing perl5 @5.12.3_1+perl5_8 --- Activating perl5 @5.12.3_1+perl5_8 --- Cleaning perl5 Why am I getting Perl 5.12.3_1 when I clearly want Perl 5.8? Did you actually end up with 5.12 installed or 5.8? Probably the version numbering system for the perl5 package is just a little confusing if you don't use the default variant. Scott ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Fwd: perl5, perl5.* changes
Forwarding to the list as Dave's reply to me off-list may be worth considering in terms of how to move forward with this perl5 stuff. Scott -- Forwarded message -- From: Dave Aiello d...@daveaiello.com Date: Tue, Mar 8, 2011 at 1:59 PM Subject: Re: perl5, perl5.* changes To: Scott Webster sewebs...@gmail.com On Mar 8, 2011, at 3:47 PM, Scott Webster wrote: Did you actually end up with 5.12 installed or 5.8? Probably the version numbering system for the perl5 package is just a little confusing if you don't use the default variant. Scott Scott: Thanks for thinking of this. When I checked, the variant that was installed reports back as 5.8.9. Do you think that this should be raised as some sort of bug? I mean, I would never have thought that something labeled perl5 @5.12.3_1+perl5_8 was actually Perl 5.8.9 unless someone suggested it. --Dave Aiello ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
segmentation fault
Hello list, I am a newbie on OS X. i installed macports with the installer, and installed some ports, quite fine. When trying to install gnome a power failure occured! and now, i am stuck with a macports problem: any action will fail with segmentation fault. exemple: port -d install p5-mac-carbon: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-mac-carbon DEBUG: OS darwin/10.6.0 (Mac OS X 10.6) arch i386 DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl DEBUG: Re-registering default for configure.universal_args DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Starting logging for p5-mac-carbon but the logfile is 0 length. the os: uname -a Darwin macmini 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386 i386 the registry does not seem empty. Please can you tell me what to do, should i reinstall all the macports collection? Many thanks in advance for your help. Regards rmgls rm...@free.fr ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Multiple ports error on upgrade
On Mar 8, 2011, at 10:06, Philip Hudson wrote: On 3 Mar, 2011, at 3:30 pm, Ryan Schmidt wrote: On Mar 3, 2011, at 09:20, Philip Hudson wrote: On 2 Mar, 2011, at 4:02 pm, Ryan Schmidt wrote: Sounds like you have a rogue dlfcn.h header, either in /usr/local/include or /opt/local/include, which should be removed. If it's in /usr/local, remove it, and anything else you may have in /usr/local; having things in /usr/local is a great way to cause problems for MacPorts. If it's in /opt/local, use port provides to find out what port provided it; if it's not provided by a port, remove it; if it is, let us know what port so we can investigate. I did indeed have a file /usr/local/include/dlfcn.h; I deleted it, re-ran port upgrade, and got exactly the same error and log. Clean the affected port and try again. (sudo port clean) Thanks for that. Did a sudo port clean --all all, then upgrade produced the following again: :info:build dso_dlfcn.c:84:20: error: dlfcn.h: No such file or directory dlfcn.h ought to exist in /usr/include/dlfcn.h. Does it? If not, your OS is incomplete and this file and any others that are missing will have to be restored from your backups or reinstalled from your Mac OS X DVD. If it does exist, then I'm not sure why it can't be found; we may need to see the complete main.log file to be able to diagnose this further. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Could not find my_print_defaults
Ryan, I did all of the cleaning I knew how, and the results are not good. I still get Could not find mysqld and the statement that non-existent directories were searched. I can fix that with --basedir= or --srcdir=, but that will not help if mysqld is corrupt which it is. It appears that my Mac is corrupting mysqld when I download it. I am going to open another thread asking if anyone could send me a copy of the contents of a current mysqld. Maybe that way I can determine what is happening when I download one. David On Mar 7, 2011, at 9:05 PM, Ryan Schmidt wrote: On Mar 7, 2011, at 19:29, David Gentry wrote: I apologize for the message below. After I sent it, I discovered that my mysqld file is not provided by MacPorts. None of the other files I moved today are provided by MacPorts either. Since they are not provided by MacPorts, I trashed my mysqld file and the other files I moved to /opt/local/lib/mysql5/bin. Please ignore the below message! I am sorry for any inconvenience it caused. Unless you have a better idea, I am going to: 1. Delete the mysql and mysql-server ports in the manner you described in an email to me. 2. Delete all other files on my Mac with mysql in the names that could possibly conflict with files from MacPorts. 3. Again, install the mysql and mysql-server ports. 4. Return to the wiki to set up a main database, etc. Ah, I'm glad you found that the files were not the ones provided by MacPorts, because I wasn't sure what to suggest otherwise. Let us know if everything works after cleaning up and trying again. David J. Gentry President Good Things -- Small Packages, LLC 205-637-8000 dgen...@localbusinesswebsites.com www.localbusinesswebsites.com ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Please send contents of current mysqld file
My Mac appears to corrupt the mysqld file whenever I download mysql5 and mysql5-server from MacPorts. I would very much like to see a current copy of the contents of mysqld. Maybe that way I can determine what my Mac is doing to mysqld. Could someone please send me a copy of the contents of mysqld? David ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Sending mail with mutt
I've been trying to get mutt to be able to send email, but I don't know what I need to configure. I tried using ssmtp, but it consistently segfaults (as noted in https://trac.macports.org/ticket/27673). When I don't give mutt any outgoing mail configuration it seems to be happy sending, but no email ever arrives anywhere. It seems to be getting queued in /var/spool/postfix/active, but I am not familiar enough with postfix to figure out what I should be doing with it. Help? --Greg ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Please send contents of current mysqld file
On Mar 8, 2011, at 19:51, David Gentry wrote: My Mac appears to corrupt the mysqld file whenever I download mysql5 and mysql5-server from MacPorts. I would very much like to see a current copy of the contents of mysqld. Maybe that way I can determine what my Mac is doing to mysqld. Could someone please send me a copy of the contents of mysqld? I can 100% assure you that if MacPorts extracts the downloaded file (and then patches, configures, builds, destroots, and installs it), it is not corrupt. MacPorts includes checksums on all distfiles and will not proceed if the file you downloaded is not exactly byte-for-byte the same file that I (in the case of the mysql ports) verified works correctly. mysqld is a compiled program, and how it is compiled depends on your operating system version and processor architecture. So getting one from someone else won't necessarily get you something that works on your system. From what you've written on this topic before, I have no reason so far to believe there is a fault in the mysqld program particularly. It's certainly possible our instructions in the wiki have gone out of date; I have not tried to follow them in a long time. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: segmentation fault
On Mar 8, 2011, at 16:11, rm...@free.fr wrote: I am a newbie on OS X. i installed macports with the installer, and installed some ports, quite fine. When trying to install gnome a power failure occured! and now, i am stuck with a macports problem: any action will fail with segmentation fault. exemple: port -d install p5-mac-carbon: DEBUG: Changing to port directory: /opt/local/var/macports/sources/rsync.macports.org/release/ports/perl/p5-mac-carbon DEBUG: OS darwin/10.6.0 (Mac OS X 10.6) arch i386 DEBUG: org.macports.load registered provides 'load', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.unload registered provides 'unload', a pre-existing procedure. Target override will not be provided DEBUG: org.macports.distfiles registered provides 'distfiles', a pre-existing procedure. Target override will not be provided DEBUG: Using group file /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/group/perl5-1.0.tcl DEBUG: Re-registering default for configure.universal_args DEBUG: adding the default universal variant DEBUG: Reading variant descriptions from /opt/local/var/macports/sources/rsync.macports.org/release/ports/_resources/port1.0/variant_descriptions.conf DEBUG: Starting logging for p5-mac-carbon but the logfile is 0 length. the os: uname -a Darwin macmini 10.6.0 Darwin Kernel Version 10.6.0: Wed Nov 10 18:13:17 PST 2010; root:xnu-1504.9.26~3/RELEASE_I386 i386 the registry does not seem empty. Please can you tell me what to do, should i reinstall all the macports collection? Where in this do you see that a segmentation fault occurred? It might help to know what program segfaulted and to see the crash log of it. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Compile Octave with GraphicsMagick patched
On Mar 8, 2011, at 02:10, conahorse wrote: Hi all, I'm not able to use 'imread()' with the octave version provided with ports since it uses GraphicsMagick unpatched (the patch I'm talking about concerns a widespread problem and can be found here http://savannah.gnu.org/bugs/?29474). The patch attached there 8 months ago indicates changes to be made to both GraphicsMagick and octave to solve the problem. If this is so important, why have the developers of these software packages not incorporated these changes by now? More generally, is there a way to patch a port before building it? Sure: sudo port extract PORTNAME Then go into the directory identified by: port work PORTNAME Make the changes you desire. Then: sudo port install PORTNAME and it will pick up where it left off. Or, is there a way to tell ports to use an already existing dependency lib instead of fetching and configuring their own? No, MacPorts uses its own libraries only; we cannot support the uncertainty of allowing users to provide their own versions of things. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
