From: Mumit Khan <khan@NanoTech.Wisc.EDU>
To: "Andrew G. Tereschenko [home]" <tag_aka_day@email.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: How soon will cyg compile via gcc ?
Date: Tue, 21 Mar 2000 21:02:00 -0000 [thread overview]
Message-ID: <200003220501.XAA27017@hp2.xraylith.wisc.edu> (raw)
In-Reply-To: <002a01bf93ba$607677c0$01010a0a@SKYNET.local>
"Andrew G. Tereschenko [home]" <tag_aka_day@email.com> writes:
> How about fix wrong source in cvs ?
> fhandler_tape.cc: In function `long long int get_ll(union LARGE_INTEGER *)'
> fhandler_tape.cc:702: `union _LARGE_INTEGER' has no member named `HighPart'
> fhandler_tape.cc:704: `union _LARGE_INTEGER' has no member named `LowPart'
>
> I have several files with this error ... How about write _STRUCT_NAME(u.) ? [
> or u.]
What CVS source do you have? What compiler do you have? You need to have
gcc-2.95.2 to handle anonymous unions.
Check the following output:
$ make VERBOSE=yes
and post what you get to the cygwin-developers list (*not* here). Before
you do that however, make sure your CVS tree is up-to-date.
> Also how about this craizy lines :
> BOOL (WINAPI *gdfse) (LPCSTR, long long *, long long *, long long *) =
> (BOOL (WINAPI *) (LPCSTR, long long *, long long *, long long *))
> GetProcAddress (k32, "GetDiskFreeSpaceExA");
>
> Something wrong in them ... Nobody in my firm still can't find solution for t
> his puzzle ;o)
Looks fine to me. What is this puzzle exactly?
> P.S> Hmm ...Possibly i'm dummy - but how soon i will be able to to compile cy
> gwin via cygwin (gcc 2.9.2 under cygwin ;o) ?
It works now, and has worked for a while. There may be occasional
instability in the development sources, but that's part of using
development sources.
Issues dealing with building Cygwin development (CVS) sources belong in
cygwin-developers list, where these issues are discussed and solved.
Regards,
Mumit
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-03-21 21:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-21 20:50 Andrew G. Tereschenko [home]
2000-03-21 21:02 ` Mumit Khan [this message]
2000-03-21 21:09 ` Chris Faylor
2000-03-22 6:59 Andrew G. Tereshchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200003220501.XAA27017@hp2.xraylith.wisc.edu \
--to=khan@nanotech.wisc.edu \
--cc=cygwin@sourceware.cygnus.com \
--cc=tag_aka_day@email.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).