On Nov 16, 2011, at 23:00, Kyle Husmann wrote:
>> Ok. What solution are you advocating?
>
> Sorry, I don't have any solutions at the moment. Frankly this is out
> of my expertise. I like your idea to mix and match the fsf fortran
> compiler with the osx toolchain though.
>
> Still, it would be
> Ok. What solution are you advocating?
Sorry, I don't have any solutions at the moment. Frankly this is out
of my expertise. I like your idea to mix and match the fsf fortran
compiler with the osx toolchain though.
Still, it would be nice to give the user the option to maintain an
entire macport
--On November 16, 2011 10:41:15 PM -0600 Ryan Schmidt
wrote:
Is it only Apple gcc that's a problem? If so, does that mean the
problem is already resolved when using Xcode 4 on Lion and Snow
Leopard, where the default compiler is not gcc, but Apple llvm-gcc or
Apple clang (depending on Xcode ve
On Nov 16, 2011, at 21:56, Kyle Husmann wrote:
> On Wed, Nov 16, 2011 at 7:44 PM, Ryan Schmidt wrote:
>> That sounds like a possibility. But my understand was that *usually* the
>> mismatched stdc library versions aren't a problem, but that in some rare
>> cases it is.
>
> I think if apple shipp
On Wed, Nov 16, 2011 at 7:44 PM, Ryan Schmidt wrote:
> That sounds like a possibility. But my understand was that *usually* the
> mismatched stdc library versions aren't a problem, but that in some rare
> cases it is.
I think if apple shipped with a gnu stdc, everything would be just
fine becau
> I'm not sure what order that would upgrade the ports in. It might not be in
> dependency order. Also, I think this will probably rebuild ports multiple
> times, once for each time it appears as a dependency.
>
> You're better off uninstalling all ports, then installing the ports you want.
So
On Nov 16, 2011, at 21:33, Kyle Husmann wrote:
>> But of course many of the science ports are not islands
>> -- they have dependencies on other "regular" software
>> like graphics libraries, which we don't put compiler variants in.
>
> Right. Does this mean that any science library that depends
On Nov 16, 2011, at 21:37, Jeremy Lavergne wrote:
>> How do I
>> force compilation of all the packages?
>
> Something like:
> sudo port -f -s upgrade installed
I'm not sure what order that would upgrade the ports in. It might not be in
dependency order. Also, I think this will probably rebuild
> How do I
> force compilation of all the packages?
Something like:
sudo port -f -s upgrade installed
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org
On Wed, Nov 16, 2011 at 7:34 PM, Kyle Husmann wrote:
> Also, I've found another hitch when adding the
> "configure.compiler=macports-gcc-4.4" command: It doesn't
> automatically rebuild ports that have binary distributions. How do I
> force compilation of all the packages?
port -s
___
On Wed, Nov 16, 2011 at 7:33 PM, Kyle Husmann wrote:
> On Wed, Nov 16, 2011 at 7:06 PM, Ryan Schmidt wrote:
>>
>> On Nov 16, 2011, at 20:40, Kyle Husmann wrote:
>>
>>> I'm wondering if it is possible to build the entire macports tree with
>>> a custom gcc version. (I would like to use gcc44). Her
On Wed, Nov 16, 2011 at 7:06 PM, Ryan Schmidt wrote:
>
> On Nov 16, 2011, at 20:40, Kyle Husmann wrote:
>
>> I'm wondering if it is possible to build the entire macports tree with
>> a custom gcc version. (I would like to use gcc44). Here's why I think
>> I need to do this:
>>
>> I've installed oc
On Nov 16, 2011, at 20:40, Kyle Husmann wrote:
> I'm wondering if it is possible to build the entire macports tree with
> a custom gcc version. (I would like to use gcc44). Here's why I think
> I need to do this:
>
> I've installed octave-devel from the macports tree, which uses gcc44.
> I have
Hi all,
I'm wondering if it is possible to build the entire macports tree with
a custom gcc version. (I would like to use gcc44). Here's why I think
I need to do this:
I've installed octave-devel from the macports tree, which uses gcc44.
I have have some programs (outside of macports) that link a
Hello,
> 1) The installation stops when trying to install okular with the following
> message
>
> "Error: Target org.macports.configure returned: Poppler must be installed
> with +qt4 and +quartz variants
> Error: Failed to install okular"
As said in previous mails, all dependencies must be i
On Wed, Nov 16, 2011 at 9:18 AM, Peng Yu wrote:
> ls --color=auto on ubuntu distinguishes broken and good links. But it
> seems that the same command does not do so using the macports version.
The color output for the ls command is set by some variables in your
shell. The LSCOLORS and CLICOLOR
On 11/15/11 5:35 PM, Ryan Schmidt wrote:
> On Nov 15, 2011, at 18:49, David Evans wrote:
>
>> unixODBC is a dependency of qt4-x11
> qt4-x11 is way old, and I had hoped obsolete. I believe the plan had been to
> make an +x11 variant of qt4-mac, but it's currently commented out.
>
Agreed, but the po
Hi,
ls --color=auto on ubuntu distinguishes broken and good links. But it
seems that the same command does not do so using the macports version.
Is there a way to mimic the behavior on ubuntu?
/opt/local/libexec/gnubin/ls
--
Regards,
Peng
___
macport
> Is maxima the only port so affected or are there others?
FWIW: this is the only one that I know.
Thank you!___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
On Nov 16, 2011, at 03:02, C D wrote:
> You need to uninstall and reinstall Maxima after each upgrade of sbcl (unless
> Maxima was itself upgraded, which happens only if a new version of Maxima was
> released): your present installation of Maxima uses a bytecode that was
> compiled with the pr
> I issued the following commands:
> sudo port selfupdate
> sudo port upgrade outdated
> I got this after typing `maxima':
> fatal error encountered in SBCL pid 812:
> can't load .core for different runtime, sorry
>
>
> Welcome to LDB, a low-level debugger for the Lisp runtime environment.
> ldb>
21 matches
Mail list logo
