delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2002/05/28/12:15:01

Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Date: Tue, 28 May 2002 12:03:46 -0400
From: rich-paul AT rich-paul DOT net
To: cygwin AT cygwin DOT com
Subject: Re: Building cygwin1.dll
Message-ID: <20020528120346.B21064@monster.rich-paul.net>
References: <000001c204b3$f2b01bc0$0200a8c0 AT sknet01>
Mime-Version: 1.0
User-Agent: Mutt/1.3.16i
In-Reply-To: <000001c204b3$f2b01bc0$0200a8c0@sknet01>; from cmml@btinternet.com on Sun, May 26, 2002 at 01:50:35PM +0100
X-Operating-System: Linux monster 2.4.17-SMPs

First, a question for the list:  Are problems with building
cygwin on-topic for this list?  I know y'all don't like custom
setups, and custom building may be worse!


I don't know if this is related to your problem, I am currently
checking to see if I can find that routine on my system, but I do
know a couple of things:

	1)	Cygwin rarely seems to build in my environement without
		hacking
		
	2)	Many packages that require an out-of-tree experience to
		build say don't make the build tree under the source
		tree. Generally with these packages (e.g. gcc) I'll cd
		into the unpacked directory, make a dir called 'src',
		move * to src, and then make a dir called bld.  That's
		just my style, the other common way is to use
		/usr/src/xxx and /usr/src/xxx-bld
		
	3)	Many of the problems I have run into have been 'solved'
		by doing a rm -fr of the src tree that is failing.  The
		winsup build builds many things, and I only needed to
		build the actual dll

Let me know if you need more info, I, personally, don't like
using I can't build.  I seem to remember my physics teacher
saying something about 'thinking you can apply a formula you
cannot derive'.  If the feeling is that this is not on-topic for
the list, we'll talk via personal email.

		
On Sun, May 26, 2002 at 01:50:35PM +0100, CM wrote:
> I seem to be unable to build the cygwin1.dll from the cygwin sources.
> The configuration and compilation go fine, but when make tries to link
> the dll, I get errors about undefined symbols:
> 
> autoload.o(.wsock32_info+0x0):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.wsock32_info+0xc):autoload.cc: undefined reference to
> `wsock_init'
> autoload.o(.wsock32_info+0x18):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.wsock32_info+0x30):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.wsock32_info+0x48):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.wsock32_info+0x60):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.wsock32_info+0x78):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.wsock32_info+0x90):autoload.cc: more undefined references to
> `std_dll_init' follow
> autoload.o(.ws2_32_info+0xc):autoload.cc: undefined reference to
> `wsock_init'
> autoload.o(.ws2_32_info+0x17):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.ws2_32_info+0x2e):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.ws2_32_info+0x45):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.ws2_32_info+0x5c):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.ws2_32_info+0x73):autoload.cc: undefined reference to
> `std_dll_init'
> autoload.o(.ws2_32_info+0x8a):autoload.cc: more undefined references to
> `std_dll_init' follow
> net.o(.text+0x26c6):net.cc: undefined reference to `_wsock32_handle'
> 
> I have used nm and grep to look through all the cygwin objects and
> libraries and can't seem to find where the symbols are defined. Could
> somebody please tell where I am going wrong? To build cygwin, all I did
> was, extract the tarball, cd into the directory, make a new directory
> inside it called build, cd into that, execute a ../configure, and hit
> make. Was there something else I was supposed to do?
> 
> Thanks,
> CM 
> 
> 
> 
> 
> --
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> Bug reporting:         http://cygwin.com/bugs.html
> Documentation:         http://cygwin.com/docs.html
> FAQ:                   http://cygwin.com/faq/
> 

-- 
Got freedom?  Vote Libertarian:  http://www.lp.org

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -


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