On Apr 2, 2010, at 5:48 AM, Ryan Schmidt wrote:
> On Apr 2, 2010, at 06:19, Yves S. Garret wrote:
>
>> I downloaded the source. I configured it and compiled it.
>>
>> % ./configure && make
>>
>> Then the install...
>>
>> % sudo make install
>>
>> Everything was as it should, then I modified
Fon's question got me thinking. While /opt/local/bin precedes /usr/
bin in my $PATH, when I `which gcc` I get /usr/bin/gcc. Huh? Since
I've never had insurmountable compiler glitches, I'd lost track of how
I'd worked around previous issues. I have created a mess! In /usr/
bin/ I've got t
$49 for the Family Pack.
Timothy Goins
ohc...@kitcarson.net
On Jun 8, 2009, at 7:26 PM, William Davis wrote:
On Jun 8, 2009, at 5:26 PM, Scott Haneda wrote:
Are you sure about that cost? I was reading http://www.macworld.com/article/140897/2009/06/keynote.html
and the price noted
I, too, am experiencing some unpleasantries in trying to install gnucash. My first attempt installed a bunch of dependencies but crashed in the end. Noted Corey's issues with goffice, so I ran a port install goffice. No problems; it installed without complaint. Then I did a port install gnucash
I am definitely not a MacPorts guru (although I am comfortable with
X11 and Unix in general). I've seen error flows like yours before.
My guess is that the port is looking for gcc in /usr/bin and not
finding it (which was the case with one of my failed ports—I had the
gcc-4.0 compiler but
Here's what I get when I try to get port_cutleaves:
t...@cotopaxi:~$ sudo port install port_cutleaves
Error: Port port_cutleaves not found
On Feb 4, 2009, at 8:50 AM, Rainer Müller wrote:
S. M. Ibrahim (Lavlu) wrote:
i am using macports for last 6 months. recently when i was cleaning
my
hdd
Thanks, Joel, that worked. However, I ran into two problems that I
found interesting. When I ran "t...@cotopaxi:~$ sudo port clean --all
vim" the call returned "/opt/local/var/macports/build/
_opt_local_var_macports_sources_rsync
.macports.org_release_ports_editors_vim/work/.macports.vim.st
When I attempt to *upgrade outdated* openssl and vim fail; all other
ports upgrade. Here is the error stream for the vim failure:
t...@cotopaxi:~$ sudo port upgrade vim
---> Building vim
Error: Target org.macports.build returned: shell command " cd "/opt/
local/var/macports/build/
_opt_loca
I get exactly the same error output; however, I'm upgrading (or trying
to) from "vim @7.2.021_0 (active)". Also lots of xorg upgrades that
succeed and a python that doesn't. Frustrating! openssl and vim are
the only active ports that are outdated and won't upgrade on my system.
Tim
On Ja
Here's what I got when I installed Apache2.0 on my Mac Pro running
10.5.6 (being a dodo, I am wondering why my port command fetched from http://distfiles.macports.org/apache2
rather than from http://www.ibiblio.org/pub/mirrors/apache/httpd):
t...@cotopaxi:~$ sudo port install apache2
Password
I am having a problem upgrading three of my active but outdated ports
[10.5.6; Xcode 3.1; user/bin/gcc-4.0]; I am much more familiar with
the configure-make-make install routine and am new to MacPorts.
Running ~$ sudo port outdated produces the following:
The following installed ports are ou
I am in the process of 'upgrading' my outdated ports. When I got to
'vim' I discovered that 44 patches needed to be applied (7.2.021 to
7.2.065). However, when I ran 'sudo port upgrade vim' it spat out the
following:
--->Building vim
Error: Target org.macports.build returned: shell comman
I encountered this problem compiling 4.3. In /usr/bin I had the gcc
executable but no gcc-4.0 file, so I created a link (sudo ln -s /usr/
bin/gcc /usr/bin/gcc-4.0). The -s is unnecessary, I believe, but I
did it because my symbolic links show up in a different color.
What I don't know why
I Googled the guy, John Korchok. As enterprising character trying to
hawk his music. I blocked him on my 3rd party firewall. Also
forwarded his email to [EMAIL PROTECTED]
—Tim
On Oct 22, 2008, at 10:54 AM, Matthew Hippely wrote:
I don't know how much it really helps but when I do the fo
14 matches
Mail list logo