OSX 10.10.4
port version 2.3.3
“port selfupdate” fails on connecting to rsync server, see output below. In the
browser
there is no problem connecting to rsync.macports.org and the connection is
instant.
Anything I can do / I should (not) do
sudo port -d selfupdate
DEBUG: Copying /Users
On Monday, August 17, 2015, Ryan Schmidt ryandes...@macports.org wrote:
On Aug 17, 2015, at 8:01 PM, Michael David Crawford wrote:
Yes, you can change what servers MacPorts uses:
https://trac.macports.org/wiki/Mirrors
If you can set up an rsync server on your network, and that server can
On Aug 17, 2015, at 8:35 PM, Michael David Crawford wrote:
On Monday, August 17, 2015, Ryan Schmidt wrote:
Yes, you can change what servers MacPorts uses:
https://trac.macports.org/wiki/Mirrors
If you can set up an rsync server on your network, and that server can
connect to our
Can one configure the port command to use a local - intranet - server for
selfupdate?
On Monday, August 17, 2015, Ryan Schmidt ryandes...@macports.org wrote:
Yes, you'll need to troubleshoot with your network administrator why
you're not able to access rsync servers. If it cannot be fixed, you
On Aug 17, 2015, at 8:04 AM, Fred Lahuis wrote:
Seems to be a firewall issue, works on home network.
Yes, you'll need to troubleshoot with your network administrator why you're not
able to access rsync servers. If it cannot be fixed, you can configure MacPorts
to sync using a different
On Aug 17, 2015, at 8:01 PM, Michael David Crawford wrote:
Can one configure the port command to use a local - intranet - server for
selfupdate?
Yes, you can change what servers MacPorts uses:
https://trac.macports.org/wiki/Mirrors
If you can set up an rsync server on your network, and
Seems to be a firewall issue, works on home network.
Fred
On 17 Aug 2015, at 13:10, Fred Lahuis f.lah...@sron.nl wrote:
OSX 10.10.4
port version 2.3.3
“port selfupdate” fails on connecting to rsync server, see output below. In
the browser
there is no problem connecting
On Jul 10, 2014, at 2:37 PM, Adam Dershowitz Ph.D., P.E. de...@alum.mit.edu
wrote:
On Jul 10, 2014, at 5:20 PM, Jerry lancebo...@qwest.net wrote:
On Jul 10, 2014, at 6:08 AM, Adam Dershowitz Ph.D., P.E.
de...@alum.mit.edu wrote:
On Jul 10, 2014, at 1:41 AM, Ryan Schmidt
On Jul 10, 2014, at 1:41 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Jul 9, 2014, at 11:01 PM, Adam Dershowitz de...@alum.mit.edu wrote:
No. They do use existing standard ports. So openmodelica does require
certain macporys dependencies, not its own separate copies. I don't know
On Jul 10, 2014, at 6:08 AM, Adam Dershowitz Ph.D., P.E. de...@alum.mit.edu
wrote:
On Jul 10, 2014, at 1:41 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Jul 9, 2014, at 11:01 PM, Adam Dershowitz de...@alum.mit.edu wrote:
No. They do use existing standard ports. So
On Jul 10, 2014, at 5:20 PM, Jerry lancebo...@qwest.net wrote:
On Jul 10, 2014, at 6:08 AM, Adam Dershowitz Ph.D., P.E. de...@alum.mit.edu
wrote:
On Jul 10, 2014, at 1:41 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Jul 9, 2014, at 11:01 PM, Adam Dershowitz
On Jul 9, 2014, at 6:15 AM, Adam Dershowitz Ph.D., P.E. de...@alum.mit.edu
wrote:
It seems that the openmodelica.org is back up, so the sync should work again
(at least it does for me)
Problem solved when openmodelica.org came back.
Maybe someday the openmodelica folks could make an
On July 9, 2014 7:15:21 PM EDT, Jerry lancebo...@qwest.net wrote:
On Jul 9, 2014, at 6:15 AM, Adam Dershowitz Ph.D., P.E.
de...@alum.mit.edu wrote:
It seems that the openmodelica.org is back up, so the sync should
work again (at least it does for me)
Problem solved when openmodelica.org came
On Jul 9, 2014, at 4:53 PM, Adam Dershowitz de...@alum.mit.edu wrote:
On July 9, 2014 7:15:21 PM EDT, Jerry lancebo...@qwest.net wrote:
On Jul 9, 2014, at 6:15 AM, Adam Dershowitz Ph.D., P.E. de...@alum.mit.edu
wrote:
It seems that the openmodelica.org is back up, so the sync should work
On Jul 9, 2014, at 11:01 PM, Adam Dershowitz de...@alum.mit.edu wrote:
No. They do use existing standard ports. So openmodelica does require certain
macporys dependencies, not its own separate copies. I don't know about Qt,
and don't have access to check at the moment. But, my guess is
Hi.
Running selfupdate results in:
'Configuring zip-archive-0.1.3.4...
Setup: At least the following dependencies are missing:
mtl -any
Command failed: cd
On Mon, Mar 25, 2013 at 10:38 AM, Phil Dobbin phildob...@gmail.com wrote:
'Configuring zip-archive-0.1.3.4...
Why do you have this port installed? If you removed ghc, perhaps you should
remove ports that require and are likely only usable by ghc.
--
brandon s allbery kf8nh
It's not installed. Neither are half a dozen other ports it keeps trying to
install which finally culminates in ghc (sorry for the ugly looking reply;
I'm using the abomination that is Google's Gmail interface).
Cheers,
Phil...
On 25 March 2013 14:41, Brandon Allbery allber...@gmail.com
On Mon, Mar 25, 2013 at 11:03 AM, Phil Dobbin phildob...@gmail.com wrote:
It's not installed. Neither are half a dozen other ports it keeps trying
to install which finally culminates in ghc (sorry for the ugly looking
reply; I'm using the abomination that is Google's Gmail interface).
Then I
On 25/03/2013 15:13, Brandon Allbery wrote:
On Mon, Mar 25, 2013 at 11:03 AM, Phil Dobbin phildob...@gmail.com
mailto:phildob...@gmail.com wrote:
It's not installed. Neither are half a dozen other ports it keeps
trying to install which finally culminates in ghc (sorry for the
On Mar 25, 2013, at 09:38, Phil Dobbin wrote:
Running selfupdate results in:
'Configuring zip-archive-0.1.3.4...
Setup: At least the following dependencies are missing:
mtl -any
Command failed: cd
In our previous episode (Wednesday, 06-Mar-2013), Ryan Schmidt said:
On Mar 6, 2013, at 14:24, LuKreme krem...@kreme.com wrote:
configure: error: in
`/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base':
configure: error: C compiler cannot create executables
See
On Mar 7, 2013, at 13:01, LuKreme wrote:
configure:3339: /usr/bin/cc --version 5
./configure: line 3341: /usr/bin/cc: No such file or directory
Please install the Xcode command line tools.
http://guide.macports.org/#installing.xcode.lion.43
___
In our previous episode (Thursday, 07-Mar-2013), Ryan Schmidt said:
On Mar 7, 2013, at 13:01, LuKreme wrote:
configure:3339: /usr/bin/cc --version 5
./configure: line 3341: /usr/bin/cc: No such file or directory
Please install the Xcode command line tools.
On Mar 7, 2013, at 17:44, LuKreme wrote:
In our previous episode (Thursday, 07-Mar-2013), Ryan Schmidt said:
On Mar 7, 2013, at 13:01, LuKreme wrote:
configure:3339: /usr/bin/cc --version 5
./configure: line 3341: /usr/bin/cc: No such file or directory
Please install the Xcode command
# port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts base version 2.1.2 installed,
MacPorts base version 2.1.3 downloaded.
--- Updating the ports tree
--- MacPorts base is outdated, installing new version 2.1.3
Installing new MacPorts release in /opt/local as root:admin;
On Mar 6, 2013, at 13:21, LuKreme wrote:
# port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts base version 2.1.2 installed,
MacPorts base version 2.1.3 downloaded.
--- Updating the ports tree
--- MacPorts base is outdated, installing new version 2.1.3
Installing new
In our previous episode (Wednesday, 06-Mar-2013), Ryan Schmidt said:
On Mar 6, 2013, at 13:21, LuKreme wrote:
# port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts base version 2.1.2 installed,
MacPorts base version 2.1.3 downloaded.
--- Updating the ports tree
---
On Mar 6, 2013, at 14:24, LuKreme krem...@kreme.com wrote:
configure: error: in
`/opt/local/var/macports/sources/rsync.macports.org/release/tarballs/base':
configure: error: C compiler cannot create executables
See `config.log' for more details
Please show us what's in this config.log
On Sep 14, 2011, at 12:38 PM, Ryan Schmidt wrote:
On Sep 13, 2011, at 21:49, William H. Magill wrote:
This is very weird… True… registry.db does not exist… no idea why unless the
previous selfupdate attempt deleted it.
False… both my userid and root (sudo)
On 28164-7-23 05:59 , William H. Magill wrote:
Returning to a problem I was having earlier before life interrupted ?.and
am still having.
I realize that the registry.db file does not exist. What I don't understand
is the couldn't write to this location part of the error.
It's a bug (fixed
On 28164-7-23 05:59 , William H. Magill wrote:
I have no problem simply wiping Mac Ports and sting over but upgrading from
Snow Leopard (where I had last run Mac Ports 1.9) to Lion and attempting to
upgrade to MacPorts 2.x should work.
Another thing: Note that the Migration instructions
On Sep 13, 2011, at 21:49, William H. Magill wrote:
This is very weird… True… registry.db does not exist… no idea why unless the
previous selfupdate attempt deleted it.
False… both my userid and root (sudo) can
write to the directory.
On Sep 12, 2011, at 8:36 PM, Ryan Schmidt wrote:
On Sep 12, 2011, at 14:54, William H. Magill wrote:
==
# 27 inch iMac Intel (mid 2010) - 27 inch diagonal screen - Acquired 6/2011
Model
Processor 2.93 GHz Intel Core i7
Note: this particular error happened before I realized I did not upgrade Xcode
on this machine…. was Xcode 4.0.2 -- OSX 10.7.1. (However, it failed again
after updating to Xcode 4.1.)
This posting is simply for the record -- that the message needs to be
expanded :).
outpost sudo port
On Sep 12, 2011, at 14:52, William H. Magill wrote:
Note: this particular error happened before I realized I did not upgrade
Xcode on this machine…. was Xcode 4.0.2 -- OSX 10.7.1. (However, it failed
again after updating to Xcode 4.1.)
This posting is simply for the record -- that the
On Sep 12, 2011, at 14:54, William H. Magill wrote:
==
# 27 inch iMac Intel (mid 2010) - 27 inch diagonal screen - Acquired 6/2011
Model
Processor 2.93 GHz Intel Core i7
Memory 4 GB 1333 MHz DDR3
Graphics ATI Radeon HD
On Mon, Sep 12, 2011 at 5:33 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 12, 2011, at 14:52, William H. Magill wrote:
Note: this particular error happened before I realized I did not upgrade
Xcode on this machine…. was Xcode 4.0.2 -- OSX 10.7.1. (However, it failed
again after
On 5 September 2011 21:48, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 5, 2011, at 23:40, Johannes Ruscheinski wrote:
Hi Ryan,
After doing a sudo port uninstall mono I still get the same error.
My build still prints out:
base32cmd.o sha1cmd.o curl.o rmd160cmd.o sha256cmd.o
On 09/06/2011 03:41 PM, Johannes Ruscheinski wrote:
Ok, so how can I remove it? And why is MacPorts picking up on it?
Something in my PATH that I need to remove?
IIRC, Mono installs a symlink to their pkg-config in the Mono.framework
into /usr/bin which causes these problems.
Rainer
On Sep 6, 2011, at 08:41, Johannes Ruscheinski wrote:
On 5 September 2011 21:48, Ryan Schmidt wrote:
On Sep 5, 2011, at 23:40, Johannes Ruscheinski wrote:
After doing a sudo port uninstall mono I still get the same error.
My build still prints out:
base32cmd.o sha1cmd.o curl.o
Hi,
Here is what I get when I run sudo port -d selfupdate:
--- Updating the ports tree
DEBUG: Synchronizing ports tree(s)
Synchronizing local ports tree from file:///opt/mports/trunk/dports
DEBUG: /usr/bin/svn update --non-interactive /opt/mports/trunk/dports
DEBUG: changing euid/egid - current
On Sep 5, 2011, at 19:07, Johannes Ruscheinski wrote:
Here is what I get when I run sudo port -d selfupdate:
--- Updating the ports tree
DEBUG: Synchronizing ports tree(s)
Synchronizing local ports tree from file:///opt/mports/trunk/dports
DEBUG: /usr/bin/svn update --non-interactive
Hi Ryan,
On 5 September 2011 17:30, Ryan Schmidt ryandes...@macports.org wrote:
On Sep 5, 2011, at 19:07, Johannes Ruscheinski wrote:
Here is what I get when I run sudo port -d selfupdate:
--- Updating the ports tree
DEBUG: Synchronizing ports tree(s)
Synchronizing local ports tree from
On Sep 5, 2011, at 19:59, Johannes Ruscheinski wrote:
Creating port index in /opt/mports/trunk/dports
Failed to parse file archivers/arj/Portfile: invalid command name
get_canonical_archflags
Any idea what might be wrong and how to fix it?
This is normal, unfortunately, for users
Hi Ryan,
The next problem that I am running into now is:
...
Failed to parse file x11/mesa/Portfile: invalid command name
get_canonical_archflags
Total number of ports parsed: 1079
Ports successfully parsed: 0
Ports failed: 1079
Up-to-date ports skipped: 7126
On Sep 5, 2011, at 21:04, Johannes Ruscheinski wrote:
The next problem that I am running into now is:
[snip]
=== making all in src/registry2.0
/usr/bin/llvm-gcc-4.2 -c -DUSE_TCL_STUBS -DTCL_NO_DEPRECATED -g -O2 -W
-Wall -pedantic
-I/Library/Frameworks/Mono.framework/Versions/2.2/include
Hi Ryan,
After doing a sudo port uninstall mono I still get the same error.
My build still prints out:
base32cmd.o sha1cmd.o curl.o rmd160cmd.o sha256cmd.o readline.o uid.o
tracelib.o tty.o readdir.o pipe.o flock.o system.o mktemp.o realpath.o
-o Pextlib.dylib
On Sep 5, 2011, at 23:40, Johannes Ruscheinski wrote:
Hi Ryan,
After doing a sudo port uninstall mono I still get the same error.
My build still prints out:
base32cmd.o sha1cmd.o curl.o rmd160cmd.o sha256cmd.o readline.o uid.o
tracelib.o tty.o readdir.o pipe.o flock.o system.o mktemp.o
On Aug 16, 2011, at 5:01 PM, Eric Cronin wrote:
As far as I know, we don't link with Mono, so it shouldn't interfere
with selfupdate (it may interfere with building your own mono). I
wasn't sure which was failing for you...
We don't. But, the 3rd party Mono package installs in a location
On 16 Aug 2011, at 22:24, Andrew Long wrote:
snip/
The problem that I now have is to find out which application that, probably
several years and several machines ago, caused me to need to install mono
framework. But that isn't a problem for this list.
The application was usenext (the
On 15 Aug 2011, at 21:12, Ryan Schmidt wrote:
On Aug 15, 2011, at 13:36, Andrew Long wrote:
On 15 Aug 2011, at 18:52, Daniel J. Luke wrote:
snip/
The perl5 portgroup was just hours ago converted into a new unified format
which is probably going to cause some issues for a few moments
On Aug 16, 2011, at 4:14 PM, Andrew Long wrote:
For the other issue, please delete /Library/Frameworks/Mono.framework. You
don't need to install the MacPorts mono ports unless you have a need for
them; MacPorts isn't going to use them.
I left ports trying to build mono last night, and
On Tue, 16 Aug 2011 16:27:06 -0400, Daniel J. Luke wrote:
On Aug 16, 2011, at 4:14 PM, Andrew Long wrote:
For the other issue, please delete
/Library/Frameworks/Mono.framework. You don't need to install the
MacPorts mono ports unless you have a need for them; MacPorts isn't
going to use
On 16 Aug 2011, at 22:01, Eric Cronin wrote:
On Tue, 16 Aug 2011 16:27:06 -0400, Daniel J. Luke wrote:
On Aug 16, 2011, at 4:14 PM, Andrew Long wrote:
snip/
As far as I know, we don't link with Mono, so it shouldn't interfere
with selfupdate (it may interfere with building your own mono).
I've just tried to self update the ports tree from 2.0.0 to 2.0.1, and it has
failed *again* This has happened to me for over a year now; the symptoms is
that it tells me the following:-
Warning: port definitions are more than two weeks old, consider using selfupdate
--- Updating the ports
On Aug 15, 2011, at 1:42 PM, Andrew Long wrote:
Can someone please tell me where to look for the log, so I can have a try at
self-diagnosing, or perhaps tell me where to look for what the *real* problem
is?
I'm not sure where the log is (someone else probably knows and can tell you),
but
On 15 Aug 2011, at 18:52, Daniel J. Luke wrote:
On Aug 15, 2011, at 1:42 PM, Andrew Long wrote:
Can someone please tell me where to look for the log, so I can have a try at
self-diagnosing, or perhaps tell me where to look for what the *real*
problem is?
I'm not sure where the log is
On Aug 15, 2011, at 13:36, Andrew Long wrote:
On 15 Aug 2011, at 18:52, Daniel J. Luke wrote:
On Aug 15, 2011, at 1:42 PM, Andrew Long wrote:
Can someone please tell me where to look for the log, so I can have a try
at self-diagnosing, or perhaps tell me where to look for what the
On 15 Aug 2011, at 21:12, Ryan Schmidt wrote:
On Aug 15, 2011, at 13:36, Andrew Long wrote:
On 15 Aug 2011, at 18:52, Daniel J. Luke wrote:
snip/
The perl5 portgroup was just hours ago converted into a new unified format
which is probably going to cause some issues for a few moments
I just tried to selfupdate and it failed.
Further down you can see: configure: error: C compiler cannot create
executable!
I wonder what's going on here! I never saw stg like this.
---
.
.
.
sent 20068 bytes received 462257 bytes 107183.33 bytes/sec
total size is 54551356 speedup is 113.10
On Jun 17, 2010, at 13:07, Marko Käning wrote:
I just tried to selfupdate and it failed.
Further down you can see: configure: error: C compiler cannot create
executable!
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in
Hi Ryan,
Well, can your C compiler create executables? Is Xcode properly installed?
Check the config.log for more details!
up to now i never had problems with my macports and Xcode installation…
config.log says this:
---
configure:3002: checking for gcc
configure:3018: found
On Jun 17, 2010, at 2:58 PM, Marko Käning wrote:
Well, can your C compiler create executables? Is Xcode properly installed?
Check the config.log for more details!
up to now i never had problems with my macports and Xcode installation…
config.log says this:
---
configure:3002: checking for
This is what happens if I call CC from bash:
---
markos-imac:~ marko$ sudo bash
bash-3.2# CC
i686-apple-darwin10-gcc-4.2.1: no input files
---
___
macports-users mailing list
macports-users@lists.macosforge.org
On Jun 17, 2010, at 13:58, Marko Käning wrote:
Well, can your C compiler create executables? Is Xcode properly installed?
Check the config.log for more details!
up to now i never had problems with my macports and Xcode installation…
config.log says this:
---
configure:3002: checking
On 2010-6-18 05:05 , Daniel J. Luke wrote:
On Jun 17, 2010, at 2:58 PM, Marko Käning wrote:
Well, can your C compiler create executables? Is Xcode properly installed?
Check the config.log for more details!
up to now i never had problems with my macports and Xcode installation…
config.log
On 2010-6-18 05:09 , Marko Käning wrote:
This is what happens if I call CC from bash:
---
markos-imac:~ marko$ sudo bash
bash-3.2# CC
i686-apple-darwin10-gcc-4.2.1: no input files
---
You're just running /usr/bin/cc here because you're on a
case-insensitive filesystem. The CC environment
On Jun 17, 2010, at 14:14, Ryan Schmidt wrote:
You have now discovered that MacPorts itself does not use configure.cc when
selfupdating. See:
http://trac.macports.org/ticket/23095
That ticket says this was supposed to have been fixed If it's not, the
ticket should be re-opened.
On 2010-6-18 05:14 , Ryan Schmidt wrote:
On Jun 17, 2010, at 13:58, Marko Käning wrote:
Well, can your C compiler create executables? Is Xcode properly installed?
Check the config.log for more details!
up to now i never had problems with my macports and Xcode installation…
config.log
On Jun 17, 2010, at 14:29, Joshua Root wrote:
On 2010-6-18 05:14 , Ryan Schmidt wrote:
You made the changes described in UsingTheRightCompiler to discover when
ports are not using the configure.cc etc. variables. You have now discovered
that MacPorts itself does not use configure.cc when
On 2010-6-18 05:45 , Ryan Schmidt wrote:
On Jun 17, 2010, at 14:29, Joshua Root wrote:
On 2010-6-18 05:14 , Ryan Schmidt wrote:
You made the changes described in UsingTheRightCompiler to discover when
ports are not using the configure.cc etc. variables. You have now
discovered that
You're just running /usr/bin/cc here because you're on a
case-insensitive filesystem. The CC environment variable is probably
what you're after.
yep, you are right:
Last login: Thu Jun 17 21:06:47 on ttys001
markos-imac:~ marko$ CC
i686-apple-darwin10-gcc-4.2.1: no input files
markos-imac:~
But well, the question is now: How do I go on to get a working macports setup
again.
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
On Jun 17, 2010, at 14:50, Joshua Root wrote:
On 2010-6-18 05:45 , Ryan Schmidt wrote:
On Jun 17, 2010, at 14:29, Joshua Root wrote:
On 2010-6-18 05:14 , Ryan Schmidt wrote:
You made the changes described in UsingTheRightCompiler to discover when
ports are not using the configure.cc
On Jun 17, 2010, at 14:55, Marko Käning wrote:
But well, the question is now: How do I go on to get a working macports setup
again.
Read the last paragraph here:
http://lists.macosforge.org/pipermail/macports-users/2010-June/020623.html
___
On 2010-6-18 06:04 , Ryan Schmidt wrote:
On Jun 17, 2010, at 14:50, Joshua Root wrote:
On 2010-6-18 05:45 , Ryan Schmidt wrote:
On Jun 17, 2010, at 14:29, Joshua Root wrote:
On 2010-6-18 05:14 , Ryan Schmidt wrote:
You made the changes described in UsingTheRightCompiler to discover
On Jun 17, 2010, at 15:06, Joshua Root wrote:
On 2010-6-18 06:04 , Ryan Schmidt wrote:
Yes exactly. So #23095 is completely the relevant ticket, since it causes
selfupdate to not use gcc anymore but to use the specific appropriate
compiler.
My point is that 'gcc' would be fine had
Read the last paragraph here:
http://lists.macosforge.org/pipermail/macports-users/2010-June/020623.html
Oh, well, yes, I did that and it worked. Sorry, there were so many posts coming
in that I got confused about how to proceed. :)
___
Absolutely, since the point of the modifications described in
UsingTheRightCompiler is to sabotage gcc so that you can identify software
that is using gcc instead of the CC environment variable.
Ha, well, that's the reason for the whole confusion: I forgot to disable this
sabotage after I
On 2010-6-18 06:14 , Marko Käning wrote:
Absolutely, since the point of the modifications described in
UsingTheRightCompiler is to sabotage gcc so that you can identify software
that is using gcc instead of the CC environment variable.
Ha, well, that's the reason for the whole confusion: I
On Jun 17, 2010, at 15:14, Marko Käning wrote:
So, well, what does this mean for macports itself then?
Looks like there is still an issue here, since it would not install with your
sabotage...
Read:
http://lists.macosforge.org/pipermail/macports-users/2010-June/020629.html
lydia:Downloads pbw$ port selfupdate
--- Updating the ports tree
Error: Synchronization of the local ports tree failed doing rsync
Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the ports
tree: Synchronization of 1 source(s) failed
Any ideas?
Peter
On Dec 22, 2009, at 5:09 AM, Peter B. West wrote:
lydia:Downloads pbw$ port selfupdate
--- Updating the ports tree
Error: Synchronization of the local ports tree failed doing rsync
Error: /opt/local/bin/port: port selfupdate failed: Couldn't sync the ports
tree: Synchronization of 1
On 23/12/2009, at 12:57 AM, Daniel J. Luke wrote:
On Dec 22, 2009, at 5:09 AM, Peter B. West wrote:
lydia:Downloads pbw$ port selfupdate
--- Updating the ports tree
Error: Synchronization of the local ports tree failed doing rsync
Error: /opt/local/bin/port: port selfupdate failed:
On 23/12/2009, at 1:16 AM, Peter B. West wrote:
On 23/12/2009, at 12:57 AM, Daniel J. Luke wrote:
On Dec 22, 2009, at 5:09 AM, Peter B. West wrote:
lydia:Downloads pbw$ port selfupdate
--- Updating the ports tree
Error: Synchronization of the local ports tree failed doing rsync
Error:
On Dec 22, 2009, at 1:52 PM, Peter B. West wrote:
Make has gone away. I swear I didn't touch it. Could a normal Mac
software update have affected it?
gmake is there, so I'll add a softlink to make. Is gmake the
standard for MacPorts? What is the standard Xcode make?
On my system, ls -l
On 2009-12-23 02:16 , Peter B. West wrote:
lydia:local pbw$ sudo port upgrade outdated
Error: Unable to open port: can't read build.cmd: Failed to locate 'make'
in path: '/opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/sbin' or at
its MacPorts configuration time location, did you
On Mon, Mar 30, 2009 at 12:11:46AM -0500, Ryan Schmidt said:
On Mar 29, 2009, at 11:17, Jochen Küpper wrote:
after the announcement of 1.7.1 I run port selfupdate, however, this
bails -- could be due to gcc_select 4.3?
So, this is a Mac OS X 10.5.6 system with MacPorts 1.7.0. I have used
On 30.03.2009, at 08:05, Bryan Blackburn wrote:
On Mon, Mar 30, 2009 at 12:11:46AM -0500, Ryan Schmidt said:
On Mar 29, 2009, at 11:17, Jochen Küpper wrote:
after the announcement of 1.7.1 I run port selfupdate, however, this
bails -- could be due to gcc_select 4.3?
So, this is a Mac OS X
Hi,
after the announcement of 1.7.1 I run port selfupdate, however, this
bails -- could be due to gcc_select 4.3?
So, this is a Mac OS X 10.5.6 system with MacPorts 1.7.0. I have used
gcc_select to pick gcc-mp-4.3:
/opt/local/bin/gcc@ - /opt/local/bin/gcc-mp-4.3
Anyway, this is what
On Mar 29, 2009, at 11:17, Jochen Küpper wrote:
after the announcement of 1.7.1 I run port selfupdate, however,
this bails -- could be due to gcc_select 4.3?
So, this is a Mac OS X 10.5.6 system with MacPorts 1.7.0. I have
used gcc_select to pick gcc-mp-4.3:
/opt/local/bin/gcc@ -
Dimitri Hendriks wrote:
Hi,
I try to selfupdate macports on system 10.4.11,
but it fails; see error message below.
Does anyone know how to solve this?
No idea. Try installing from the disk image as a workaround.
Rainer
___
macports-users mailing
of the official information leads to rsync.
Eric Platon
--
View this message in context:
http://www.nabble.com/newbie-selfupdate-fails-tf4120147.html#a11755851
Sent from the MacPorts - Users mailing list archive at Nabble.com.
___
macports-users mailing list
I've been trying for a couple daze to get Darwin/MacPorts to install
but still have problems.
I followed the directions on the wiki
http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts
but when I get to the update step I get
$ sudo port -d selfupdate
DEBUG: Rebuilding
On Jun 17, 2007, at 22:03, andlabs wrote:
Hello. I need to install components with universal binary support,
and when I go to sudo port selfudate, here's what I get, put on a
pastebin: http://www.slexy.org/paste/3133
The relevant portion of that:
ld: Undefined symbols:
On Jun 18, 2007, at 10:22, Ryan Schmidt wrote:
On Jun 17, 2007, at 22:03, andlabs wrote:
Hello. I need to install components with universal binary support,
and when I go to sudo port selfudate, here's what I get, put on a
pastebin: http://www.slexy.org/paste/3133
The relevant portion of
On Jun 18, 2007, at 16:33, andlabs wrote:
Ryan Schmidt wrote:
It sounds to me like you have a rogue copy of readline, perhaps in
/usr/local/lib. If so, you need to at least move that out of the
way until
you install MacPorts, but MacPorts would probably be happier if
you would
delete it
I just got a new MacPro, and decided to give MacPorts a try this time
around. I would like to get it up and running, but right now it is looking
like I will have to go back to Fink. I didn't read the installation
instructions initially, so I installed the MacPorts binary before XCode and
X11,
Can you verify that X11User.pkg and X11SDK.pkg are in /Library/Receipts? It
looks like you
still don't have X11 properly installed.
On 5/4/07, Nathan Corvino [EMAIL PROTECTED] wrote:
I just got a new MacPro, and decided to give MacPorts a try this time
around. I would like to get it up and
1 - 100 of 106 matches
Mail list logo
