Re: macports Error: Port m4 not found
On Aug 3, 2011, at 15:38, Jacob, Raymond A Jr. CIV SPAWARSYSCEN-ATLANTIC, 58150 wrote: Question: I see m4 in the .../devel/m4 directory and I see a PortFile too. Is there another file that I should check? I am using subversion to access macports, in case that makes a difference. Thank you, raymond OS X 10.5.8 uname -a Darwin x 9.8.0 Darwin Kernel Version 9.8.0: Wed Jul 15 16:55:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_I386 i386 $ sudo port -d install m4 Password: Error: Port m4 not found selfupdate and try again. The m4 port is definitely there. Perhaps there is something wrong with your portindex (which a selfupdate (or sync)) should rebuild. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
gcc 4.6 port for OSX Lion
Hello, I need to install gcc 4.6 on OSX Lion. I found serveral ports that mention gcc in their title, but I'm not sure of which one to choose. http://www.macports.org/ports.php?by=namesubstr=gcc Could you tell me which is the right one, please ? Thanks ! Best regards, Christophe ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Salut Christophe, I need to install gcc 4.6 on OSX Lion. I found serveral ports that mention gcc in their title, but I'm not sure of which one to choose. You can’t. Well, there is a gcc46 port but it installs a deprecated ß-version. I myself tried to update the port and install gcc 4.6.[01]: It fails because of a ld (1) bug in the 10.7 toolchain – at least, if you want gfortran to be built: It does not seem to plague C, C++ and obj-C front-ends. So, if you are just interested in the C-family languages, I can give you the portfile so you can have a try. Ciao ! Vincent PS: pas d’espaces en anglais avant ! et ?, contrairement au français… :) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Emacs cannot open termcap database resolution
On Aug 4, 2011, at 09:23, Rodolfo Aramayo wrote: We were finally able to pin down the reason why emacs could not open the termcap database in some of my computers but not in others To make a long story short: emacs was being compiled against 'libintl.dylib' library that was built for i386 which is not the architecture being linked (x86_64). This library was part of an INACTIVE Fink installation. This is very confusing to me because: Fink was NOT active. I installed it because I was trying to install a weird program. But after that I removed Fink from my PATHS. I had No Fink in '/etc/profile' No Fink in .bashrc. No Fink in .bash_profile. Regardless, somehow during emacs compilation the wrong ncurses library was being found and emacs was linking to the incorrect compilation of libncurses. The solution: I deleted the '/sw' directory and proceeded to re-install emacs via Ports and YES this time it works!! Please see: https://trac.macports.org/ticket/30581 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
On Aug 4, 2011, at 05:32, vincent habchi wrote: I need to install gcc 4.6 on OSX Lion. I found serveral ports that mention gcc in their title, but I'm not sure of which one to choose. You can’t. Well, there is a gcc46 port but it installs a deprecated ß-version. Yes, although the date of that version is the same day the final 4.6.0 version was released, so it can't be too terribly different. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Le 4 août 2011 à 16:42, Ryan Schmidt a écrit : Yes, although the date of that version is the same day the final 4.6.0 version was released, so it can't be too terribly different. Thanks for pointing out this: I hadn’t even checked. Yet, it is impossible, with this port, to build both fortran and java, it seems. Cheers Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
On Aug 4, 2011, at 09:51, vincent habchi wrote: Le 4 août 2011 à 16:42, Ryan Schmidt a écrit : Yes, although the date of that version is the same day the final 4.6.0 version was released, so it can't be too terribly different. Thanks for pointing out this: I hadn’t even checked. Yet, it is impossible, with this port, to build both fortran and java, it seems. Yes, the gfortran and java variants are conflicting. Pre-release versions of the gcc ports have always had this restriction, though there is no need for it. I submitted a patch three years ago to fix it but the maintainer declined to apply it: https://trac.macports.org/ticket/16410 But as you noticed gfortran doesn't work with gcc46 anyway right now: https://trac.macports.org/ticket/30166 Perhaps that is one of the reasons why the the maintainer of the port has not updated it to the final version. (Final-version gcc ports have always included gfortran and java support before, and for gcc46 that seems not to be possible right now.) ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Ryan, Yes, the gfortran and java variants are conflicting. Pre-release versions of the gcc ports have always had this restriction, though there is no need for it. I submitted a patch three years ago to fix it but the maintainer declined to apply it: https://trac.macports.org/ticket/16410 Any good reason why? But as you noticed gfortran doesn't work with gcc46 anyway right now: https://trac.macports.org/ticket/30166 Perhaps that is one of the reasons why the the maintainer of the port has not updated it to the final version. (Final-version gcc ports have always included gfortran and java support before, and for gcc46 that seems not to be possible right now.) Ryan, you’re just brilliant! I hadn’t seen this report: in fact, I get the same error on Lion, and opened a radar. But I am not sure it will be duly considered (or maybe duplicate). By the way, Portfile for llvm-devel and dragonegg (based on gcc45) are working. May I submit those? Cheers, Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
port selfupdate failed (on Lion)
Hi! I just got the following output after running svn up followed by sudo port selfupdate: Warning: port definitions are more than two weeks old, consider using selfupdate --- Updating the ports tree --- Updating MacPorts base sources using rsync MacPorts base version 1.9.99 installed, MacPorts base version 2.0.1 downloaded. --- MacPorts base is outdated, installing new version 2.0.1 Installing new MacPorts release in /opt/local as root:admin; permissions 0755; Tcl-Package in /Library/Tcl Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed I assume this is a common problem on Lion? If not, I'd be happy to provide whatever logs are needed to troubleshoot this. Any help is greatly appreciated! -- Johannes Obligatory current favourite quotes: We are all atheists about most of the gods that societies have ever believed in. Some of us just go one god further. --Richard Dawkins Religion is regarded by the common people as true, by the wise as false, and by the rulers as useful. -- Seneca I have more confidence in the methods of science, based on the amazing record of science and its ability over the centuries to answer unanswerable questions, than I do in the methods of faith (what are they?). -- David J. Gross Physics Nobel Laureate Atheism is a religion to the same extent that not collecting stamps is a hobby. -- seen on Slashdot.org http://xkcd.com/808/ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port selfupdate failed (on Lion)
On 2011-08-04 17:40 , Johannes Ruscheinski wrote: Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed I assume this is a common problem on Lion? If not, I'd be happy to provide whatever logs are needed to troubleshoot this. No, MacPorts is supposed to work on Lion. Please run 'sudo port -d selfupdate' to see the debug output. It should indicate what exactly failed. Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Le 4 août 2011 à 12:32, vincent habchi a écrit : Salut Christophe, I need to install gcc 4.6 on OSX Lion. I found serveral ports that mention gcc in their title, but I'm not sure of which one to choose. You can’t. Well, there is a gcc46 port but it installs a deprecated ß-version. I myself tried to update the port and install gcc 4.6.[01]: It fails because of a ld (1) bug in the 10.7 toolchain – at least, if you want gfortran to be built: It does not seem to plague C, C++ and obj-C front-ends. So, if you are just interested in the C-family languages, I can give you the portfile so you can have a try. Ciao ! Vincent PS: pas d’espaces en anglais avant ! et ?, contrairement au français… :) Well, all I need is actually C-family languages so I think it'll be ok. So I've chosen gcc46 port that install 4.6.01 and all seems to work fine. To use this new version, I had to change some symbolic links in /usr/bin. Was it right to proceed that way ? By the way, what is the difference between x86_64-apple-darwin11-gcc-4.6.1 and x86_64-apple-darwin11-gcc-mp-4.6? What does 'mp' stand for? Thanks a lot! Christophe PS: désolé pour la ponctuation, je ne suis pas un spécialiste de la typographie anglaise ... ;-) Vive Latex ! ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port selfupdate failed (on Lion)
Thu, 4 Aug 2011 (17:57 +0200 UTC) Rainer Müller wrote: On 2011-08-04 17:40 , Johannes Ruscheinski wrote: Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed I assume this is a common problem on Lion? If not, I'd be happy to provide whatever logs are needed to troubleshoot this. No, MacPorts is supposed to work on Lion. Please run 'sudo port -d selfupdate' to see the debug output. It should indicate what exactly failed. Rainer I see the same problem on SL and did for 2.00. The problem is that after the error `port -v` reports that the new version is installed, and repeating the command `port selfupdate` with '-vd' does not provide any useful answers because selfupdate does not recognize that there was an error. Finally, the output says to see the log, but there are only logs for individual packages in /opt/local/var/macports/logs. I could not find another place where the install logs are stored. Would it help to go to the /opt/local/var/macports/sources/rsync.macports.org/release/base directory and rerun configure/make/make install to see what errors there might have been? At first I suspected it was from trying to make a macports user, but the user existed for the 2.0 to 2.01 update. -- rdr ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
gcc-mp-4.4: error trying to exec '/opt/local/bin/i686-apple-darwin10-gcc-4.2.1': execvp: No such file or directory
I am running into the same error as this post -- http://lists.macosforge.org/pipermail/macports-users/2011-June/024446.html I did not see any response to it. If I use the full path to gcc, ie, /opt/local/bin/gcc I do not get the error. If I just enter gcc on the command line I do get the error. I'm not sure what is going on. Thanks Gedaliah ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc-mp-4.4: error trying to exec '/opt/local/bin/i686-apple-darwin10-gcc-4.2.1': execvp: No such file or directory
On Aug 4, 2011, at 11:57 AM, Wolosh, Glenn wrote: I am running into the same error as this post -- http://lists.macosforge.org/pipermail/macports-users/2011-June/024446.html I did not see any response to it. If I use the full path to gcc, ie, /opt/local/bin/gcc I do not get the error. If I just enter gcc on the command line I do get the error. I'm not sure what is going on. What's the output of the following? which gcc Then what's the output when you run ls -l with that path? Also, run the port select command with the -d flag and post the output, namely: sudo port -d select gcc mp-gcc44 Cheers! Frank ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
On 2011-08-04 21:58 , Rainer Müller wrote: Use the command 'port select' to change which gcc is invoked when typing 'gcc' in your shell. It will change the symlink at /opt/local/bin/gcc. sudo port select gcc gcc46 Sorry, I made a slight mistake. Should have read: sudo port select gcc mp-gcc46 Rainer ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Error m4 port not found. I tried selfupdate and found Failed to parse file errors.
Subject: re: Error m4 port not found. I tried selfupdate and found Failed to parse file errors. I am using subversion to update ports instead of rsynch. In case that has anything to do with the problem. Question: is the problem with installs_libs? $ sudo port -d selfupdate Total number of ports parsed: 147 Ports successfully parsed: 115 Ports failed: 32 Up-to-date ports skipped: 8089 DEBUG: MacPorts sources location: /opt/local/var/macports/sources/ rsync.macports.org/release/base --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/ rsync-35.2/rsync/clientserver.c(105) [receiver=2.6.9] shell command /usr/bin/rsync -rtzv --delete-after rsync:// rsync.macports.org/release/base/ /opt/local/var/macports/sources/ rsync.macports.org/release/base returned error 10 DEBUG: Error synchronizing MacPorts sources: shell command failed (see log for details) while executing macports::selfupdate [array get global_options] base_updated Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: shell command failed (see log for details) :~ $ grep m4 macports.080411.txt U/opt/local/var/macports/sources/svn.macports.org/trunk/dports/kde/ kdepim4/Portfile Failed to parse file devel/m4/Portfile: invalid command name installs_libs Adding port kde/kdepim4 :~ $ :~ $ grep Failed macports.080411.txt Failed to parse file archivers/gzip/Portfile: invalid command name installs_libs Failed to parse file devel/bazaar/Portfile: invalid command name installs_libs Failed to parse file devel/gmake/Portfile: invalid command name installs_libs Failed to parse file devel/m4/Portfile: invalid command name installs_libs Failed to parse file games/fortune/Portfile: invalid command name installs_libs Failed to parse file gnome/desktop-file-utils/Portfile: invalid command name installs_libs Failed to parse file lang/gawk/Portfile: invalid command name installs_libs Failed to parse file mail/gnupg/Portfile: invalid command name installs_libs Failed to parse file net/rsync/Portfile: invalid command name installs_libs Failed to parse file net/squid/Portfile: invalid command name add_users Failed to parse file net/squid3/Portfile: invalid command name add_users Failed to parse file python/py-altgraph/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-amqplib/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-bdist_mpkg/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-bitstring/Portfile: can't read subport: no such variable Failed to parse file python/py-blist/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-kombu/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-numeric/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-pika/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-pil/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-postgresql/Portfile: can't read subport: no such variable Failed to parse file python/py-redis/Portfile: can't set python.versions: invalid command name subport Failed to parse file python/py-tkinter/Portfile: can't set python.versions: invalid command name subport Failed to parse file sysutils/coreutils/Portfile: invalid command name installs_libs Failed to parse file sysutils/findutils/Portfile: invalid command name installs_libs Failed to parse file sysutils/getopt/Portfile: invalid command name installs_libs Failed to parse file sysutils/grep/Portfile: invalid command name installs_libs Failed to parse file textproc/gsed/Portfile: invalid command name installs_libs Failed to parse file textproc/xmlcatmgr/Portfile: invalid command name installs_libs Failed to parse file textproc/xmlto/Portfile: invalid command name installs_libs Failed to parse file x11/imake/Portfile: invalid command name installs_libs Failed to parse file x11/makedepend/Portfile: invalid command name installs_libs :~ $ ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Le 4 août 2011 à 19:59, vincent habchi a écrit : Christophe, Well, all I need is actually C-family languages so I think it'll be ok. So I've chosen gcc46 port that install 4.6.01 and all seems to work fine. You can find elsewhere (ticket #29184), or I can handle you, a portfile that will bump to latest 4.6.1. Thank you. But when I type 'gcc --version', I get this: gcc (GCC) 4.6.1 20110325 (prerelease) Is it the latest 4.6.1 that you're talking about or not ? If not, I'm interested in your portfile, but I don't really know what to do with it (I'm new to MacPorts). Could you explain this to me, please ? Christophe ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Le 4 août 2011 à 20:06, Jason Swails a écrit : Building macports should put /opt/local/bin in your PATH before anything else in your .bash_profile or .profile file (I don't recall which), so unless you've changed something that should already be there. You're right, my PATH contains /opt/local/bin Secondly, I'd suggest installing gcc_select to manage different compiler versions. You certainly can play with the links yourself to get it to work, but why not let a package that already exists do it? ;) I use it to toggle between many versions (4.2, 4.3, 4.4, 4.5, and 4.6, in addition to the apple versions). I didn't know such a package existed, thank you. But maybe using 'port select' is simpler ? Also, who uses a java compiler? Why not just use a JRE to run java programs? From what I've heard, gcj is lacking in full feature support anyway (so it doesn't seem like no java + fortran support really matters much, and I use both languages). I don't need any Java compiler (I didn't know some existed, anyway ;-) ), so I'm fine with this port. All the best, Jason Thank you. Christophe On Thu, Aug 4, 2011 at 1:59 PM, vincent habchi vi...@macports.org wrote: Christophe, Well, all I need is actually C-family languages so I think it'll be ok. So I've chosen gcc46 port that install 4.6.01 and all seems to work fine. You can find elsewhere (ticket #29184), or I can handle you, a portfile that will bump to latest 4.6.1. To use this new version, I had to change some symbolic links in /usr/bin. Was it right to proceed that way ? By the way, what is the difference between x86_64-apple-darwin11-gcc-4.6.1 and x86_64-apple-darwin11-gcc-mp-4.6? What does 'mp' stand for? 'MP' stands for MacPorts. Usually, it is a *bad* idea to alter /usr/bin tools, because other parts of the systems may depend on them. If you want to use your gcc46, you must add /opt/local/bin in your PATH variable and call gcc-mp-4.6 instead. Or, in /opt/local/bin, link your gcc46 to gcc. Vincent ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users -- Jason M. Swails Quantum Theory Project, University of Florida Ph.D. Candidate 352-392-4032 ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Le 4 août 2011 à 21:58, Rainer Müller a écrit : On 2011-08-04 19:32 , ENDERLIN Christophe wrote: To use this new version, I had to change some symbolic links in /usr/bin. Was it right to proceed that way ? By the way, what is the difference between x86_64-apple-darwin11-gcc-4.6.1 and x86_64-apple-darwin11-gcc-mp-4.6? What does 'mp' stand for? Do *not* alter any files in /usr! Thanks for this advice. I'll remember it. ;-) Use the command 'port select' to change which gcc is invoked when typing 'gcc' in your shell. It will change the symlink at /opt/local/bin/gcc. sudo port select gcc gcc46 Yes, it works. Well, almost. I put everything back in /usr as it was before my modifications, and then, I tried the 'port select' command. Now, I can see that the correct links have actually been created in /opt/local/bin but the old ones in /usr/bin have not been deleted. So, I get an error message when I try a command like 'gcc --version' which seems normal since I have two links with the same name. (one in /usr/bin and one in /opt/local/bin) I had to remove those old links in /usr/bin so that everything works fine. 'mp' means MacPorts. It's used to indicate that this is not a gcc with the Apple drivers unlike /usr/bin/gcc-4.0 or /usr/bin/gcc-4.2. Ok thanks. Also, I don't know the difference there is between gcc, llvm-gcc and X86_64-apple-darwin11-gcc Rainer Thanks for your help and good night. Christophe ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
Le 4 août 2011 à 22:00, Rainer Müller a écrit : On 2011-08-04 21:58 , Rainer Müller wrote: Use the command 'port select' to change which gcc is invoked when typing 'gcc' in your shell. It will change the symlink at /opt/local/bin/gcc. sudo port select gcc gcc46 Sorry, I made a slight mistake. Should have read: sudo port select gcc mp-gcc46 Rainer Yes it works. I got an error about a not found target gcj, but I guess it's normal if gcj is a Java compiler, right ? Christophe ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc-mp-4.4: error trying to exec '/opt/local/bin/i686-apple-darwin10-gcc-4.2.1': execvp: No such file or directory
On Aug 4, 2011, at 3:56 PM, Frank Schima wrote: On Aug 4, 2011, at 11:57 AM, Wolosh, Glenn wrote: I am running into the same error as this post -- http://lists.macosforge.org/pipermail/macports-users/2011-June/024446.html I did not see any response to it. If I use the full path to gcc, ie, /opt/local/bin/gcc I do not get the error. If I just enter gcc on the command line I do get the error. I'm not sure what is going on. What's the output of the following? which gcc Then what's the output when you run ls -l with that path? Also, run the port select command with the -d flag and post the output, namely: sudo port -d select gcc mp-gcc44 Well, this is odd, when I opened a new terminal to get the output, the gcc command worked as expected. I tried a few more times and all is well. There must have been something screwy particular to the terminal I was working in. Thanks G Cheers! Frank ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
kde installation question
Hello, I have recently installed MacPorts and among other things kde. I was trying to use neuroscope, but received the following error message Will not save configuration. Configuration file /Users/UserName/.kde/share/config/neuroscoperc not writable the file .kde is owned by root and has permissions 700 Can I change the ownership to the admin and also the permissions so that it's writable? Thanks in advance for any help ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: gcc 4.6 port for OSX Lion
On Thu, Aug 4, 2011 at 17:23, ENDERLIN Christophe c.ender...@me.com wrote: I put everything back in /usr as it was before my modifications, and then, I tried the 'port select' command. Now, I can see that the correct links have actually been created in /opt/local/bin but the old ones in /usr/bin have not been deleted. This is normal, expected, and necessary; make sure /opt/local/bin is in $PATH before /usr/bin, do *not* remove or alter the ones in /usr/bin. MacPorts doesn't modify them for the same reason you shouldn't: non-MacPorts stuff will break. So, I get an error message when I try a command like 'gcc --version' which seems normal since I have two links with the same name. (one in /usr/bin and one in /opt/local/bin) --version will report the version of the one you ran, independent of any other version anywhere. What error message are you getting? I had to remove those old links in /usr/bin so that everything works fine. Put them back; let's get this figured out correctly, do NOT break things by altering /usr/bin. Ok thanks. Also, I don't know the difference there is between gcc, llvm-gcc and X86_64-apple-darwin11-gcc gcc is normal gcc. llvm-gcc compiles to LLVM bytecode; this is handy for grid job managers which can relink LLVM executables for other platforms available in the grid, and for various optimizers that operate on LLVM bytecode. (But if you're not familiar with LLVM then you can just ignore the whole thing.) The final one is Apple's gcc for Xcode with various Xcode-specific optimizations and code generators. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: [MacPorts-announce] Update hangs configuring g95
Glad to hear it worked. Scott On Thu, Aug 4, 2011 at 5:43 PM, martin cohen mj...@yahoo.com wrote: --- On *Wed, 8/3/11, Scott Webster sewebs...@gmail.com* wrote: From: Scott Webster sewebs...@gmail.com Subject: Re: [MacPorts-announce] Update hangs configuring g95 To: macports-users@lists.macosforge.org Cc: mjco...@acm.org Date: Wednesday, August 3, 2011, 4:05 PM On Wed, Aug 3, 2011 at 4:00 PM, David Moreno da...@axiombox.comhttp://mc/compose?to=da...@axiombox.com wrote: On Aug 3, 2011 6:45 PM, martin cohen mj...@yahoo.comhttp://mc/compose?to=mj...@yahoo.com wrote: This is what happens: --- Computing dependencies for g95 --- Fetching archive for g95 --- Attempting to fetch g95-0.92_2+gcc42.darwin_10.x86_64.tgz from http://packages.macports.org/g95 --- Fetching g95 --- Attempting to fetch g95_source.tgz from http://ftp.g95.org/v0.92/ --- Verifying checksum(s) for g95 --- Extracting g95 --- Applying patches to g95 --- Configuring g95 How long did you wait? I would try again in debug mode to get more info. sudo port clean g95 sudo port -d install g95 You could also try posting the log file on the web somewhere and sending the link to the mailing list for analysis and searching the macports trac system for open tickets (bug reports) about g95 to see if this is a known issue. Scott Scott, Thanks. I did this and it seemed to work. At least it made it through with only warnings, but a surprising number of them. My macports update then ran ok. I was impressed with how long the g95 update took. I guess software is a third thing we should not watch being made. Marty Cohen ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: kde installation question
On 05/08/2011, at 10:27 AM, Monika Szulc wrote: I have recently installed MacPorts and among other things kde. I was trying to use neuroscope, but received the following error message Will not save configuration. Configuration file /Users/UserName/.kde/share/config/neuroscoperc not writable the file .kde is owned by root and has permissions 700 Can I change the ownership to the admin and also the permissions so that it's writable? ~/.kde (or $HOME/.kde) on a Linux system would be where KDE 3 applications and libraries keep your personal config, preferences, what you were doing last time, etc. It would definitely have the same ownership as /Users/UserName (or $HOME). And permissions 700 is fine. So you could try changing ownership and see if it works. With KDE 4 applications, a Linux system would use $HOME/.kde4 for these purposes, but Macports does something quite different and more in line with OS X usage. So I wonder if your .kde directory is legit in the Macports world ... Cheers, Ian W ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: kde installation question
On Thu, Aug 4, 2011 at 21:32, Ian Wadham iandw...@gmail.com wrote: With KDE 4 applications, a Linux system would use $HOME/.kde4 for these purposes, but Macports does something quite different and more in line with OS X usage. So I wonder if your .kde directory is legit in the Macports world ... As yet, if you go to install kde from MacPorts you get KDE3; you need to install the various KDE4 ports manually, there is no metaport. -- brandon s allbery allber...@gmail.com wandering unix systems administrator (available) (412) 475-9364 vm/sms ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: Error m4 port not found. I tried selfupdate and found Failed to parse file errors.
On Aug 4, 2011, at 16:06, Jacob, Raymond A Jr. CIV SPAWARSYSCEN-ATLANTIC, 58150 wrote: Subject: re: Error m4 port not found. I tried selfupdate and found Failed to parse file errors. I am using subversion to update ports instead of rsynch. In case that has anything to do with the problem. Question: is the problem with installs_libs? installs_libs is a new command introduced in MacPorts 2.0.0. MacPorts 1.x will not understand it. That is why you must update to MacPorts 2.0.0 first, which is what selfupdate is supposed to do. $ sudo port -d selfupdate Total number of ports parsed: 147 Ports successfully parsed:115 Ports failed: 32 Up-to-date ports skipped: 8089 DEBUG: MacPorts sources location: /opt/local/var/macports/sources/ rsync.macports.org/release/base --- Updating MacPorts base sources using rsync rsync: failed to connect to rsync.macports.org: Operation timed out (60) Evidently you are not able to connect to our rsync server, therefore you cannot selfupdate. Try again later. If it's not a temporary problem, and your network is banning access to rsync servers, and you or your network administrators cannot fix that, you'll have to update MacPorts base to 2.0.1 another way, for example by visiting our web site and downloading the disk image and running the installer package. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
Re: port selfupdate failed (on Lion)
On Aug 4, 2011, at 12:48, robert delius royar wrote: Thu, 4 Aug 2011 (17:57 +0200 UTC) Rainer Müller wrote: On 2011-08-04 17:40 , Johannes Ruscheinski wrote: Error: /opt/local/bin/port: port selfupdate failed: Error installing new MacPorts base: shell command failed I assume this is a common problem on Lion? If not, I'd be happy to provide whatever logs are needed to troubleshoot this. No, MacPorts is supposed to work on Lion. Please run 'sudo port -d selfupdate' to see the debug output. It should indicate what exactly failed. Rainer I see the same problem on SL and did for 2.00. The problem is that after the error `port -v` reports that the new version is installed, and repeating the command `port selfupdate` with '-vd' does not provide any useful answers because selfupdate does not recognize that there was an error. Finally, the output says to see the log, but there are only logs for individual packages in /opt/local/var/macports/logs. I could not find another place where the install logs are stored. Would it help to go to the /opt/local/var/macports/sources/rsync.macports.org/release/base directory and rerun configure/make/make install to see what errors there might have been? I do not know where or if we retain logs from selfupdate. But you can just try selfupdate again, forcing it to run again: sudo port -vf selfupdate At first I suspected it was from trying to make a macports user, but the user existed for the 2.0 to 2.01 update. MacPorts will not attempt to create the user or group if they already exist. ___ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
