building cygwin1.dll

building cygwin1.dll

[Alexey Voinov]

Hello,

   Tried to build cygwin1.dll myself.
Got:
fhandler.h: In method `select_record::select_record(fhandler_base * = 0)':
fhandler.h:759: implicit declaration of function `int __builtin_memset(...)'

if I comment out #define memset __builtin_memset in winsup.h
all compiles but I got link time error in ntea.o.

I use:
$ uname -a
CYGWIN_98-4.10 VOINS 1.1.0(0.16/3/2) 2000-01-06 12:55:43 i586 unknown
$ gcc --version
2.95.2

Also tried gcc 2.95... same result.

Best regards,
Alexey Voinov
voins@caravan.ru



--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: building cygwin1.dll

[Mumit Khan]

Alexey Voinov <voins@caravan.ru> writes:
> Hello,
> 
>    Tried to build cygwin1.dll myself.
> Got:
> fhandler.h: In method `select_record::select_record(fhandler_base * = 0)':
> fhandler.h:759: implicit declaration of function `int __builtin_memset(...)'
> 
> if I comment out #define memset __builtin_memset in winsup.h
> all compiles but I got link time error in ntea.o.
> 
> I use:
> $ uname -a
> CYGWIN_98-4.10 VOINS 1.1.0(0.16/3/2) 2000-01-06 12:55:43 i586 unknown
> $ gcc --version
> 2.95.2
> 
> Also tried gcc 2.95... same result.
> 

You should browse the cygwin-developers list if you're building the 
snapshots (as opposed to say using the binary installations provided 
with each snapshot). This problem has been fixed since.

http://sourceware.cygnus.com/ml/cygwin-developers/ for email archives.

You should wait for the next snapshot which fixes a configuration goof
when installing mingw headers bundled with winsup.

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Building cygwin1.dll

[Fabio Fabbri]

I downloaded and installed all the recent binary tools.
Standard installation, binary mounts, WIN98.
I downloaded the cygwin-1.1.5-2-src.tar.gz and unpacked it in /usr/local
Then I did a
$ configure
$ make

but I got some make errors about

make[3]: Nothing to be done for `all'.
make[3]: Leaving directory
`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/w32api/lib'
make[2]: Leaving directory
`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/w32api'
make[2]: Entering directory
`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/cygwin'
make[2]: Leaving directory
`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/cygwin'
make[1]: Leaving directory `/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup'

What do I need to rebuild cygwin1.dll ?
Where can I find the building instructions ?

Thanks


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Re: Building cygwin1.dll

[Christopher Faylor]

On Tue, Oct 31, 2000 at 07:52:12PM +0100, Fabio Fabbri wrote:
>I downloaded and installed all the recent binary tools.
>Standard installation, binary mounts, WIN98.
>I downloaded the cygwin-1.1.5-2-src.tar.gz and unpacked it in /usr/local
>Then I did a
>$ configure
>$ make
>
>but I got some make errors about
>
>make[3]: Nothing to be done for `all'.
>make[3]: Leaving directory
>`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/w32api/lib'
>make[2]: Leaving directory
>`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/w32api'
>make[2]: Entering directory
>`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/cygwin'
>make[2]: Leaving directory
>`/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup/cygwin'
>make[1]: Leaving directory `/usr/local/cygwin-1.1.5-2/i586-pc-cygwin/winsup'
>
>What do I need to rebuild cygwin1.dll ?
>Where can I find the building instructions ?

I don't see any errors there.

Brief build instructions are here:

http://www.cygwin.com/faq/faq_4.html#SEC82

cgf

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

Building cygwin1.dll

[CM]

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/

Re: Building cygwin1.dll

[rich-paul]

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/

Re: Building cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
>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'm not sure what "custom building" means but issues with building 
the Cygwin DLL are on-topic for this list.  Generally speaking though,
the process should be as described in the FAQ entry:


How do I rebuild the tools on my NT box?
http://cygwin.com/faq/faq_4.html#SEC102



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

Re: Building cygwin1.dll

[Christopher Faylor]

On Tue, May 28, 2002 at 12:28:04PM -0400, Larry Hall (RFK Partners, Inc) wrote:
>At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
>>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'm not sure what "custom building" means but issues with building the
>Cygwin DLL are on-topic for this list.  Generally speaking though, the
>process should be as described in the FAQ entry:
>
>How do I rebuild the tools on my NT box?
>http://cygwin.com/faq/faq_4.html#SEC102

