Hi everyone, first post...
I've been trying for a while to get the IT department at work to open up port
873 so that macports could work there, but to no avail. Then I saw a post on
the mailing list that explained how to collect the distfiles and other stuff
needed to run macports without an in
On Mar 21, 2010, at 22:59, Daniel J. Luke wrote:
On Mar 21, 2010, at 3:33 PM, Kok-Yong Tan wrote:
No, what I meant is that I had to "manually" install ruby by doing
"port -v install ruby" before doing "port -v install subversion"
and that "port -v install subversion" didn't seem to automati
On Mar 21, 2010, at 3:33 PM, Kok-Yong Tan wrote:
> No, what I meant is that I had to "manually" install ruby by doing "port -v
> install ruby" before doing "port -v install subversion" and that "port -v
> install subversion" didn't seem to automatically chain to an installation of
> ruby. If I
On Mar 21, 2010, at 4:58 PM, Norman Khine wrote:
> hello, is there a macport for xvidcap?
> thanks
"port search xvidcap" returns nothing. So no. You can file a trac ticket
requesting it [1], but unless you actually submit a portfile, don't expect much
to happen. Even the submissions queue [2]
Hello, I wasn't sure whether I was suppose wait for something to be done that
was suppose to be done, or install the patch, so I decided to install the
batch, and, the following happened after downloading what I thought to be the
proper patch:
---
On Mar 21, 2010, at 19:14 , Mark Hattam wrote:
I don't understand which port was skipped in the upgrading ... all
four items that were outdated now appear to be "active". If I run a
subsequent "port outdated" nothing needs doing.
(...)
Warning: Skipping upgrade since libtool 2.2.6b_1 >= libto
I don't understand which port was skipped in the upgrading ... all four items
that were outdated now appear to be "active". If I run a subsequent "port
outdated" nothing needs doing.
iMac:~ mark$ sudo port outdated
The following installed ports are outdated:
bash 4.0.3
hello, is there a macport for xvidcap?
thanks
--
%>>> "".join( [ {'*':'@','^':'.'}.get(c,None) or
chr(97+(ord(c)-83)%26) for c in ",adym,*)&uzq^zqf" ] )
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailm
On Mar 21, 2010, at 13:13, Ryan Schmidt wrote:
On Mar 21, 2010, at 00:52, Kok-Yong Tan wrote:
On Mar 20, 2010, at 16:22, Rainer Müller wrote:
sudo port deactivate cyrus-sasl2
sudo port clean cyrus-sasl2
sudo port upgrade cyrus-sasl2
Many thanks for the reply. I did as you recommended
On Mar 21, 2010, at 11:22, Daniel J. Luke wrote:
On Mar 21, 2010, at 1:52 AM, Kok-Yong Tan wrote:
I noticed that despite it also making the same complaint about
ruby being too outdated for subversion 1.6.5 to use, the build had
continued until it crapped out about an hour later instead of
Dear users,
I've installed g95 and netcdf in two macs. The first is a MacBook Pro
(Intel 2.53 GHz) with Mac OS X 10.6.2.
After installation I obtain:
$port installed
g95 @0.91_2+darwin_10+gcc42 (active)
netcdf @4.1_1+g95 (active)
The second mac is PowerPC G5, 2.5 GHz with Mac OS X 10.5.8. The
On Mar 21, 2010, at 00:52, Kok-Yong Tan wrote:
> On Mar 20, 2010, at 16:22, Rainer Müller wrote:
>
>> sudo port deactivate cyrus-sasl2
>> sudo port clean cyrus-sasl2
>> sudo port upgrade cyrus-sasl2
>
> Many thanks for the reply. I did as you recommended and that got me over
> that obstacle
On Mar 21, 2010, at 1:52 AM, Kok-Yong Tan wrote:
> I noticed that despite it also making the same complaint about ruby being
> too outdated for subversion 1.6.5 to use, the build had continued until it
> crapped out about an hour later instead of acknowledging the critical
> dependency on ruby
On Mar 20, 2010, at 22:20, Kastus Shchuka wrote:
> On Mar 20, 2010, at 6:32 PM, Ryan Schmidt wrote:
>
>> On Mar 20, 2010, at 14:03, Kastus Shchuka wrote:
>>
>>> I forgot to mention that despite libevent mentioned in conflicts lint in
>>> the qt4-mac port file, port command did not produce any e
On Mar 21, 2010, at 03:50, Wolf Drechsel wrote:
> I failed to build curl, cc'ed that ticket:
>
> http://trac.macports.org/ticket/24059
>
> As a workaround it is suggested to pass --with-random=/dev/urandom manually
> to configure. As on my machine /dev/urandom exists, I dont have to carry out
Hi,
I failed to build curl, cc'ed that ticket:
http://trac.macports.org/ticket/24059
As a workaround it is suggested to pass --with-random=/dev/urandom
manually to configure. As on my machine /dev/urandom exists, I dont
have to carry out that test. I did fetch, checksum, extract patch
ma
On 2010-3-21 09:49 , Michael_google gmail_Gersten wrote:
> Will macports ever support a three-way universal, for the following systems:
>
> 1. PPC/10.5.8
> 2. i386/10.5.8
> 3. x64/10.6.2
>
> Obviously, 10.5.8 systems cannot compile for case #3, but a 10.6.2
> system should (in theory) be able to
17 matches
Mail list logo
