delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2000/11/13/12:10:37

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 13 Nov 2000 12:07:08 -0500
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: make: could not load advapi32.dll
Message-ID: <20001113120708.K7424@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20001113143929 DOT 28133 DOT qmail AT web106 DOT yahoomail DOT com>
Mime-Version: 1.0
User-Agent: Mutt/1.3.11i
In-Reply-To: <20001113143929.28133.qmail@web106.yahoomail.com>; from earnie_boyd@yahoo.com on Mon, Nov 13, 2000 at 06:39:29AM -0800

On Mon, Nov 13, 2000 at 06:39:29AM -0800, Earnie Boyd wrote:
>--- Christopher Faylor <cgf AT redhat DOT com> wrote:
>> On Sun, Nov 12, 2000 at 10:48:10PM +0100, Emanuele Aliberti wrote:
>> >  I am from the RactOS developers. We use GCC/MinGW to compile the
>> >kernel an the Win32 personality. I am reporting not properly an error,
>> >but a behaviour you should probably be aware of.
>> >
>> >The setup is a bit strange. 
>> >
>> >1. GCC/MingW 2.95.2
>> >2. CygWin 1.1.5 (make, ld, dlltool only; no GCC)
>> >
>> >PATH is set to give priority to CygWin binaries. Remember that there is
>> >no GCC/Cygwin here.
>> >
>> >Note that ntoskrnl.exe is compiled and linked regularly by
>> >gcc/mingw+ld/cygwin. The same for ntdll.dll, kernel32.dll and
>> >crtdll.dll. It happens something strange when ld is called to link
>> >advapi32.dll (actually make.exe/cygwin can not load advapi32.dll).
>> 
>> Cygwin autoloads advapi32.dll.  I suspect that if you're building the
>> DLL this could be a problem.
>> 
>
>So, you would need to build new-advapi32.dll and let the install process copy
>it to the advapi32.dll name.

Even that would be hard, though, since 'cp' could be using advapi32.dll, too.
Possibly, if you rename the .dll to foo.advapi32.dll first or something that
might work.

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019