Yeah, but I have a lot of problems with those instructions.  I've found
that I generally have to convert all of the C code to Modula 3 and
rewrite the Makefiles as c-shell scripts before I can rebuild anything.
Sometimes I have to hand-compile stuff, too.  That's pretty tedious.

Of course, maybe this is just my own personal preferences showing
through.

cgf

--
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/

Re: Building cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

At 01:12 PM 5/28/2002, Christopher Faylor wrote:
>On Tue, May 28, 2002 at 12:28:04PM -0400, Larry Hall (RFK Partners, Inc) wrote:
> >At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
> >>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'm not sure what "custom building" means but issues with building the
> >Cygwin DLL are on-topic for this list.  Generally speaking though, the
> >process should be as described in the FAQ entry:
> >
> >How do I rebuild the tools on my NT box?
> >http://cygwin.com/faq/faq_4.html#SEC102
>
>Yeah, but I have a lot of problems with those instructions.  I've found
>that I generally have to convert all of the C code to Modula 3 and
>rewrite the Makefiles as c-shell scripts before I can rebuild anything.
>Sometimes I have to hand-compile stuff, too.  That's pretty tedious.


<humor>
I'd direct you to the email list archives but you'd probably be overwhelmed
by the number of posts with people saying they do the same thing.  Of course
when you run into this kind of problem, the best thing to do is send email
to this list about it and repeat it many times.  Most of the folks on this
list that could help you have allot of free time so they prefer to read 
multiple repeat posts.  However, sometimes the best course of action when 
you encounter a problem like this is to drop back to version B14 of Cygwin.
Either that or just use DOS or CPM.  These often work much better than the
current version of Cygwin.  But since you're a newbie, Chris, we can't 
expect you to know that.
</humor>





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

Re: Building cygwin1.dll

[Christopher Faylor]

On Tue, May 28, 2002 at 01:49:38PM -0400, Larry Hall (RFK Partners, Inc) wrote:
>At 01:12 PM 5/28/2002, Christopher Faylor wrote:
>>On Tue, May 28, 2002 at 12:28:04PM -0400, Larry Hall (RFK Partners, Inc) wrote:
>> >At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
>> >>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'm not sure what "custom building" means but issues with building the
>> >Cygwin DLL are on-topic for this list.  Generally speaking though, the
>> >process should be as described in the FAQ entry:
>> >
>> >How do I rebuild the tools on my NT box?
>> >http://cygwin.com/faq/faq_4.html#SEC102
>>
>>Yeah, but I have a lot of problems with those instructions.  I've found
>>that I generally have to convert all of the C code to Modula 3 and
>>rewrite the Makefiles as c-shell scripts before I can rebuild anything.
>>Sometimes I have to hand-compile stuff, too.  That's pretty tedious.
>
>
><humor>
>I'd direct you to the email list archives but you'd probably be overwhelmed
>by the number of posts with people saying they do the same thing.  Of course
>when you run into this kind of problem, the best thing to do is send email
>to this list about it and repeat it many times.  Most of the folks on this
>list that could help you have allot of free time so they prefer to read 
>multiple repeat posts.  However, sometimes the best course of action when 
>you encounter a problem like this is to drop back to version B14 of Cygwin.
>Either that or just use DOS or CPM.  These often work much better than the
>current version of Cygwin.  But since you're a newbie, Chris, we can't 
>expect you to know that.
></humor>

UNSUBSCRIBE

--
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/

Re: Building cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

At 01:57 PM 5/28/2002, Christopher Faylor wrote:
>On Tue, May 28, 2002 at 01:49:38PM -0400, Larry Hall (RFK Partners, Inc) wrote:
> >At 01:12 PM 5/28/2002, Christopher Faylor wrote:
> >>On Tue, May 28, 2002 at 12:28:04PM -0400, Larry Hall (RFK Partners, Inc) wrote:
> >> >At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
> >> >>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'm not sure what "custom building" means but issues with building the
> >> >Cygwin DLL are on-topic for this list.  Generally speaking though, the
> >> >process should be as described in the FAQ entry:
> >> >
> >> >How do I rebuild the tools on my NT box?
> >> >http://cygwin.com/faq/faq_4.html#SEC102
> >>
> >>Yeah, but I have a lot of problems with those instructions.  I've found
> >>that I generally have to convert all of the C code to Modula 3 and
> >>rewrite the Makefiles as c-shell scripts before I can rebuild anything.
> >>Sometimes I have to hand-compile stuff, too.  That's pretty tedious.
> >
> >
> ><humor>
> >I'd direct you to the email list archives but you'd probably be overwhelmed
> >by the number of posts with people saying they do the same thing.  Of course
> >when you run into this kind of problem, the best thing to do is send email
> >to this list about it and repeat it many times.  Most of the folks on this
> >list that could help you have allot of free time so they prefer to read 
> >multiple repeat posts.  However, sometimes the best course of action when 
> >you encounter a problem like this is to drop back to version B14 of Cygwin.
> >Either that or just use DOS or CPM.  These often work much better than the
> >current version of Cygwin.  But since you're a newbie, Chris, we can't 
> >expect you to know that.
> ></humor>
>
>UNSUBSCRIBE



