I upgraded from Tiger to Leopard, and GDC seems to be working fine. I've found two problems that don't seem to be related to GDC, but I don't know where to ask.

First, I can't build powerpc-apple-darwin9.0.0-gdc basically because I can't get GCC 4.0.x and 4.1.x to compile. With 4.1.2, I get:

gcc -c   -g -O2  -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.1.2/gcc -I../../gcc-4.1.2/gcc/. -I../../gcc-4.1.2/gcc/../include -I../../gcc-4.1.2/gcc/../libcpp/include     -I. -I. -I../../gcc-4.1.2/gcc -I../../gcc-4.1.2/gcc/. -I../../gcc-4.1.2/gcc/../include -I../../gcc-4.1.2/gcc/../libcpp/include ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c -o host-ppc-darwin.o
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:38: warning: 'struct sigaltstack' declared inside parameter list
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:38: warning: its scope is only this definition or declaration, which is probably not what you want
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:38: error: conflicting types for 'sigaltstack'
/usr/include/signal.h:89: error: previous declaration of 'sigaltstack' was here
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c: In function 'segv_handler':
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:71: error: 'struct __darwin_mcontext' has no member named 'ss'
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:120: error: 'struct __darwin_mcontext' has no member named 'es'
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:120: error: 'struct __darwin_mcontext' has no member named 'ss'
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c: In function 'darwin_rs6000_extra_signals':
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:134: warning: passing argument 1 of 'sigaltstack' from incompatible pointer type

It's not a GDC problem, as I also tried to compile GCC without GDC and got the same error. I also got the same with GCC 4.0.4. GCC 4.2.2 builds, but GDC doesn't support it.

The other problem is more like a small annoyance:

$ gdmd
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LC_ALL = (unset),
	LANG = "UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to the standard locale ("C").
gdc (GCC) 4.1.2 20070214 ( gdc 0.24, using dmd 1.021)
...

Every time I run gdmd I get those horrible first 6 lines, and I have no idea how to set up my system so that LANG = "es_EC.UTF-8" and that it shows up when I run "locale -a".

Sorry, but I had to get it out of my chest, even if I know those are not really issues with GDC. However, if anybody has a clue of how to solve them, I'd really appreciate it.

-- 
Carlos Santander Bernal

Commenting out line 38 of host-darwin.c may fix the problem.

Carlos Santander wrote:
> I upgraded from Tiger to Leopard, and GDC seems to be working fine. I've found two problems that don't seem to be related to GDC, but I don't know where to ask.
> 
> First, I can't build powerpc-apple-darwin9.0.0-gdc basically because I can't get GCC 4.0.x and 4.1.x to compile. With 4.1.2, I get:
> 
> gcc -c   -g -O2  -DIN_GCC -DCROSS_COMPILE  -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.1.2/gcc -I../../gcc-4.1.2/gcc/. -I../../gcc-4.1.2/gcc/../include -I../../gcc-4.1.2/gcc/../libcpp/include     -I. -I. -I../../gcc-4.1.2/gcc -I../../gcc-4.1.2/gcc/. -I../../gcc-4.1.2/gcc/../include -I../../gcc-4.1.2/gcc/../libcpp/include ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c -o host-ppc-darwin.o
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:38: warning: 'struct sigaltstack' declared inside parameter list
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:38: warning: its scope is only this definition or declaration, which is probably not what you want
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:38: error: conflicting types for 'sigaltstack'
> /usr/include/signal.h:89: error: previous declaration of 'sigaltstack' was here
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c: In function 'segv_handler':
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:71: error: 'struct __darwin_mcontext' has no member named 'ss'
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:120: error: 'struct __darwin_mcontext' has no member named 'es'
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:120: error: 'struct __darwin_mcontext' has no member named 'ss'
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c: In function 'darwin_rs6000_extra_signals':
> ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:134: warning: passing argument 1 of 'sigaltstack' from incompatible pointer type
> 
> It's not a GDC problem, as I also tried to compile GCC without GDC and got the same error. I also got the same with GCC 4.0.4. GCC 4.2.2 builds, but GDC doesn't support it.
> 
> The other problem is more like a small annoyance:
> 
> $ gdmd
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>     LC_ALL = (unset),
>     LANG = "UTF-8"
>     are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> gdc (GCC) 4.1.2 20070214 ( gdc 0.24, using dmd 1.021)
> ...
> 
> Every time I run gdmd I get those horrible first 6 lines, and I have no idea how to set up my system so that LANG = "es_EC.UTF-8" and that it shows up when I run "locale -a".
> 
> Sorry, but I had to get it out of my chest, even if I know those are not really issues with GDC. However, if anybody has a clue of how to solve them, I'd really appreciate it.
> 

David Friedman escribió:
> Commenting out line 38 of host-darwin.c may fix the problem.
>

Thanks, David, but it only solved the first error. I'm still getting:

gcc -c   -g -O2  -DIN_GCC   -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -Wmissing-format-attribute    -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.1.2/gcc -I../../gcc-4.1.2/gcc/. -I../../gcc-4.1.2/gcc/../include -I../../gcc-4.1.2/gcc/../libcpp/include     -I. -I. -I../../gcc-4.1.2/gcc -I../../gcc-4.1.2/gcc/. -I../../gcc-4.1.2/gcc/../include -I../../gcc-4.1.2/gcc/../libcpp/include ../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c -o host-ppc-darwin.o
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c: In function 'segv_handler':
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:71: error: 'struct __darwin_mcontext' has no member named 'ss'
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:120: error: 'struct __darwin_mcontext' has no member named 'es'
../../gcc-4.1.2/gcc/config/rs6000/host-darwin.c:120: error: 'struct __darwin_mcontext' has no member named 'ss'


