07010607.txt 01-Jul-00


Subject: Any successful Harbour/Linux users out there?
From: see.sig@for.email.address (Peter B. Steiger)

I downloaded Build 34 today and installed it on my RedHat
  6.2 system, along with GCC 2.91.66, and tried to compile a
  "hello world" program.
Alas!  GCC complains about not being able to find about a
  bazillion #include files, such as stdio.ch.  I read the
  info page about how to use "-I" and tried tinkering with
  bld.sh so that it would search the harbour include
  directory as well as the location of those other include
  files, /usr/i386-glibc20-linux/include but to no avail;
  gcc is still unhappy.
The main problem is, of course, I don't know diddly about
  gcc and I'm still wet behind the ears in linux.  Give me a
  good old SET LIB = any day.
So... could someone point me at a FAQ or sample script or
  something that will get me from hello.prg to hello.c to an
  executable hello?
Many thanks!

Peter B. Steiger


Subject: Re: Any successful Harbour/Linux users out there?
From: "jdm" <jdm1intx@DIE_SPAMBOT_DIEhome.com>

I really think they went down the wrong road when they
  decided to have it compile to C Code.  The original idea,
  a replacement for Clipper, is sound but the implementation
  is not.  C/C++ compilers are too fussy for most people to
  want to hassle with.  I think they should have stuck with
  simply implementing a native code Clipper Compiler for the
  x86 family using MSDOS.  Get that working smoothly, then
  port it to Linux.  That covers about 99.9% of your
  potential user base right there. To heck with
  "portability".

John M.


Subject: Re: Any successful Harbour/Linux users out there?
From: davep.news@davep.org (Dave Pearson)

The idea behind harbour is to build a portable free software
  Clipper clone.
As you can imagine, portability is important here.
Also, you're wrong about the requirement for a C compiler.
  On at least one platform harbour is producing its own
  object files and it could do so on any other platform if
  someone cares enough to actually do the work.
As it is, on Linux, for example, the need for object file
  generation really isn't that great because a C compiler
  comes "out of the box".
As for writing harbour so that it was DOS native. Are you
  serious?


Subject: Re: Any successful Harbour/Linux users out there?

From: "Gunnar Wagenknecht" <gunnar.wagenknecht@planet-
  wagenknecht.de>

Hi Dave!

Which platform is the one where Harbour produce its own
  object file?
Ist it Windows 32bit or ist it DOS? Which linker do I need
  to link these object files to an EXE and how to use this
  linker? Does it Blinker 5.1?

Cu, Gunnar


Subject: Re: Any successful Harbour/Linux users out there?
From: davep.news@davep.org (Dave Pearson)

>
Which platform is the one where Harbour produce its own
  object file? Ist it Windows 32bit or ist it DOS?
<
Win32.
>
Which linker do I need to link these object files to an EXE
  and how to use this linker? Does it Blinker 5.1?
<
I don't personally use harbour on Win32 so I can't say for
  sure but it is my understanding that Blinker 5.1 works.
  Even if it doesn't the intention is that it will come such
  a time as harbour is in a stable state (as in late
  beta/post beta).
Actually, I've just had a ferret in the DOC directory and
  found:
,----[ doc/whatsnew.txt ]
| Version 0.34 Build 34 (2000-06-02)
|
| [SNIP]
| - OBJ generation support for BCC5x + Blinker5
| [SNIP]
`----
so it seems that, so far, the Borland C++ 5.x linker and
  Blinker 5.x are supported.


Subject: Re: Any successful Harbour/Linux users out there?
From: davep.news@davep.org (Dave Pearson)

GCC shouldn't be complaining about a file called stdio.ch.
  .CH files, as you know, are Clipper (and harbour) header
  files. Those files are pre-processed by the harbour
  preprocessor.
However, STDIO.CH isn't a header file that is part of
  harbour anyway. Can you confirm the list of header files
  that are missing and exactly what can't find them?
>
I read the info page about how to use "-I" and tried
  tinkering with bld.sh so that it would search the harbour
  include directory as well as the location of those other
  include files, /usr/i386-glibc20-linux/include but to no
  avail; gcc is still unhappy.

The main problem is, of course, I don't know diddly about
  gcc and I'm still wet behind the ears in linux. Give me a
  good old SET LIB = any day.
<
harbour gives you that too. From bld.sh:
,----
| if [ -z "$HB_BIN_INSTALL" ]; then export
  HB_BIN_INSTALL=../bin/; fi
| if [ -z "$HB_LIB_INSTALL" ]; then export
  HB_LIB_INSTALL=../lib/; fi
| if [ -z "$HB_INC_INSTALL" ]; then export
  HB_INC_INSTALL=../include/; fi
`----
You simply need to set the above environment variables to
  point to the right places. For example:
,----[ Excerpt from my ~/.bashrc ]
| # This is for when we're working on harbour.
| export HB_ARCHITECTURE=linux
| export HB_COMPILER=gcc
| export HB_SRC_DIR=/usr/local/src/harbour/
| export HB_BIN_INSTALL=/usr/local/bin/
| export HB_LIB_INSTALL=/usr/local/lib/harbour/
| export HB_INC_INSTALL=/usr/local/include/harbour/
`----
>
So... could someone point me at a FAQ or sample script or
  something that will get me from hello.prg to hello.c to an
  executable hello? Many thanks!
<
I think you'll need to provide a little more information
  first. It sounds to me like you've got a GCC problem here,
  not a harbour problem.
Can you confirm that you've got the glibc-devel package
  installed? At a prompt type "rpm -q glibc-devel".
If you have, try compiling a simple C program. Try this:
-- cut here --
#include <stdio.h>
int main( void )
{
  printf( "Hello, World!\n" );
  return( 0 );
}
-- cut here --
Call it foo.c and compile it by simply typing "make foo" in
  the directory where foo.c lives. Does it compile? Can you
  run it ("./foo")?