www.digitalmars.com         C & C++   DMDScript  

D.gnu - Mac OS X 10.5

reply Carlos Santander <csantander619 gmail.com> writes:
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
Oct 28 2007
next sibling parent reply David Friedman <dvdfrdmn users.ess-eff.net> writes:
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.
 

Oct 28 2007
parent Carlos Santander <csantander619 gmail.com> writes:
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
Oct 29 2007
prev sibling next sibling parent reply =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:
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
Oct 29 2007
next sibling parent reply Carlos Santander <csantander619 gmail.com> writes:
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
Oct 29 2007
parent reply =?ISO-8859-1?Q?Anders_F_Bj=F6rklund?= <afb algonet.se> writes:
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
Oct 30 2007
parent reply Carlos Santander <csantander619 gmail.com> writes:
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
Oct 30 2007
next sibling parent reply =?UTF-8?B?QW5kZXJzIEYgQmrDtsKacmtsdW5k?= <afb algonet.se> writes:
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
Oct 30 2007
parent Carlos Santander <csantander619 gmail.com> writes:
Anders F Bj├Â┬Ürklund escribi├│:
 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/Conceptua /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

I still fail to see what the big difference is between the two, sorry. -- Carlos Santander Bernal
Oct 31 2007
prev sibling parent =?UTF-8?B?QW5kZXJzIEYgQmrDtsKacmtsdW5k?= <afb algonet.se> writes:
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
Oct 30 2007
prev sibling parent Carlos Santander <csantander619 gmail.com> writes:
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
Oct 29 2007
prev sibling next sibling parent reply Dave Cheney <dave cheney.net> writes:
Hi

I was able to build a workable gdc 0.24 from the darwin ports archive 
by removing the reference to c++ in the configure.args section of this 
file

/opt/local/var/macports/sources/rsync.macports.org/release/ports/lang/gdc/Portfile

and 

then installing with

sudo port install gdc

This builds gdc 0.24 against gcc 4.1.2.

During operation gdc generates numerous warnings

/var/folders/-9/-91jp5FuE3GuA1DJFsQFLE+++TI/-Tmp-//cckNieF8.s:658:indirect 
jmp without `*'
/var/folders/-9/-91jp5FuE3GuA1DJFsQFLE+++TI/-Tmp-//cckNieF8.s:673:indirect 
jmp without `*'
/var/folders/-9/-91jp5FuE3GuA1DJFsQFLE+++TI/-Tmp-//cckNieF8.s:692:indirect 
jmp without `*'
/var/folders/-9/-91jp5FuE3GuA1DJFsQFLE+++TI/-Tmp-//cckNieF8.s:707:indirect 
jmp without `*'

but produces a workabout executable

I haven't had any luck compiling gdc from svn yet as the only apple 
compiler sources available are gcc-5363, which is from the tiger 
series. It appears that the gcc built into Leopard is build from 
revision 5465 which has just been released now. If I have any luck 
building against leopards gcc i'll report it to this list

Cheers

Dave
Oct 31 2007
next sibling parent reply =?UTF-8?B?QW5kZXJzIEYgQmrDtsKacmtsdW5k?= <afb algonet.se> writes:
Dave Cheney wrote:

 I haven't had any luck compiling gdc from svn yet as the only apple 
 compiler sources available are gcc-5363, which is from the tiger series. 
 It appears that the gcc built into Leopard is build from revision 5465 
 which has just been released now. If I have any luck building against 
 leopards gcc i'll report it to this list