-- 
Carlos Santander Bernal

Carlos Santander wrote:

> It's not a GDC problem, as I also tried to compile GCC without GDC and got the same error. I also got the same with GCC 4.0.4. GCC 4.2.2 builds, but GDC doesn't support it.

Why are you using the FSF GCC, rather than the Apple GCC ?

(just curious)

--anders

Anders F Björklund escribió:
> Carlos Santander wrote:
> 
>> It's not a GDC problem, as I also tried to compile GCC without GDC and got the same error. I also got the same with GCC 4.0.4. GCC 4.2.2 builds, but GDC doesn't support it.
> 
> Why are you using the FSF GCC, rather than the Apple GCC ?
> 
> (just curious)
> 
> --anders

I guess I'm used to it, I find it easier to use, and I get to use the same steps when I build on Ubuntu. Plus, http://www.opensource.apple.com/darwinsource/ doesn't show Leopard yet.

-- 
Carlos Santander Bernal

Anders F Björklund escribió:
> Carlos Santander wrote:
> 
>> It's not a GDC problem, as I also tried to compile GCC without GDC and got the same error. I also got the same with GCC 4.0.4. GCC 4.2.2 builds, but GDC doesn't support it.
> 
> Why are you using the FSF GCC, rather than the Apple GCC ?
> 
> (just curious)
> 
> --anders

I went on and downloaded http://www.opensource.apple.com/darwinsource/tarballs/other/gcc-5363.tar.gz, but I got the same errors I previously reported.

I guess I should've asked: what are the differences between the two GCCs? What benefits does the Apple version provide? I guess it fits better with the OS, or something like that, but I'd like to know specifics.

-- 
Carlos Santander Bernal

Carlos Santander wrote:

>> Why are you using the FSF GCC, rather than the Apple GCC ?
> 
> I guess I'm used to it, I find it easier to use, and I get to use the same steps when I build on Ubuntu. Plus, http://www.opensource.apple.com/darwinsource/ doesn't show Leopard yet.

Right, Xcode 2.4.1 and 3.0 has not been released (yet?).

I used FSF GCC 3.3.x on Panther, but eventually gave up
on FSF GCC 4.x.y with Tiger since it didn't really work.

But having both available would be great, so keep it up! :-)

> I guess I should've asked: what are the differences between the two
> GCCs? What benefits does the Apple version provide? I guess it fits
> better with the OS, or something like that, but I'd like to know specifics.

Some of it is language support (Objective-C++ for Tiger
and Objective-C 2.0 for Leopard), it also has more support
for old operating systems quirks - both Mac OS and NeXTstep.
And not sure if FSF GCC supports the SDKs and -isysroot yet ?

There's a lot of changes, the diff between them is now huge...

--anders

Anders F Björklund escribió:
> Carlos Santander wrote:
> 
>>> Why are you using the FSF GCC, rather than the Apple GCC ?
>>
>> I guess I'm used to it, I find it easier to use, and I get to use the same steps when I build on Ubuntu. Plus, http://www.opensource.apple.com/darwinsource/ doesn't show Leopard yet.
> 
> Right, Xcode 2.4.1 and 3.0 has not been released (yet?).
> 
> I used FSF GCC 3.3.x on Panther, but eventually gave up
> on FSF GCC 4.x.y with Tiger since it didn't really work.
> 
> But having both available would be great, so keep it up! :-)
> 
>> I guess I should've asked: what are the differences between the two
>> GCCs? What benefits does the Apple version provide? I guess it fits
>> better with the OS, or something like that, but I'd like to know specifics.
> 
> Some of it is language support (Objective-C++ for Tiger
> and Objective-C 2.0 for Leopard), it also has more support
> for old operating systems quirks - both Mac OS and NeXTstep.
> And not sure if FSF GCC supports the SDKs and -isysroot yet ?
> 
> There's a lot of changes, the diff between them is now huge...
> 
> --anders

Well, I'm a Mac OS X user, not Mac OS or NeXTstep (what a weird spellng...), so I don't care about that. I don't know what -isysroot is; I remember seeing it somewhere, but I don't think I've missed it. And I don't know what you mean by supporting the SDKs. I've used -framework to use Carbon, Cocoa, Mono, and perhaps others, and they've worked just fine. Am I missing something?

-- 
Carlos Santander Bernal

Carlos Santander wrote:

> I don't know what -isysroot is; I remember seeing it somewhere, but I don't think I've missed it. And I don't know what you mean by supporting the SDKs.

SDKs are what Apple use to support cross-developing between OS releases.
http://developer.apple.com/documentation/DeveloperTools/Conceptual/cross_development/

It also supports cross-compiling between the architectures, in order to
make Universal Binaries but I'm sure you were aware of that already...

--anders

Carlos Santander skrev:

>> Some of it is language support (Objective-C++ for Tiger
>> and Objective-C 2.0 for Leopard), it also has more support
>> for old operating systems quirks - both Mac OS and NeXTstep.
> 
> Well, I'm a Mac OS X user, not Mac OS or NeXTstep (what a weird spellng...), so I don't care about that. 

Same difference, Mac OS X is a merge between the two older ones.

(e.g. Mac OS would be Carbon API and NeXTstep would be Cocoa API)

--anders