hej!
this is what your linux environment should look like:
/usr/local/m68k-palmos-coff/
and under this directory should be:
/bin
/include
/lib
the installation process should have set up file links
from the /usr/local/bin directory to your m68k-palmos-coff/bin
directory.
if your path is set to include /usr/local/bin, everything
should work as normal.
you might want to check the directory structures over
again.. i am using slackware linux - so i dont know if
it is a red hat problem you have defined (but i doubt it)
hope this helps. i am using linux+gcc for all my development
and all that was required was to un-tar the gcc archive
into "/" as root.
slackware.... the hackers linux :)
cheers.
az.
--
Aaron Ardiri
Lecturer http://www.hig.se/~ardiri/
University-College i G�vle mailto:[EMAIL PROTECTED]
SE 801 76 G�vle SWEDEN
Tel: +46 26 64 87 38 Fax: +46 26 64 87 88
Mob: +46 70 352 8192 A/H: +46 26 10 16 11
On Sun, 9 May 1999, Alan Kennington wrote:
> While trying to compile a "hello world" program provided with the
> CD-ROM at the back of O'Reilly "Palm Programming" for the Linux
> environment, I've found several problems.
> Most of these relate to setting up paths etc., and I haven't
> yet found any info on this -- I'm just using standard
> search and kludge techniques to deal with these.
>
> But now I've come to a point where maybe these problems are
> wider than the linux environment.
> The palm header files in
>
> /usr/palm/lib/gcc-lib/m68k-palmos-coff/2.7.2.2-kgpd-071097/include/PalmOS3/System
>
> on my machine (as installed from redhat package manager rpm) seem to
> have nested C-style comments, like
> /* blah... /* nested comment */ more stuff.... */
>
> The compiler very correctly rejects these, for instance in
>
> SystemMgr.h
> ErrorMgr.h
>
> So I've started editing these header files.
>
> The ErrorMgr.h file contains
>
> Copyright(c) 1994, Palm Computing Inc
>
> as copyright message. Does this mean that I have out-of-date
> header files here?
> The SytemMgr.h files contains
>
> Copyright (c) 1994-1997, Palm Computing Inc
>
> which is bit more recent.
>
> I can only imagine that this problem is still present
> because most people are suing a compiler that permits
> non-standard C comment nesting.
> K&R 2nd edition p.192 says "Comments do not nest,...".
>
> My apologies for asking such an elementary question, but as
> soon as I get past "hello, world", it looks like the
> documentation I downloaded from 3com looks ample to work out
> most things for myself. It's just the first step that's a bit tricky.
>
> Regards,
> Alan Kennington.
>
>