LOL!

Sometimes, less is really more! :-)



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
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/

Re: Building cygwin1.dll

[rich-paul]

Real programmers use cat > a.out.  xxd is for wimps.

On Tue, May 28, 2002 at 01:12:41PM -0400, Christopher Faylor wrote:
> On Tue, May 28, 2002 at 12:28:04PM -0400, Larry Hall (RFK Partners, Inc) wrote:
> >At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
> >>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'm not sure what "custom building" means but issues with building the
> >Cygwin DLL are on-topic for this list.  Generally speaking though, the
> >process should be as described in the FAQ entry:
> >
> >How do I rebuild the tools on my NT box?
> >http://cygwin.com/faq/faq_4.html#SEC102
> 
> Yeah, but I have a lot of problems with those instructions.  I've found
> that I generally have to convert all of the C code to Modula 3 and
> rewrite the Makefiles as c-shell scripts before I can rebuild anything.
> Sometimes I have to hand-compile stuff, too.  That's pretty tedious.
> 
> Of course, maybe this is just my own personal preferences showing
> through.
> 
> cgf
> 
> --
> 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/

Re: Building cygwin1.dll

[rich-paul]

I meant that what I have built, I did not install through
setup.exe ...

The faq entry is good as far as it goes, but generally there are
problems. With my current download I believe they involved a
present but empty directory (perhaps windows32api?), and a couple
of other things.  I just removed the subtrees that didn't built,
and was able to patch and build what I needed.


On Tue, May 28, 2002 at 12:28:04PM -0400, Larry Hall (RFK Partners, Inc) wrote:
> At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
> >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'm not sure what "custom building" means but issues with building 
> the Cygwin DLL are on-topic for this list.  Generally speaking though,
> the process should be as described in the FAQ entry:
> 
> 
> How do I rebuild the tools on my NT box?
> http://cygwin.com/faq/faq_4.html#SEC102
> 
> 
> 
> Larry Hall                              lhall@rfk.com
> RFK Partners, Inc.                      http://www.rfk.com
> 838 Washington Street                   (508) 893-9779 - RFK Office
> Holliston, MA 01746                     (508) 893-9889 - FAX
> 
> 
> --
> 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/

Re: Building cygwin1.dll

[Christopher Faylor]

On Tue, May 28, 2002 at 07:02:38PM -0400, rich-paul@rich-paul.net wrote:
>I meant that what I have built, I did not install through
>setup.exe ...
>
>The faq entry is good as far as it goes, but generally there are
>problems. With my current download I believe they involved a
>present but empty directory (perhaps windows32api?), and a couple
>of other things.  I just removed the subtrees that didn't built,
>and was able to patch and build what I needed.

I'll remove the empty subdirectories from future source tar balls.

cgf

--
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/

Re: Building cygwin1.dll

[rich-paul]

Thanks!

I'm finding some more problems, but haven't had time to really
document them.  I'm leaving the notes which I started taking in
this editor here, in case anyone's interested, but don't flame me
for giving you raw ramblings, and letting you sort it out ...
I'll clean 'em up and submit 'em as a patch when I get a chance.
They're just there if anyone wants to read 'em.

Anyway, I'll let you know if/when I get through it, I've had this
editor open forever.  I'll try to get you enough patch that the
next version can compile 'out of the box'.  <G>

<ramble mode on>
	I noticed that removing that directory exposes another problem,
	the makefile wants to make a target called w32api, but there are
	no rules for such a target.  Of course, make hapilly thought
	it had already made it, in the form of a directory, so didn't
	complain.

	I removed the dependencies from four lines, and am trying again
	...

	Hmmm ... switching the lib directories to use the installed
	mingw32/win32api

	OK, got farther, added a check for the cross-directory
	libkernel32.a dependency ....

	At this point, started dying of 'parse error before symbol
	__gnuc_va_list' in stdio.h.  It does include stdarg.h, but
	perhaps whatever keeps stdio.h from exposing va_list, as the
	comment in the gnuc stdio says, is the culpret.  Anyway, I didn't
	want to dig too deeply, so I played with making .i files  for
	a while, and resorted to commenting out the conditionals at
	line 143, so that __VALIST would be #defined to char*.

	That may come back to haunt me when I try to compile some
	c++, but I'm not sure ... can't recall is varargs fns require
	c linkage or not.

	Well, c linkage aside, it haunted me ... 'new' c++ void*
	casting rules.  Oh, well, let's try void* instead.  <ramble
	mode off>




