Rob Managan wrote:
> Since crazy things happen I will ask. I assume that you can run gcc
> from the command line?
Yes. Just tried it.
> Next question. What shell are you running? Mine is set to tcsh but
> newer Macs tend to run bash.
I typed "shell" and it came back: tcsh: shell: Command no
Christopher Barker wrote:
>David M. Cooke wrote:
>
>
>>Experience has shown that compiling Scipy with gcc 4.0 on a Mac doesn't
>>work (various really annoying problems with how Fortran libraries end up
>>being linked and so on). So it's suggested that you use 3.3.
>>
>>
>
>There is the same
Rob,
Here is the output of the 'make' command after my ./configure command.
Again the only difference from your successful output in the beginning
is my output shows g++ being used in place of gcc for you. But then in
line 5 (I think I counted right) an error of some type occurs. What the
he
Rob,
Here is the output of my ./configure command for SWIG Install. There
are some differences from your successful ouput.
Not sure you want to see all this, but if you have the time here are
where the differences in our configure output are. Lines marked with
"+" are in addition to lines yo
David M. Cooke wrote:
> Experience has shown that compiling Scipy with gcc 4.0 on a Mac doesn't
> work (various really annoying problems with how Fortran libraries end up
> being linked and so on). So it's suggested that you use 3.3.
There is the same problem with Fedora Core4, also using gcc 4.*,
David M. Cooke wrote:
>On Tue, Dec 06, 2005 at 05:41:21PM -0500, Louis Pecora wrote:
>
>
>>Rob Managan wrote:
>>
>>
>>
>>>PS the command to switch to gcc 3.3 seems to be
>>>
>>>'sudo gcc_select 3.3'
>>>
>>>Not sure if you had to do this with scipy or not.
>>>
>>>
>>H... I don't kno
On Tue, Dec 06, 2005 at 05:41:21PM -0500, Louis Pecora wrote:
> Rob Managan wrote:
>
> > PS the command to switch to gcc 3.3 seems to be
> >
> > 'sudo gcc_select 3.3'
> >
> > Not sure if you had to do this with scipy or not.
>
> H... I don't know about this one. What has this to do with Scip
Rob Managan wrote:
> PS the command to switch to gcc 3.3 seems to be
>
> 'sudo gcc_select 3.3'
>
> Not sure if you had to do this with scipy or not.
H... I don't know about this one. What has this to do with Scipy?
--
Cheers,
Lou Pecora
Code 6362
Naval Research Lab
Washington, DC 20375
Rob Managan wrote:
> [cut]
>
> [mangrove:~/Documents/My_Downloads/swig-1.3.27] managan% make
> make all-am
> depbase=`echo CParse/cscanner.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; \
> if gcc -DHAVE_CONFIG_H -I../Source/Include -I../Source/CParse
> -I../Source/Include -I../Source/DOH -I../Sou
Not having SWIG installed myself, I know that there's often issues
with different versions of GCC on OS X...you might want to verify in
the SWIG install docs (if they exist) and make sure your version of
GCC doesn't have some odd incompatibility with the SWIG source. Only
a guess, but still
I'm trying to install the SWIG
The README says to treat Mac OS X like a Unix (makes sense) and do the
following,
% ./configure
% make
% make install
./configure seemed to run ok. No errors that I could see in the long
print out.
When I try the first make I get,
louispec% mak
11 matches
Mail list logo
