Date: Wed, 16 Feb 2005 00:04:19 EST-10EDT,10,-1,0,7200,3,-1,0,7200,3600
Subject: [UnixOS2_Archive] No. 522

**************************************************
Tuesday 15 February 2005
 Number  522
**************************************************

Subjects for today
 
1  Re:  gcc-3.3.5-beta4 & emxomf & more : Stefan.Neis at t-online.de
2  Re:  gcc-3.3.5-beta4 & emxomf & more : Knut St. Osmundsen" <bird at anduin.net>


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

Date:  Mon, 14 Feb 2005 16:50:41 +0100 (CET)
From:  Stefan.Neis at t-online.de
Subject:  Re:  gcc-3.3.5-beta4 & emxomf & more

Knut St. Osmundsen schrieb:

> PS. There should be no reason for converting
> libstdc++.a, MakeOmfLibs.cmd already does 
> this.

Sure, I just wanted to give a self-contained
example instead of asking everybody to try
to build a DLL version of wxWindows. ;-)

BTW, the other thing I found is that "nm"
on (a.out) executables isn't working any more.
I'm using that to determine if an executable
calls some GUI initialization routine to
automagically determine if I should run "emxbind -ep " on it or not
(wxWindows apps
may be either plain text apps, or X11 apps
or PM apps - I need to detect the later case
and make it a PM app, since the linker default
is to assume a text app).
Any idea what to check in absence of a working
"nm"? Even more import: Any idea how to check
OMF executables?

      Regards,
             Stefan


**= Email   2 ==========================**

Date:  Mon, 14 Feb 2005 21:49:31 +0100
From:  "Knut St. Osmundsen" <bird at anduin.net>
Subject:  Re:  gcc-3.3.5-beta4 & emxomf & more



Stefan.Neis at t-online.de wrote:
> Knut St. Osmundsen schrieb:
> 
> 
>>PS. There should be no reason for converting
>>libstdc++.a, MakeOmfLibs.cmd already does 
>>this.
> 
> 
> Sure, I just wanted to give a self-contained
> example instead of asking everybody to try
> to build a DLL version of wxWindows. ;-)
Ok :)


> BTW, the other thing I found is that "nm"
> on (a.out) executables isn't working any more.
That's very odd, putting it on the todo list.

> I'm using that to determine if an executable
> calls some GUI initialization routine to
> automagically determine if I should run "emxbind -ep " on it or not
> (wxWindows apps
> may be either plain text apps, or X11 apps
> or PM apps - I need to detect the later case
> and make it a PM app, since the linker default
> is to assume a text app).
> Any idea what to check in absence of a working
> "nm"? Even more import: Any idea how to check
> OMF executables?

objdump -t will work in a somewhat similar way as nm. But if nm is 
broken objdump might be too.

On omf, emxexp would be a very good choice if you just wanna see 
publics. You can also use listomf, but that'll give you *everything*.

Kind Regards,
  knut