Date: Tue, 15 Mar 2005 00:04:16 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600
Subject: [UnixOS2_Archive] No. 530

**************************************************
Monday 14 March 2005
 Number  530
**************************************************

Subjects for today
 
1  Re:  gcc-3.3.5-beta4 & emxomf? : Knut St. Osmundsen" <bird at anduin.net>


**= Email   1 ==========================**

Date:  Mon, 14 Mar 2005 01:34:02 +0100
From:  "Knut St. Osmundsen" <bird at anduin.net>
Subject:  Re:  gcc-3.3.5-beta4 & emxomf?



Stefan.Neis at t-online.de wrote:
>         Hi,
> 
> Anybody else having problems with emxomf?
> To me it appears to be completely broken...
> Just going into include directory and running e.g.
> "emxomf -s -l libstdc++.a" (the standard to generate
> a .lib from a .a, isn't it?) just gives me a "usage
> message", i.e. 
> 
>>emxomf 0.6b4.0 (Innotek Build 2005-01-17 09:41) -- Copyright (c) 1992-1995 by Eberhard Mattes
>>
>>Usage:
>>  emxomf [-dgqs] [-l[<symbol>]] [-m <symbol>] [-p <page_size>]
>>         [-i <default_lib>] [-I <idmdll>] [-D <dataseg>]
>>         -o <output_file> <input_file>
>>  emxomf [-dgqsx] [-l[<symbol>]] [-m <symbol>] [-p <page_size>]
>>         [-O <directory>] [-r|R <response_file>] [-i <default_lib>]
>>         [-I <idmdll>] [-D <dataseg>] <input_file>...
> 
> (snipp)
> and no .lib file.
> 

Fixed it. getopt() was treating optional arguments the BSD way instead 
of the GNU way. Using getopt_long() instead and the problem is gone.

I've also implemented -Zargs-wild and -Zargs-resp. All will be included 
in the next gcc/libc release.

Kind Regards,
  knut