said:
>I have a small unix program that I want to compile for eCS. I downloaded
>it and see many file suffixes that a new to me. So I downloaded GCC432
>and M4. Now I want to compile so I look and the makefiles one is a .am
>and the other is a .in, neither look like a makefile to me. There are a
>few .sh scripts that I am ignoring.
I recommend not ignoring anything. If you want to compile apps designed
to be built with the gcc toolchain, you really need the full toolchain.
Except for toy apps, anything else is more work than you might imagine.
There's a ready to use toolchain at
http://www.smedley.info/os2ports/index.php?page=build-environment
I still use my home-brew environment because it's been in place for a long
time, but Paul's setup seems to work well for those that use it.
>I build my own makefile and try a compile. None of the C standard
>headers are found which surprised me, I had expected them to come with
>the compiler.
Not surprising. You tried to roll your own, which means you need to
understand and satisfy every requirement the app has and you need to debug
any problems created by just guessing as to what's needed.
>Where can I download the standard C header files?
Unless I missed an update, you only downloaded a subset of the gcc
compiler toolchain. The gcc432 zip is an experimental development
release. It is designed to layer on top of 3.3.5 which is the current
stable release.
>Generated from configure.ac by autoheader. */" and has many #undef
>statements. What is this program 'autoheader' and do I need it?
Maybe.
>There are two .m4 files that I ran M4 on but they did not appear to do
>anything.
I'm sure they did something, but I'm also sure they did not do anything
useful run standalone. The .m4 files that come with the sources add
application specific extensions to the generic autoconf scripts.
>Where can I get a MAN program for eCS?
I use man.exe, version 1.5g. It should be on Hobbes. Generally, I go to
the web to read man pages.
>Anything else I need so I can use GCC432?
Yes.
I recommend you google for an autoconf tutorial so you have a basic idea
of how the pieces fit together.
You might want to browse the netlabs libc-user mailing list which is
archived a gmane because it contains a wealth of OS/2 specific gcc
information.
The comp.os.os2.programmer.misc newsgroup also has some useful gcc
information.
You probably should subscribe to the libc-user list. It's as good a place
as any to get gcc related questions answered.
Once you have a gcc toolchain installed and working, to build an app, you
- unpack the sources
- run configure one time to build site specific makefiles and such
- run make to create your executables
In rare cases, you might need to run autoconf and/or automake to rebuild
configure and its inputs, but this is not typical. All recent autoconf's
know about OS/2, so the supplied configure scripts usually already have
OS/2 support.
The autoconf toolset philosophy differs from what you are used to. Linux
and unix apps, unlike OS/2 and Windows apps, typically run on a wide
variety of different CPU architectures and a wide variety of
distributions. They all vary in terms of what is installed where.
A configure script knows what's needed to build a particular app and how
to check if the requirements are met. The configure scripts are complex,
but you can generally use them like black boxes.
BTW, got a link to the app you are trying to build?
Steven
--
----------------------------------------------------------------------
"Steven Levine" MR2/ICE 3.00.11.18 BETA #10183 eCS/Warp/DIY/14.103a_W4 etc.
www.scoug.com irc.ca.webbnet.info #scoug (Wed 7pm PST)
----------------------------------------------------------------------
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 23 |
October |
2008 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.
