Fixing Imake
Suhaib Siddiqi
ssiddiqi@inspirepharm.com
Thu Apr 12 04:06:00 GMT 2001
> It turns out that the general target is being used. Below is
> the imake
> target generation command:
> gcc -o imake -O -I../../include
> -I../../imports/x11/include/X11 imake.o
>
> Should I throw automode.o on the end?
NOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
OOOOOOOOOOOOOOOOOOOOO
unless you know how to read bitmaps and fonts files properly with M$ CR\LF
crap
inserted.
Suhaib
>
> Harold
>
> > -----Original Message-----
> > From: Robert Collins [ mailto:robert.collins@itdomain.com.au ]
> > Sent: Thursday, April 12, 2001 12:07 AM
> > To: Harold Hunt; Cygx (E-mail)
> > Subject: Re: Fixing Imake
> >
> >
> > ----- Original Message -----
> > From: "Harold Hunt" <huntharo@msu.edu>
> > To: "Cygx (E-mail)" <cygwin-xfree@sources.redhat.com>
> > Sent: Thursday, April 12, 2001 1:46 PM
> > Subject: Fixing Imake
> >
> >
> > > Here's a line from xc/config/imake/Makefile.ini
> > >
> > > imake.exe:: imake.obj
> > > cl -nologo imake.obj libc.lib kernel32.lib
> > >
> > > Anyone else think that linking with kernel32.lib might be
> > the root of
> > the
> > > problem?
> > >
> > > Harold
> > >
> > >
> >
> > Nope. kernel32 is always linked in implicitly. What will be
> > an issue is
> > if
> > a) Imake is using win32 file read and write calls or
> > b) it doesn't set the fhandle to text mode when it opened,
> or brefore
> > reads occur.
> >
> > Rob
> >
>
More information about the Cygwin-xfree
mailing list