As reported earlier, the check in setup-gcc.sh for "Apple Computer" doesn't match the new "Apple the Phone company", errr, "Apple Inc.": grep version_string gcc/version.c | grep -qF '(Apple Computer, Inc.' const char version_string[] = "4.0.1 (Apple Inc. build 5465)"; It should instead be: if grep -q 'Apple version' gcc/version.c; then so that the correct GCC patch is used, and build_gcc needs fixing up. But then the build is on its way, let's see whether it completes/works. (I don't think there are too many differences actually, but we'll know) --anders
Oct 31 2007
next sibling parent reply Dave Cheney <dave cheney.net> writes:
On 2007-10-31 23:58:01 +1100, Anders F Bjֆrklund <afb algonet.se> said:

 It should instead be: if grep -q 'Apple version' gcc/version.c; then
 so that the correct GCC patch is used, and build_gcc needs fixing up.
 
 But then the build is on its way, let's see whether it completes/works.
 (I don't think there are too many differences actually, but we'll know)
 
 --anders

My compile consistently bombs out at this line gcc -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic -Wno-long-long -Wno-variadic-macros -Wold-style-definition -mdynamic-no-pic -DHAVE_CONFIG_H -o gdc \ d/d-spec.o d/d-gcc.o version.o prefix.o intl.o darwin-driver.o ../libcpp/libcpp.a ./../intl/libintl.a /usr/lib/libiconv.dylib ../libiberty/libiberty.a Undefined symbols: "_need_pthreads", referenced from: _need_pthreads$non_lazy_ptr in d-spec.o I have a vague recollection of reading that Leopard included some changes to the pthread libraries (but I'm unable to find the reference again) so possibly this symbol has moved location ? Cheers Dave
Oct 31 2007
parent =?UTF-8?B?QW5kZXJzIEYgQmrDtsKacmtsdW5k?= <afb algonet.se> writes:
Dave Cheney skrev:

 My compile consistently bombs out at this line
 
 gcc   -g -DENABLE_CHECKING -DENABLE_ASSERT_CHECKING -DIN_GCC   -W -Wall 
 -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -pedantic 
 -Wno-long-long -Wno-variadic-macros -Wold-style-definition   
 -mdynamic-no-pic -DHAVE_CONFIG_H  -o gdc \
     d/d-spec.o d/d-gcc.o version.o prefix.o intl.o darwin-driver.o 
 ../libcpp/libcpp.a ./../intl/libintl.a /usr/lib/libiconv.dylib  
 ../libiberty/libiberty.a
 Undefined symbols:
  "_need_pthreads", referenced from:
      _need_pthreads$non_lazy_ptr in d-spec.o

AFAIK, that's just a failed patch... diff -cr gcc-orig/gcc.c gcc/gcc.c *** gcc-orig/gcc.c Sat Jan 21 13:38:48 2006 --- gcc/gcc.c Thu Mar 1 10:27:25 2007 *************** *** 134,139 **** --- 134,142 ---- /* Flag set by cppspec.c to 1. */ int is_cpp_driver; + /* Flag set by drivers needing Pthreads. */ + int need_pthreads; + /* Flag saying to pass the greatest exit code returned by a sub-process to the calling program. */ static int pass_exit_codes; --anders
Oct 31 2007
prev sibling parent reply Carlos Santander <csantander619 gmail.com> writes:
Anders F Bj├Â┬Ürklund escribi├│:
 Dave Cheney wrote:
 
 I haven't had any luck compiling gdc from svn yet as the only apple 
 compiler sources available are gcc-5363, which is from the tiger 
 series. It appears that the gcc built into Leopard is build from 
 revision 5465 which has just been released now. If I have any luck 
 building against leopards gcc i'll report it to this list

As reported earlier, the check in setup-gcc.sh for "Apple Computer" doesn't match the new "Apple the Phone company", errr, "Apple Inc.": grep version_string gcc/version.c | grep -qF '(Apple Computer, Inc.' const char version_string[] = "4.0.1 (Apple Inc. build 5465)"; It should instead be: if grep -q 'Apple version' gcc/version.c; then so that the correct GCC patch is used, and build_gcc needs fixing up. But then the build is on its way, let's see whether it completes/works. (I don't think there are too many differences actually, but we'll know) --anders

Trying gcc-5465 now. I added another if to setup-gcc.sh, since I don't know enough sh to do it better: if grep version_string gcc/version.c | grep -qF '(Apple Inc.'; then gcc_apple=apple- fi But now I got a different error: ../../gcc-5465/gcc/d/d-lang.cc: In function 'void d_write_global_declarations()': ../../gcc-5465/gcc/d/d-lang.cc:670: warning: comparison between signed and unsigned integer expressions ../../gcc-5465/gcc/d/d-lang.cc: At global scope: ../../gcc-5465/gcc/d/d-lang.cc:1580: error: invalid conversion from 'char' to 'tree_code_class' I wonder if I should report it as a bug? -- Carlos Santander Bernal
Oct 31 2007
next sibling parent reply Carlos Santander <csantander619 gmail.com> writes:
Carlos Santander escribi├│:
 Anders F Bj├Â┬Ürklund escribi├│:
 Dave Cheney wrote:

 I haven't had any luck compiling gdc from svn yet as the only apple 
 compiler sources available are gcc-5363, which is from the tiger 
 series. It appears that the gcc built into Leopard is build from 
 revision 5465 which has just been released now. If I have any luck 
 building against leopards gcc i'll report it to this list

As reported earlier, the check in setup-gcc.sh for "Apple Computer" doesn't match the new "Apple the Phone company", errr, "Apple Inc.": grep version_string gcc/version.c | grep -qF '(Apple Computer, Inc.' const char version_string[] = "4.0.1 (Apple Inc. build 5465)"; It should instead be: if grep -q 'Apple version' gcc/version.c; then so that the correct GCC patch is used, and build_gcc needs fixing up. But then the build is on its way, let's see whether it completes/works. (I don't think there are too many differences actually, but we'll know) --anders

Trying gcc-5465 now. I added another if to setup-gcc.sh, since I don't know enough sh to do it better: if grep version_string gcc/version.c | grep -qF '(Apple Inc.'; then gcc_apple=apple- fi But now I got a different error: .../../gcc-5465/gcc/d/d-lang.cc: In function 'void d_write_global_declarations()': .../../gcc-5465/gcc/d/d-lang.cc:670: warning: comparison between signed and unsigned integer expressions .../../gcc-5465/gcc/d/d-lang.cc: At global scope: .../../gcc-5465/gcc/d/d-lang.cc:1580: error: invalid conversion from 'char' to 'tree_code_class' I wonder if I should report it as a bug?

Oh, and setup-gcc.sh also failed, but I went ahead anyway. This is the relevant section: patching file build_gcc Hunk #1 succeeded at 114 (offset 8 lines). Hunk #2 FAILED at 149. Hunk #3 FAILED at 246. Hunk #4 succeeded at 288 (offset 18 lines). Hunk #5 succeeded at 304 (offset 18 lines). Hunk #6 succeeded at 354 (offset -7 lines). Hunk #7 succeeded at 419 with fuzz 2 (offset -4 lines). Hunk #8 FAILED at 437. 3 out of 8 hunks FAILED -- saving rejects to file build_gcc.rej -- Carlos Santander Bernal
Oct 31 2007
parent =?UTF-8?B?QW5kZXJzIEYgQmrDtsKacmtsdW5k?= <afb algonet.se> writes:
Carlos Santander skrev:

 Oh, and setup-gcc.sh also failed, but I went ahead anyway. This is the 
 relevant section:
 
 patching file build_gcc
 Hunk #1 succeeded at 114 (offset 8 lines).
 Hunk #2 FAILED at 149.
 Hunk #3 FAILED at 246.
 Hunk #4 succeeded at 288 (offset 18 lines).
 Hunk #5 succeeded at 304 (offset 18 lines).
 Hunk #6 succeeded at 354 (offset -7 lines).
 Hunk #7 succeeded at 419 with fuzz 2 (offset -4 lines).
 Hunk #8 FAILED at 437.
 3 out of 8 hunks FAILED -- saving rejects to file build_gcc.rej

Some of the context around the patch changed, because of the addition of the ARM cross-compiler targets... (for the iPhone) The failed lines are the ones that lipo together gdc-4.0 and rdmd --anders
Oct 31 2007
prev sibling parent =?UTF-8?B?QW5kZXJzIEYgQmrDtsKacmtsdW5k?= <afb algonet.se> writes:
Carlos Santander skrev:

 But now I got a different error:
 

 ../../gcc-5465/gcc/d/d-lang.cc: At global scope:
 ../../gcc-5465/gcc/d/d-lang.cc:1580: error: invalid conversion from 
 'char' to 'tree_code_class'
 
 I wonder if I should report it as a bug?

I'm seeing this too, but it's a strange one since it should only be a char for GCC versions < 4.0 --anders
Oct 31 2007
prev sibling next sibling parent reply "Anders Bergh" <anders1 gmail.com> writes:
Hi,

I'm getting the same warnings.

/var/folders/iT/iTI3bw3gHJudhiAFd4HJV++++TI/-Tmp-//ccVYelUD.s:208:indirect
jmp without `*'

OS X version: 10.5.1
gcc -v: gcc version 4.0.1 (Apple Inc. build 5465)
gdc -v: gcc version 4.1.2 20070214 (  (gdc 0.24, using dmd 1.020))

I used macports to install gdc.

Anders
Dec 14 2007
parent reply =?UTF-8?B?QW5kZXJzIEYgQmrDtnJrbHVuZA==?= <afb algonet.se> writes:
Anders Bergh wrote:

 I'm getting the same warnings.
 
 /var/folders/iT/iTI3bw3gHJudhiAFd4HJV++++TI/-Tmp-//ccVYelUD.s:208:indirect
 jmp without `*'
 
 OS X version: 10.5.1
 gcc -v: gcc version 4.0.1 (Apple Inc. build 5465)
 gdc -v: gcc version 4.1.2 20070214 (  (gdc 0.24, using dmd 1.020))
 
 I used macports to install gdc.

Those warnings are "normal", when using FSF GCC instead of Apple GCC. Apparently GCC 4.2.0 and later has better support for Darwin, but GDC wasn't working too well with those newer versions of GCC (yet) ? But I would still recommend using Apple's GCC on Apple's OS... :-) --anders
Dec 15 2007
parent =?UTF-8?B?QW5kZXJzIEYgQmrDtnJrbHVuZA==?= <afb algonet.se> writes:
Anders Bergh wrote:

 But I would still recommend using Apple's GCC on Apple's OS... :-)

You'd think MacPorts would compile a Apple-ified version of gdc... oh well.

I think that the Apple versions of GCC all start with "apple-", such as "gcc33" vs. "apple-gcc33" and "gcc40" vs. "apple-gcc40" So in this case "gdc" would be using the FSF version of GCC, while a "apple-gdc" port could be using the Apple GCC version ? --anders
Dec 16 2007
prev sibling parent "Anders Bergh" <anders1 gmail.com> writes:
On Dec 15, 2007 10:59 AM, Anders F Bj├Ârklund <afb algonet.se> wrote:
 Those warnings are "normal", when using FSF GCC instead of Apple GCC.

 Apparently GCC 4.2.0 and later has better support for Darwin, but
 GDC wasn't working too well with those newer versions of GCC (yet) ?

 But I would still recommend using Apple's GCC on Apple's OS... :-)

 --anders

You'd think MacPorts would compile a Apple-ified version of gdc... oh well. Anders
Dec 15 2007
prev sibling parent reply Oriol Fornes Crespo <oriol.fornes gmail.com> writes:
Hi Carlos, you must download the xcode_3.0 from mac. You should first register
as
a mac software developer, then download this dmg and install it all. After this
you will have gcc, make, etc.
Jan 11 2008
parent Carlos Santander <csantander619 gmail.com> writes:
Oriol Fornes Crespo escribiˇ:
 Hi Carlos, you must download the xcode_3.0 from mac. You should first register
as
 a mac software developer, then download this dmg and install it all. After this
 you will have gcc, make, etc.

XCode 3.0 comes with Leopard, and gdc worked fine with Tiger. Recent GDC revisions have worked, but now I've had linker troubles. See issue #1755 (http://d.puremagic.com/issues/show_bug.cgi?id=1755) -- Carlos Santander Bernal
Jan 11 2008