On Wed, 16 Sep 2009, Przemyslaw Czerpak wrote: hi,
> I'm really sorry but I was wrong. I've just tested current SVN > and default build time CC is preferred. that is contrary to what i'm experiencing. i've built hb in cpp mode (so it was using g++ as the compiler), and if i don't explicitly specify "-cpp" to hbmk2, it will call "gcc". what i'm experiencing is: tinky:/tmp/hb$ ./bin/harbour -build 2>&1 | fgrep Build Harbour Build Info Build options: (C++ mode) tinky:/tmp/hb$ ./bin/hbmk2 -trace t.prg hbmk2: Processing configuration: /tmp/hb/bin/hbmk.cfg hbmk2: Harbour compiler command (internal): (/tmp/hb/bin/harbour) -n2 t.prg -i/tmp/hb/include Harbour 2.0.0beta3 (Rev. 12513) Copyright (c) 1999-2009, http://www.harbour-project.org/ Compiling 't.prg'... Lines 5, Functions/Procedures 1 Generating C source output to 't.c'... Done. hbmk2: C compiler command: suncc -c -fast -xnolibmopt -KPIC -I/tmp/hb/include t.c hbmk2: Linker command: suncc t.o -lhbextern -lhbdebug -lhbvm -lhbrtl -lhblang -lhbcpage [...] so _even though_ it was built by sunCC, it still calls suncc by default. it sunpro seems to overcome this, but this freaks gcc/g++ out without the special -lstdc++/supc++ treatment. my (and i think yours too, and i think viktor's too :), at least that's what i gather) view is that if nothing more specific instruction is given to hbmk2 (ie no -cpp, no -comp, no whatever else you can tell it what to use), then it should invoke the compiler it was compiled with. > BTW you or Tomaz asked about using OpenWatcom in Linux. Current version > (1.8) in full installation contains binaries for DOS, WIN, OS2 and > Linux builds. It's enough to set executable attributes for Linux > binaries in ${WATCOM}/binl directory. yup, my test builds include cross from linux to os2, dos, win and also native linux (btw, linux native and os2 cross are still broken :). -- [-] mkdir /nonexistent _______________________________________________ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
