Article View: comp.os.os2.programmer
Article #3609Re: Problem with GCC 0.8f
From: ochealth
Date: Mon, 25 Jan 1993 04:53
Date: Mon, 25 Jan 1993 04:53
60 lines
2651 bytes
2651 bytes
In article <1jv5rlINNbg8@access.usask.ca> lowey@jester.usask.ca (CrazyMan) writes:
:Hi,
:
:I'm using the EMX 0.8f gcc compiler. I'm currently porting a program
:that converts ZyXEL modem voice file formats to and from Soundblaster
:VOC formats. The program is converted, but I want to distribute it as
:a stand alone program, not requiring the EMX*.DLL files. (When it is
:done, I'll put it on the FTP site listed below with the MS-DOS versin
:that is already there)
please don't. OS/2 uses DLLs for a reason. Static linking just creates a
lot of redundant, disk hogging code, that can never have bugs in the
library fixed without distributing the whole program again.
Anybody using free software should have the EMX DLLs anyway.
:
:When I say:
:
:gcc -o vcnvt.exe vcnvt.c
:
:everything works fine. However, when I add the -Zomf -Zsys options, I
:get the following:
:
:======================================================================
:[C:\kevin\src\zyxel]gcc -o vcnvt.exe vcnvt.c -Zomf -Zsys
:
:c:\emx\lib\crt0.obj(crt0.obj) : error L2029: '_entry2' : unresolved external
:
:LINK386 : warning L4071: application type not specified; assuming WINDOWCOMPAT
:
:There was 1 error detected
:======================================================================
:
:I tried using "emxomf" to convert the crt0.o file to a new crt0.obj, but I
:don't think I was using it correctly. I tried:
:
:emxomf -o crt0.obj crt0.o
:
:I read something in the docs about the "crt0" requires the -m option.
:Unfortunately, the -m option requires a symbol. I tried using
:_entry2, but that didn't solve the problem.
:
:Does anyone have any suggestions?
RTFM!!!!
run omf??.cmd in the lib directory to create the .lib files. EMX f doesn't
ship with .lib files, because they are just converted from the .a libraries.
:
:Thanks
:- Kevin Lowey (Lowey@Sask.USask.CA)
:>>>>> Anonymous FTP to FTP.USASK.CA for DOS, OS/2, and Windows programs <<<<<
--
______________________________________________________________________________
ochealth@unixg.ubc.ca
Technical Details
Message-ID:
<1jvrobINNigu@skeena.ucs.ubc.ca>Path:
arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!batcomputer!cornell!uw-beaver!cs.ubc.ca!unixg.ubc.ca!ochealthReferences:
<1jv5rlINNbg8@access.usask.ca>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!usc!rpi!batcomputer!cornell!uw-beaver!cs.ubc.ca!unixg.ubc.ca!ochealth From: ochealth@unixg.ubc.ca (ochealth) Newsgroups: comp.os.os2.programmer Subject: Re: Problem with GCC 0.8f Date: 25 Jan 1993 04:53:31 GMT Organization: University of British Columbia, Vancouver, B.C., Canada Lines: 60 Message-ID: <1jvrobINNigu@skeena.ucs.ubc.ca> References: <1jv5rlINNbg8@access.usask.ca> NNTP-Posting-Host: unixg.ubc.ca Keywords: GCC