On Tue, May 28, 2002 at 07:29:30PM -0400, Christopher Faylor
wrote:
> On Tue, May 28, 2002 at 07:02:38PM -0400,
> rich-paul@rich-paul.net wrote:
> >I meant that what I have built, I did not install through
> >setup.exe ...
> >
> >The faq entry is good as far as it goes, but generally there
> >are problems. With my current download I believe they involved
> >a present but empty directory (perhaps windows32api?), and a
> >couple of other things.  I just removed the subtrees that
> >didn't built, and was able to patch and build what I needed.
> 
> I'll remove the empty subdirectories from future source tar
> balls.
> 
> cgf
> 
> -- 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/

Re: Building cygwin1.dll

[Christopher Faylor]

On Wed, May 29, 2002 at 09:17:28AM -0400, rich-paul@rich-paul.net wrote:
>	I noticed that removing that directory exposes another problem,
>	the makefile wants to make a target called w32api, but there are
>	no rules for such a target.  Of course, make hapilly thought
>	it had already made it, in the form of a directory, so didn't
>	complain.

That's because you *need* the directory to be populated.

>	I removed the dependencies from four lines, and am trying again
>	...

Wrong "solution".

>	Hmmm ... switching the lib directories to use the installed
>	mingw32/win32api

Wrong "solution".

>	OK, got farther, added a check for the cross-directory
>	libkernel32.a dependency ....
>
>	At this point, started dying of 'parse error before symbol
>	__gnuc_va_list' in stdio.h.  It does include stdarg.h, but
>	perhaps whatever keeps stdio.h from exposing va_list, as the
>	comment in the gnuc stdio says, is the culpret.  Anyway, I didn't
>	want to dig too deeply, so I played with making .i files  for
>	a while, and resorted to commenting out the conditionals at
>	line 143, so that __VALIST would be #defined to char*.

Something is wrong in your installation.

When, you think about this problem, think about it from the point of
view that many people (me, for instance) are building cygwin.  We don't
build it by hacking at the Makefile.  We build it by having the complete
sources installed.

If you have to start editing things, you're obviously going down the
wrong track.

cgf

--
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/

Re: Building cygwin1.dll

[rich-paul]

OK, why don't I start over:

	My assumption, from the previous discussion, was that the directions
	in the FAQ were, in theory, sufficient to actually perform the task.
	Therefore, I assumed that cygwin-1.3.10-1-src.tar.bz2 was supposed
	to be able to build alone, and that it's inability to do so was
	brokenness on it's part, which has been hidden because it's
	generally only compiled as part of the larger 'net-release',
	which contains other things.

	This was bolstered by being able to compile a working cygwin1.dll
	using, I assume, my installed version of w32api in place of the one
	that belongs in the source tree.  It may be, however, that doing
	this worked "by accident" and should not be assumed to be a workable
	thing in the future.

	But if there are other packages that *SHOULD* be required to build
	cygwin1.dll, then my assumption was invalid.  My next instict was to
	say "OK, the brokenness is in the FAQ".  But having re-read that
	entry, I cannot say that it's technically wrong.  It merely says to
	put "the sources" into /src.  It does not say what constitutes "The
	sources".  It was *my* assumption that the only sources required to
	build cygwin1.dll were contained in cygwin-1.3.10-1-src.tar.bz2.

	So now the question becomes, what is the minimum subset of the
	source distribution that must be unpacked into /src in order for
	following the directions in the FAQ to work, and how should they be
	put there.  I assume that the three empty directories, w32api, mingw,
	and cinstall should be filled, so I'll start with them and see if
	that produces a dll.

	Another question:  Are there any directions as to how to use the
	mknetrel package from the cygwin-apps cvs tree?  I've read some of
	the script, and it looks like it might make life easier, but it
	appears to need things mounted in particular absolute directories.
	If there are no such docs, would you be interested in having some?

