Mark J. Reed wrote:
> On Wed, Jul 1, 2009 at 6:33 AM, Dave Korn wrote:
>> I noticed this when we added StrStrI to setup.exe, and I forgot to bootstrap
>> the generated files; I got a bad exe that didn't work [...]
>
> So, not really funny "ha-ha", then... too bad.
Nah, just a funny peculiar.
On Wed, Jul 1, 2009 at 6:33 AM, Dave Korn wrote:
>
> I noticed this when we added StrStrI to setup.exe, and I forgot to bootstrap
> the generated files; I got a bad exe that didn't work [...]
So, not really funny "ha-ha", then... too bad. I was hoping for an
API knee-slapper.
--
Mark J. Reed
On Jul 1 11:33, Dave Korn wrote:
>
> I noticed this when we added StrStrI to setup.exe, and I forgot to bootstrap
> the generated files; I got a bad exe that didn't work for me because it
> imported StrStrIA from comctl32.dll (which was the next -l option in the
> LDFLAGS), which - at least on
I noticed this when we added StrStrI to setup.exe, and I forgot to bootstrap
the generated files; I got a bad exe that didn't work for me because it
imported StrStrIA from comctl32.dll (which was the next -l option in the
LDFLAGS), which - at least on w2k - doesn't actually export that function:
4 matches
Mail list logo