Firebird sql port

2014-02-08 Thread julien Touche
Hello, I'm trying to make a port for Firebird SQL database and the corresponding perl bindings but I got a problem. While I can manage to compile it outside of macports, it doesn't work though macports architecture See https://trac.macports.org/ticket/42128 I had a discussion with the binary pa

Re: Issue upgrading from 2.2.0 to 2.2.1 - Error: llvm-3.1 is not supported on Mavericks or later.

2014-02-08 Thread Ryan Schmidt
On Feb 8, 2014, at 12:43, William H. Magill wrote: > The error is pretty self explanatory. > > My question is -- did I do something wrong or is this "just" a Perl5 issue? > > > > outpost> sudo port selfupdate > ---> Updating MacPorts base sources using rsync > MacPorts base version 2.2.0 i

Re: Issue upgrading from 2.2.0 to 2.2.1 - Error: llvm-3.1 is not supported on Mavericks or later.

2014-02-08 Thread William H. Magill
On Feb 8, 2014, at 1:47 PM, Jeremy Lavergne wrote: > How did you get llvm-3.1 installed to begin with? Sounds like you upgraded > your OS. > https://trac.macports.org/wiki/Migration Back when Mavericks came out back in ?the fall? I thought I had gone through the migration process after the h

Re: Issue upgrading from 2.2.0 to 2.2.1 - Error: llvm-3.1 is not supported on Mavericks or later.

2014-02-08 Thread Jeremy Lavergne
How did you get llvm-3.1 installed to begin with? Sounds like you upgraded your OS. https://trac.macports.org/wiki/Migration On Feb 8, 2014, at 13:43, William H. Magill wrote: > Error: llvm-3.1 is not supported on Mavericks or later. > Error: org.macports.fetch for port llvm-3.1 returned: unsup

Issue upgrading from 2.2.0 to 2.2.1 - Error: llvm-3.1 is not supported on Mavericks or later.

2014-02-08 Thread William H. Magill
The error is pretty self explanatory. My question is -- did I do something wrong or is this "just" a Perl5 issue? outpost> sudo port selfupdate ---> Updating MacPorts base sources using rsync MacPorts base version 2.2.0 installed, MacPorts base version 2.2.1 downloaded. ---> Updating the po

Re: "port echo requested" dupes

2014-02-08 Thread Brandon Allbery
On Sat, Feb 8, 2014 at 9:59 AM, Samuel Halliday wrote: > If I issue a “port echo requested” there are always tonnes of dupes in > there… and I have to uninstall specific versions. > > How can I easily purge all old copies of ports so that they don’t show up > here? > sudo port uninstall inactive

"port echo requested" dupes

2014-02-08 Thread Samuel Halliday
Hi all, If I issue a “port echo requested” there are always tonnes of dupes in there… and I have to uninstall specific versions. How can I easily purge all old copies of ports so that they don’t show up here? -- Best regards, Samuel Halliday ___