--On November 18, 2011 2:17:26 AM -0800 Kyle Husmann
wrote:
On Thu, Nov 17, 2011 at 4:02 AM, Keith J. Schultz
wrote:
Just good programming practices and experience.
On Thu, Nov 17, 2011 at 6:41 PM, Mike
Alexander wrote:
I learned what I know about it from experience and talking to other
On Thu, Nov 17, 2011 at 4:02 AM, Keith J. Schultz wrote:
> Just good programming practices and experience.
On Thu, Nov 17, 2011 at 6:41 PM, Mike Alexander wrote:
> I learned what I know about it from experience and talking to other
> developers.
Are there some simple rules of thumb I can follo
--On November 17, 2011 12:32:58 AM -0800 Kyle Husmann
wrote:
On Thu, Nov 17, 2011 at 12:16 AM, Keith J. Schultz
wrote:
Yet, as long as you are aware what you are doing and the
"subtleties" of mixing compilers and libraries you are on the safe
side.
Where can one learn these "subtleties"? D
Hi Kyle,
Sorry, I do know of any courses or resources.
Just like there are no true resources for mixing languages.
Just good programming practices and experience.
regards
Keith.
Am 17.11.2011 um 09:32 schrieb Kyle Husmann:
> On Thu, Nov 17, 2011 at 12:16 AM, Keith J. Schultz
> wrote:
On Thu, Nov 17, 2011 at 12:16 AM, Keith J. Schultz wrote:
> Yet, as long as you are aware what you are doing and the
> "subtleties" of mixing compilers and libraries you are on the safe side.
Where can one learn these "subtleties"? Do you have any good resources
I can peruse?
Thanks,
Kyle
__
Hi All,
Generally, mixing compilers should not be a problem to the experienced
programmer
as long as s/he is aware that they are mixing them.
Naturally, using a single compiler is easier. Yet, as long as you are aware
what you are doing and the
"subtleties" of mixing compilers and libraries y
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
20 matches
Mail list logo