On Wed, May 29, 2002 at 10:36:18AM -0400, Christopher Faylor wrote:
> On Wed, May 29, 2002 at 09:17:28AM -0400, rich-paul@rich-paul.net wrote:
> >	I noticed that removing that directory exposes another problem,
> >	the makefile wants to make a target called w32api, but there are
> >	no rules for such a target.  Of course, make hapilly thought
> >	it had already made it, in the form of a directory, so didn't
> >	complain.
> 
> That's because you *need* the directory to be populated.
> 
> >	I removed the dependencies from four lines, and am trying again
> >	...
> 
> Wrong "solution".
> 
> >	Hmmm ... switching the lib directories to use the installed
> >	mingw32/win32api
> 
> Wrong "solution".
> 
> >	OK, got farther, added a check for the cross-directory
> >	libkernel32.a dependency ....
> >
> >	At this point, started dying of 'parse error before symbol
> >	__gnuc_va_list' in stdio.h.  It does include stdarg.h, but
> >	perhaps whatever keeps stdio.h from exposing va_list, as the
> >	comment in the gnuc stdio says, is the culpret.  Anyway, I didn't
> >	want to dig too deeply, so I played with making .i files  for
> >	a while, and resorted to commenting out the conditionals at
> >	line 143, so that __VALIST would be #defined to char*.
> 
> Something is wrong in your installation.
> 
> When, you think about this problem, think about it from the point of
> view that many people (me, for instance) are building cygwin.  We don't
> build it by hacking at the Makefile.  We build it by having the complete
> sources installed.
> 
> If you have to start editing things, you're obviously going down the
> wrong track.
> 
> cgf
> 
> --
> 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/

Re: Building cygwin1.dll

[..]

rich-paul@rich-paul.net wrote:
> 
> OK, why don't I start over:
> 
>         My assumption, from the previous discussion, was that the directions
>         in the FAQ were, in theory, sufficient to actually perform the task.

Not yet. I myself whish that this was more refined, but it might
take a while for those that by their concentrated experiance consider
points to be trivial to understand to the extent to which documentation
is required to adapt that experiance to your or another's needs.


-- 
--=<> Dr. Clue (A.K.A. Ian A. Storms) <>=--
--=<[]>=- http://www.drclue.net
--=<[]>=- C++ HTML JavaScript DHTML CGI TCP/IP SQL JAVA VRML NSAPI 
--=<[]>=- http://www.drclue.net/F1.cgi/HTML/HTML.html	(My famous
HTML/CGI guide.)
--=<[]>=- http://www.drclue.net/beta			(My X-BROWSER DHTML library.)



--
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/

Re: Building cygwin1.dll

[Christopher Faylor]

On Sun, Jun 02, 2002 at 12:47:47AM -0400, rich-paul@rich-paul.net wrote:
>Another question: Are there any directions as to how to use the
>mknetrel package from the cygwin-apps cvs tree?  I've read some of the
>script, and it looks like it might make life easier, but it appears to
>need things mounted in particular absolute directories.  If there are
>no such docs, would you be interested in having some?

I never say no to documentation.

cgf

--
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/

Re: Building cygwin1.dll

[rich-paul]

Great, can anyone here provide any tips as to starting points in using
the mknetrel package?  I'll reverse engineer it if need be or to fill in
the blanks, but I'm guessing somebody knows something.  <G>

What I know so far, is before you start using mknetrel, you've gotta
install getopt.

C'mon, lay it on me, I promise they won't make you sleep with the
fishes.

On Sun, Jun 02, 2002 at 02:28:24AM -0400, Christopher Faylor wrote:
> On Sun, Jun 02, 2002 at 12:47:47AM -0400, rich-paul@rich-paul.net wrote:
> >Another question: Are there any directions as to how to use the
> >mknetrel package from the cygwin-apps cvs tree?  I've read some of the
> >script, and it looks like it might make life easier, but it appears to
> >need things mounted in particular absolute directories.  If there are
> >no such docs, would you be interested in having some?
> 
> I never say no to documentation.
> 
> cgf
> 
> --
> 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/

Re: Building cygwin1.dll

[Larry Hall (RFK Partners, Inc)]

At 07:02 PM 5/28/2002, rich-paul@rich-paul.net wrote:
>I meant that what I have built, I did not install through
>setup.exe ...


Ah-ha!  You're the one!  We can't allow this subversion!  You will be 
forever banished!! ;-)

I'd hope that anyone who's capable enough to build Cygwin from source 
would also be capable enough to handle basic configuration issues that
setup helps to automate.  I think people can use their best judgement 
about asking questions in this regard.  But I'd be surprised to see 
any thoughtful question about building Cygwin shot-down based on the 
premise that it's off-topic because setup hasn't been used.  I think 
the person involved here has a different goal than those who are just
looking to install Cygwin.  This list can accommodate both of these 
"types" IMO.


