Hallo,
since an CVS update this morning, I get a lot of messages about no
implemenatation of RPCRT functions:
err:win32:fixup_imports No implementation for RPCRT4.dll.365(RpcRaiseException),
setting to 0xdeadbeef
err:win32:fixup_imports No implementation for RPCRT4.dll.294(RpcBindingFree),
Has anyone successfully built Wine on Cygwin? Before
you laugh out loud and send nasty flames, please read
the whole message. Thanks.
Cygwin recently added Xfree86 4.0 X server capability
for Win NT/9x which appeared to be the final component
needed for a Wine port. It has gcc and appears to
On Wed, 8 Nov 2000, Andrew Lynch wrote:
[...]
I downloaded the Wine-20001026 source and attempted to
build Wine from source. Following the "quick start"
instructions resulted in the following error messages
from ./tools/wineinstall see attachment
It seems you forgot to redirect stderr:
Uwe Bonnes [EMAIL PROTECTED] wrote:
some days ago I asked about opinions what we need to do about a
builtin 16 bit commctrl implementation and sent a framework
patch. However I didn't get any feedback.
I still like to hear opinions whether we need our own 16 bit commctrl
implemenation...
Joerg Mayer [EMAIL PROTECTED] writes:
while talking about documentation. Your last patches broke the
"--debugmsg help" feature. How should we handle this?
a) write a tool to collect the info and add it in the old place?
b) add it to the manpage (maintainance problems)
c) ???
d) not do
Well, it was done that way for a purpose ;-)
The problem is that the higher-level thread libraries (typically pthreads)
tend to make certain assumptions about things application programs typically
do or don't do, and these are sometimes violated by Wine.
...
Thanks for bringing me up to
On Wed, 8 Nov 2000, Andrew Lynch wrote:
Francois Gouget, you are right. Attached is the
proper file based on your recommendation.
I have extracted the parts that seemed interesting:
WINE Installer v0.4
./tools/wineinstall: hash: rpm: not found
Well, not surprising but I think we
On Wed, 8 Nov 2000, Francois Gouget wrote:
[...]
Look for '-Bforcearchive' in configure.in. You need to remove the
second instance and then rerun autoconf (or manually remove the flag
from configure too).
Well, actually the configure.in script seems a bit strange. I believe
it would
I would like to submit a patch to disable rpath
by default, and add a '--enable-rpath[=DIR]' configure
options. Objections?
we do have to use rpath so that we don't need to tweak
the LD_LIBRARY_PATH or /etc/ld.conf on any user configuration
since your request is specific (and using
