This is the mail archive of the
mailing list for the Cygwin project.
Re: Mapping of Windows registry not complete
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 28 Nov 2011 13:39:36 -0500
- Subject: Re: Mapping of Windows registry not complete
- References: <4ED0D791.firstname.lastname@example.org> <4ED278E2.email@example.com>
- Reply-to: cygwin at cygwin dot com
On 11/27/2011 12:52 PM, Julien wrote:
Le -10/01/-28163 20:59, Christian Franke a écrit :
Julien Nabet wrote:
I'm trying to compile Libreoffice on Windows with Cygwin. For this, I had
to install some softs including Microsoft Visual C++ Express 8.
When I launched configuration part of Libreoffice (so just before
compiling), I noticed that some config elements weren't found.
By taking a look about the cause of this, I saw that Windows registry
mapped by Cygwin located in /proc/registry wasn't complete.
For example I've got :
/proc/registry/HKLM/Software/Microsoft/VC8 (since I'm right now on Linux,
the path is not exactly this one but that's the idea) but nothing in it
whereas I can see with regedit there are keys and subkeys.
I could not reproduce this. Please provide output of:
$ uname -rs
$ cd /proc/registry/HKEY_LOCAL_MACHINE/SOFTWARE/Microsoft
$ stat VisualStudio/8.0
$ ls -la VisualStudio/8.0
If 'ls' output is actually empty, retry with Cygwin shell running as
(ls /proc/registry/HKEY_LOCAL_MACHINE/SAM/SAM should work then).
Please note that the Express editions of Visual Studio put some subkeys to
a different location:
A configuration script expecting Express edition might not work with a
regular edition and vice versa.
In fact, I can't test any more since I uninstall Cygwin (registry cleaning +
cygwin directory) and can't succeed in reinstall it again.
Each time I try, I've got a Windows error blue screen (BSoD).
Of course, I know there could be interaction with other softs, so i
deactivated Avast for example and use no software meanwhile (I thought it
could be the fact to use Firefox during install for example) but no way.
I appreciate your help but now I don't want to waste some time to guess the
cause of this BSoD so I return to Linux.
Thank you for having answered.
A BSoD is caused by bad drivers or some other kernel problem. You can
check the first line of the report for the DLL/SYS file that it bombed
in to see if that gives you a clue as to the source of the problem.
Otherwise, try updating Windows or back out any recently added hardware.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple