home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.programmer
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!rpi!uwm.edu!src.honeywell.com!mail-enters-news
- From: bergstro@src.honeywell.com (Pete Bergstrom)
- Subject: Can't get gcc2.1 to work
- In-Reply-To: figueroa@SPUNKY.CS.NYU.EDU's message of 18 Aug 92 15: 24:16 GMT
- To: comp.os.os2.programmer
- Message-ID: <9208181552.AA09832@data.src.honeywell.com>
- Posted-Date: Tue, 18 Aug 92 10: 52:57 CDT
- Sender: daemon@src.honeywell.com
- Organization: Honeywell Systems & Research Center
- Date: Tue, 18 Aug 1992 15:52:57 GMT
- Received-Date: Tue, 18 Aug 92 10: 52:59 CDT
- Lines: 48
-
- figueroa@SPUNKY.CS.NYU.EDU (Samuel A. Figueroa) wrote:
-
- >I recently downloaded the gcc2.1 binaries (the one that uses the native
- >OS/2 linker), and while I am able to compile the "Hello world" sample
- >program without any problems, I can't figure out how to link it. The
- >result of the two commands:
- >
- > GCC -c SAMPLE1.C
- ^^^
-
- Try recompiling with sample1.c as the parameter. My recollection is
- that case matters in sources and .C means c++ while .c means c.
-
- > LINK386 SAMPLE1;
- >
- >is as follows:
- >
- >
- >Operating System/2 LX (Linear Executable) Linker
- >Version 2.00.000 Feb 25 1992
- >Copyright (C) IBM Corporation 1988-1992.
- >Copyright (C) Microsoft Corp. 1988-1992.
- >All rights reserved.
- >
- >
- >D:\GNU\LIB\LIBC.lib(gnulib3.obj) : error L2029: '___CTOR_LIST__' : unresolved external
- >D:\GNU\LIB\LIBC.lib(gnulib3.obj) : error L2029: '___DTOR_LIST__' : unresolved external
-
- The ___CTOR_LIST__ and ___DTO... are c++ thingies (sorry for being so
- technical :-).
-
-
- >LINK386 : warning L4071: application type not specified; assuming WINDOWCOMPAT
- >
- >There were 2 errors detected
- >
- >
- >Could someone please tell me what I am doing wrong? As far as I know, I
- >installed gcc correctly according to the installation instructions (except
- >that I installed it on the D: drive instead of the C: drive; I copied the
- >SAMPLE1.C program to the C: drive and compiled it from there).
-
-
- Note that the specification of the file's extension to the compiler is
- the important thing here - it doesn't necessarily matter that the file
- system (FAT) doesn't keep case.
-
- Pete
-