On Dec 20, 2013, at 05:01, Jerry wrote:
> On Dec 20, 2013, at 3:43 AM, Ryan Schmidt wrote:
>
>> On Dec 20, 2013, at 04:36, Jerry wrote:
>>
>>> Also: Can you comment on Michael's suggestion?
>>
>> Michael suggested you install the octave port with the variants you
>> need/want. You appear to h
On Dec 20, 2013, at 13:55, David Mandelberg wrote:
> I'm trying to port some software to Mac, and it uses mysql and odbc. The
> mysql-connector-odbc port depends on mysql5, but I also had an issue with
> mysql5 for which I was told to use another mysql package:
> https://trac.macports.org/tick
Hi,
I'm trying to port some software to Mac, and it uses mysql and odbc.
The mysql-connector-odbc port depends on mysql5, but I also had an issue
with mysql5 for which I was told to use another mysql package:
https://trac.macports.org/ticket/41863
Is there another port for the MySQL ODBC con
On Dec 20, 2013, at 3:43 AM, Ryan Schmidt wrote:
>
> On Dec 20, 2013, at 04:36, Jerry wrote:
>
>> On Dec 20, 2013, at 2:38 AM, Ryan Schmidt wrote:
>>
>>> I don’t know how far the problem reaches.
>>>
>>> I did see in your output that you’re using gcc45. Any particular reason?
>>> The defaul
On Dec 20, 2013, at 04:36, Jerry wrote:
> On Dec 20, 2013, at 2:38 AM, Ryan Schmidt wrote:
>
>> I don’t know how far the problem reaches.
>>
>> I did see in your output that you’re using gcc45. Any particular reason? The
>> default is now gcc48; you could try that instead. That may help; parts
On Dec 20, 2013, at 2:38 AM, Ryan Schmidt wrote:
>
> On Dec 19, 2013, at 15:00, Jerry wrote:
>
>> On Dec 19, 2013, at 1:40 AM, Ryan Schmidt wrote:
>>
>>> MacPorts should not be supplying -arch flags to compilers like fortran that
>>> do not understand them.
>>>
>>> MacPorts bases its decisi
On Dec 19, 2013, at 2:49 PM, Michael Dickens wrote:
> Hi Jerry - I just updated my 10.9 boot to 10.9.1, then updated MacPorts
> to latest; Xcode did not change. Then uninstalled octave and reinstalled
> it. No issues for me. Just a guess: Your MacPorts install is out of
> date. Try:
> {{{
> su
On 12/20/13 04:39, Ryan Schmidt wrote:
On Dec 20, 2013, at 03:36, Kok-Yong Tan wrote:
I just tried the "port clean --dist curl" and then tried to redo
the "port -v install git-core +svn +doc +bash_completion +gitweb"
and slammed into the same error again.
The port that failed was not curl bu
On Dec 20, 2013, at 03:36, Kok-Yong Tan wrote:
> I just tried the "port clean --dist curl" and then tried to redo the "port -v
> install git-core +svn +doc +bash_completion +gitweb" and slammed into the
> same error again.
The port that failed was not curl but curl-ca-bundle, so that is the po
On Dec 19, 2013, at 15:00, Jerry wrote:
> On Dec 19, 2013, at 1:40 AM, Ryan Schmidt wrote:
>
>> MacPorts should not be supplying -arch flags to compilers like fortran that
>> do not understand them.
>>
>> MacPorts bases its decision on whether -arch flags are supported on the
>> value of conf
Sorry about that.
I just tried the "port clean --dist curl" and then tried to redo the
"port -v install git-core +svn +doc +bash_completion +gitweb" and
slammed into the same error again. I wonder how one can check if the
curl sources are indeed corrupt?
On 12/19/13 21:40, Jeremy Lavergne w
On Dec 19, 2013, at 20:40, Jeremy Lavergne wrote:
> Kok-Yong Tan wrote:
>
>> ---> Verifying checksum(s) for curl-ca-bundle
>> DEBUG: Executing org.macports.checksum (curl-ca-bundle)
>> ---> Checksumming curl-7.19.7.tar.bz2
>> DEBUG: Correct (md5) checksum for curl-7.19.7.tar.bz2
>> DEBUG: Corr
12 matches
Mail list logo