>The faq entry is good as far as it goes, but generally there are
>problems. With my current download I believe they involved a
>present but empty directory (perhaps windows32api?), and a couple
>of other things.  I just removed the subtrees that didn't built,
>and was able to patch and build what I needed.
>
>
>On Tue, May 28, 2002 at 12:28:04PM -0400, Larry Hall (RFK Partners, Inc) wrote:
> > At 12:03 PM 5/28/2002, rich-paul@rich-paul.net wrote:
> > >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'm not sure what "custom building" means but issues with building 
> > the Cygwin DLL are on-topic for this list.  Generally speaking though,
> > the process should be as described in the FAQ entry:
> > 
> > 
> > How do I rebuild the tools on my NT box?
> > http://cygwin.com/faq/faq_4.html#SEC102
> > 
> > 
> > 
> > Larry Hall                              lhall@rfk.com
> > RFK Partners, Inc.                      http://www.rfk.com
> > 838 Washington Street                   (508) 893-9779 - RFK Office
> > Holliston, MA 01746                     (508) 893-9889 - FAX
> > 
> > 
> > --
> > 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/


--
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/

Re: Building cygwin1.dll

[Keen Wayne A Contr AFRL/MNGG]

The utterly sad and pathetic thing is that it took me a period of time, not
best measured in seconds,
to recognize the roflmao character of Chris' statement.

Theres a technical term for that sort of delay, its called DUHHHHHH!

Hey, how do I unsubscribe to this list again?

Waynebozo Keen

--
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/

Re: Building cygwin1.dll

[linguist-cygwin]

Just send a message to the list that says 'Jane get me off this
crazy thing!'

Seriously, though, I once sent a reply to a spam I had received.
My reply read simply 'take me off your list'.  Unfortunately, the
spam had been sent to linguist-linux, which is the addr I use to
subscribe to the linux-kernel list ... they were automatically
cc'd.  So I now when I read those messages, I just cringe.

Ironically, I had unsubscribed from linux kernel weeks before,
so they couldn't, though they surely wanted to!

Wish I knew how to add a prompt to mutt that says, b4 sending to
a list, "To the list, right?".  I'm sure it's easy, if you know
how. ;>


On Tue, May 28, 2002 at 01:16:59PM -0500, Keen Wayne A Contr AFRL/MNGG wrote:
> The utterly sad and pathetic thing is that it took me a period of time, not
> best measured in seconds,
> to recognize the roflmao character of Chris' statement.
> 
> Theres a technical term for that sort of delay, its called DUHHHHHH!
> 
> Hey, how do I unsubscribe to this list again?
> 
> Waynebozo Keen
> 
> --
> 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/

Building cygwin1.dll

[Johan van den Berg]

Any pointers on how to compile cygwin1.dll? I installed cygwin latest onto a windows machine, installed all the prerequisites as per faq (gcc perl et al), downloaded a snapshot, configured and maked but keep running into compile errors.

There is no mention in the docs regarding version of gcc required, possibility of using gcc as supplied by cygwin or mingw, etc.
I am trying to build a custom cygwin1.dll to test http://cygwin.com/ml/cygwin/2011-12/msg00337.html
I have set the send and receive buffers to 256k so that I can get transfer speeds up on a high latency rsync copy from one cygwin windows to another cygwin windows box with over 300ms latency between the two, but a 100mbit bandwidth
I tested with a previous version (very old) of cygwin that had the buffers at 8k and that caused the transfer speeds to go down to next to nothing, so the theory seems sound that increasing the buffers should increase the amount of packets that can be sent without receiving an ack.
I have already patched the code, now I just need to figure out how to actually build cygwin, and 3 hours worth of google + reading of cygwin mailing lists have been fruitless.

The error I get when trying to compile using the default cygwin install of gcc and tools:

