This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug fortran/20500] f95 build fails on MacOSX 10.4 Tiger


------- Additional Comments From fca at mail dot cern dot ch  2005-03-17 17:49 -------
Subject: Re:  f95 build fails on MacOSX 10.4 Tiger

Hello,
  it is now failing with the following error. Any hint? Regards, Fed

mkdir .libs
/usr/local/gcc-4_0/build/gcc/xgcc -B/usr/local/gcc-4_0/build/gcc/ 
-B/usr/local/powerpc-apple-darwin8.0.0/bin/ 
-B/usr/local/powerpc-apple-darwin8.0.0/lib/ -isystem 
/usr/local/powerpc-apple-darwin8.0.0/include -isystem 
/usr/local/powerpc-apple-darwin8.0.0/sys-include -DHAVE_CONFIG_H -I. 
-I../../../libgfortran -I. -iquote../../../libgfortran/io -std=gnu99 -O2 
-g -O2 -c ../../../libgfortran/runtime/environ.c  -fno-common -DPIC -o 
.libs/environ.o
In file included from ../../../libgfortran/runtime/environ.c:35:
../../../libgfortran/libgfortran.h:63: error: conflicting types for 
'int8_t'
/usr/include/ppc/types.h:72: error: previous declaration of 'int8_t' was 
here
make[2]: *** [environ.lo] Error 1
make[1]: *** [all] Error 2
make: *** [all-target-libgfortran] Error 2



On Thu, 17 Mar 2005, Federico Carminati wrote:

> I was not complaining at all!! I know I am in uncharted land for the
> moment. It is churning away and I will let you know how it goes. Thanks
> for your help. Fed
> 
> On Thu, 17 Mar 2005, pinskia at gcc dot gnu dot org wrote:
> 
> > 
> > ------- Additional Comments From pinskia at gcc dot gnu dot org  2005-03-17 07:06 -------
> > (In reply to comment #4)
> > > Subject: Re:  f95 build fails on MacOSX 10.4 Tiger
> > > 
> > > Hello,
> > >    I rerun everything once more. The problem changed but now is 
> > > reproducible. When you are in
> > > 
> > > /usr/local/gcc-4_0/build/powerpc-apple-darwin8.0.0/ppc64/libgfortran
> > 
> > Oh, well considering darwin 8.0 (aka Tiger) is no released yet, what do you expect.  Anyways the correct 
> > way is to do --disable-multilib as you found out.  There is no way around this right now and is the 
> > expected way.
> > 
> > 
> 
> 



-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20500


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]