Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-Id: <199907121411.JAA00782@mercury.xraylith.wisc.edu> To: "Thomas Riley" cc: cygwin AT sourceware DOT cygnus DOT com Subject: Re: libio? Another related question In-Reply-To: Your message of "Mon, 12 Jul 1999 01:01:49 EDT." <000701becc23$a71167d0$010000c0 AT dubious> Date: Mon, 12 Jul 1999 09:11:08 -0500 From: Mumit Khan "Thomas Riley" writes: > > I am trying to compile some stuff that wants to use vfscanf. > compiles go OK, but linking finds unresolved references.=20 > As nearly as I can tell, it should be in libio.a .=20 Why do you think it should be libio? > Where can it be found? It's not standard, and not included in the cygwin runtime. > The source in libio.tar.bz2 from > sourceware.cygnus.com/pub/cygwin/cygwin-b20/src-by-top-dir has nothing > to indicate that this has ever been compiled under cygwin. I don't know what you mean. libio is part of libstdc++ (GNU C++ runtime library), and is definitely been compiled under cygwin. If your code uses/needs it, you have the following choices: - modify newlib's vfscanf and export it from the Cygwin DLL. I'm sure patches will be welcome so that it can be included in the next release. See newlib/libc/stdio/vfscanf. - write your own. You can use the newlib version, with minor modifications. If you contribute an implementation, the Cygwin folks might include it. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com