... lots of successful compiles, and then:
make[5]: Entering directory `/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/libc/locale'
gcc -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup/cygwin -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup/w32api/lib -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/cygwin/include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/w32api/include -B/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/ -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/targ-include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/newlib/libc/include    -I/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/cygwin/include -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" -DPACKAGE_VERSION=\"1.20.0\" -DPACKAGE_STRING=\"newlib\ 1.20.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -I. -I../../../../../newlib/libc/locale -DHAVE_OPENDIR -DHAVE_RENAME -DSIGNAL_PROVIDED -D_COMPILING_NEWLIB -DHAVE_BLKSIZE -DHAVE_FCNTL -DMALLOC_PROVIDED -fno-builtin      -g -O2 -c -o lib_a-nl_langinfo.o `test -f 'nl_langinfo.c' || echo '../../../../../newlib/libc/locale/'`nl_langinfo.c
../../../../../newlib/libc/locale/nl_langinfo.c:66: error: parse error before "struct"
../../../../../newlib/libc/locale/nl_langinfo.c:66: error: `outdigits' undeclared here (not in a function)
../../../../../newlib/libc/locale/nl_langinfo.c:66: error: initializer element is not constant
../../../../../newlib/libc/locale/nl_langinfo.c:66: error: (near initialization for `nl_ext[0].offset')
../../../../../newlib/libc/locale/nl_langinfo.c:66: error: parse error before ')' token
../../../../../newlib/libc/locale/nl_langinfo.c:66: error: initializer element is not constant
../../../../../newlib/libc/locale/nl_langinfo.c:66: error: (near initialization for `nl_ext[0]')
.... and many more similar complaints.

Johan van den Berg
Play Safe IT Services South Africa (Pty) Ltd
Email: johan.vdberg@playsafesa.com
Skype: johantheitguy




--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Building cygwin1.dll

[marco atzeri]

On 1/4/2012 2:49 PM, Johan van den Berg wrote:
> Any pointers on how to compile cygwin1.dll? I installed cygwin latest onto a windows machine, installed all the prerequisites as per faq (gcc perl et al), downloaded a snapshot, configured and maked but keep running into compile errors.
>
> There is no mention in the docs regarding version of gcc required, possibility of using gcc as supplied by cygwin or mingw, etc.
> I am trying to build a custom cygwin1.dll to test http://cygwin.com/ml/cygwin/2011-12/msg00337.html
> I have set the send and receive buffers to 256k so that I can get transfer speeds up on a high latency rsync copy from one cygwin windows to another cygwin windows box with over 300ms latency between the two, but a 100mbit bandwidth
> I tested with a previous version (very old) of cygwin that had the buffers at 8k and that caused the transfer speeds to go down to next to nothing, so the theory seems sound that increasing the buffers should increase the amount of packets that can be sent without receiving an ack.
> I have already patched the code, now I just need to figure out how to actually build cygwin, and 3 hours worth of google + reading of cygwin mailing lists have been fruitless.
>
> The error I get when trying to compile using the default cygwin install of gcc and tools:
>
> ... lots of successful compiles, and then:
> make[5]: Entering directory `/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/libc/locale'
> gcc -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup/cygwin -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup/w32api/lib -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/cygwin/include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/w32api/include -B/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/ -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/targ-include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/newlib/libc/include    -I/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/cygwin/include -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" -DPACKAGE_VERSION=\"1.20.0\" -DPACKAGE_STRING=\"newlib\ 1.20.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKA
GE_URL=\"\" -I. -I../../../../../newlib/libc/locale -DHAVE_OPENDIR -DHAVE_RENAME -DSIGNAL_PROVIDED -D_COMPILING_NEWLIB -DHAVE_BLKSIZE -DHAVE_FCNTL -DMALLOC_PROVIDED -fno-builtin      -g -O2 -c -o lib_a-nl_langinfo.o `test -f 'nl_langinfo.c' || echo '../../../../../newlib/libc/locale/'`nl_langinfo.c
> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: parse error before "struct"
> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: `outdigits' undeclared here (not in a function)
> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: initializer element is not constant
> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: (near initialization for `nl_ext[0].offset')
> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: parse error before ')' token
> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: initializer element is not constant
> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: (near initialization for `nl_ext[0]')
> .... and many more similar complaints.
>
> Johan van den Berg

hi John,

gcc and g++ version 4.5.3 (GCC)
as provided by cygwin packages

gcc4-core                      4.5.3-3
gcc4-g++                       4.5.3-3

usually this is enough for building

  <source_path>/configure
  make

Regards
Marco



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: Building cygwin1.dll

[Johan van den Berg]

I am very happy to report that increasing the send and receive buffers has done the job (at least, on a 10MBit link but will be testing a 100Mbit in a few days). I calculated the ideal size as per http://www.ibm.com/developerworks/linux/library/l-hisock/index.html

$ diff -u cygwin-snapshot-20111222-1/winsup/cygwin/net.cc.orig cygwin-snapshot-20111222-1/winsup/cygwin/net.cc
--- cygwin-snapshot-20111222-1/winsup/cygwin/net.cc.orig        2012-01-04 06:56:22.094250000 -0500
+++ cygwin-snapshot-20111222-1/winsup/cygwin/net.cc     2012-01-04 07:10:14.031750000 -0500
@@ -569,8 +569,12 @@
      be nice, though.

      (*) Maximum normal TCP window size.  Coincidence?  */
-  ((fhandler_socket *) fd)->rmem () = 65535;
-  ((fhandler_socket *) fd)->wmem () = 65535;
+
+  /* JVDB - 64K is too small for our 100mb link with 200ms latency. Bumped to 2MB
+     See http://www.ibm.com/developerworks/linux/library/l-hisock/index.html */
+
+  ((fhandler_socket *) fd)->rmem () = 2097152;
+  ((fhandler_socket *) fd)->wmem () = 2097152;
   if (::setsockopt (soc, SOL_SOCKET, SO_RCVBUF,
                    (char *) &((fhandler_socket *) fd)->rmem (), sizeof (int)))
     {

Thank you very much for the help!

Kind regards
Johan


On 04 Jan 2012, at 4:24 PM, marco atzeri wrote:

> On 1/4/2012 2:49 PM, Johan van den Berg wrote:
>> Any pointers on how to compile cygwin1.dll? I installed cygwin latest onto a windows machine, installed all the prerequisites as per faq (gcc perl et al), downloaded a snapshot, configured and maked but keep running into compile errors.
>> 
>> There is no mention in the docs regarding version of gcc required, possibility of using gcc as supplied by cygwin or mingw, etc.
>> I am trying to build a custom cygwin1.dll to test http://cygwin.com/ml/cygwin/2011-12/msg00337.html
>> I have set the send and receive buffers to 256k so that I can get transfer speeds up on a high latency rsync copy from one cygwin windows to another cygwin windows box with over 300ms latency between the two, but a 100mbit bandwidth
>> I tested with a previous version (very old) of cygwin that had the buffers at 8k and that caused the transfer speeds to go down to next to nothing, so the theory seems sound that increasing the buffers should increase the amount of packets that can be sent without receiving an ack.
>> I have already patched the code, now I just need to figure out how to actually build cygwin, and 3 hours worth of google + reading of cygwin mailing lists have been fruitless.
>> 
>> The error I get when trying to compile using the default cygwin install of gcc and tools:
>> 
>> ... lots of successful compiles, and then:
>> make[5]: Entering directory `/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/libc/locale'
>> gcc -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup/cygwin -L/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/winsup/w32api/lib -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/cygwin/include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/w32api/include -B/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/ -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/build/i686-pc-cygwin/newlib/targ-include -isystem /home/DBA/cygwin-build/cygwin-snapshot-20111222-1/newlib/libc/include    -I/home/DBA/cygwin-build/cygwin-snapshot-20111222-1/winsup/cygwin/include -DPACKAGE_NAME=\"newlib\" -DPACKAGE_TARNAME=\"newlib\" -DPACKAGE_VERSION=\"1.20.0\" -DPACKAGE_STRING=\"newlib\ 1.20.0\" -DPACKAGE_BUGREPORT=\"\" -DPACKA
> GE_URL=\"\" -I. -I../../../../../newlib/libc/locale -DHAVE_OPENDIR -DHAVE_RENAME -DSIGNAL_PROVIDED -D_COMPILING_NEWLIB -DHAVE_BLKSIZE -DHAVE_FCNTL -DMALLOC_PROVIDED -fno-builtin      -g -O2 -c -o lib_a-nl_langinfo.o `test -f 'nl_langinfo.c' || echo '../../../../../newlib/libc/locale/'`nl_langinfo.c
>> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: parse error before "struct"
>> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: `outdigits' undeclared here (not in a function)
>> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: initializer element is not constant
>> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: (near initialization for `nl_ext[0].offset')
>> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: parse error before ')' token
>> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: initializer element is not constant
>> ../../../../../newlib/libc/locale/nl_langinfo.c:66: error: (near initialization for `nl_ext[0]')
>> .... and many more similar complaints.
>> 
>> Johan van den Berg
> 
> hi John,
> 
> gcc and g++ version 4.5.3 (GCC)
> as provided by cygwin packages
> 
> gcc4-core                      4.5.3-3
> gcc4-g++                       4.5.3-3
> 
> usually this is enough for building
> 
>  <source_path>/configure
>  make
> 
> Regards
> Marco
> 
> 
> 
> --
> Problem reports:       http://cygwin.com/problems.html
> FAQ:                   http://cygwin.com/faq/
> Documentation:         http://cygwin.com/docs.html
> Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
> 


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple