Why is Cygwin1.dll monolithic?

2006-06-10 Thread Václav Haisman
Today I woke up and one of the first things that came on my mind was
this: Why isn't Cygwin1.dll devided to the "kernel" and separate C library?

--
Vaclav Haisman

PS: I am not trying to suggest anything or to troll, I am merely curious.



signature.asc
Description: OpenPGP digital signature


Re: Why is Cygwin1.dll monolithic?

2006-06-10 Thread Erich Dollansky

Hi,

Václav Haisman wrote:

Today I woke up and one of the first things that came on my mind was
this: Why isn't Cygwin1.dll devided to the "kernel" and separate C library?


isn't it just the API?

So why should there be a 'kernel'?

Erich


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



Re: Why is Cygwin1.dll monolithic?

2006-06-10 Thread Christopher Faylor
On Sat, Jun 10, 2006 at 12:28:00PM +0200, V??clav Haisman wrote:
>Today I woke up and one of the first things that came on my mind was
>this: Why isn't Cygwin1.dll devided to the "kernel" and separate C library?

Maybe you should outline the benefits of such a plan since I can only
see drawbacks.  Both DLLs would have to be loaded by every application
anyway.  That means two separate directory lookups.  And, the "separate
C library" would suffer from dll load-time issues with accessing data
and functions, i.e., it would be slower than the current way of doing
things.  And, then, there would be the "It says cyglibc.dll not found.
Why it not there?" issues that are sure to crop up.

So, other than the esoteric issue of isolating things into separate
regions for maintenance sake, I don't see any end-user benefits.

cgf

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



Re: [ANNOUNCEMENT] Updated: swig-1.3.29-1

2006-06-10 Thread Richard Graham
Until swig-1.3.29-2 becomes available, here's how you can get
swig-1.3.29-1 to work (it's missing "swigwarn.swg"):

1. Download source with setup.exe
2. cd to /usr/src (within your cygwin directory)
3. execute "./swig-1.3.29-1.sh conf"
4. "cd swig-1.3.29/.build"
5. "make Lib/swigwarn.swg"
6. "cp Lib/swigwarn.swg /usr/share/swig/1.3.29"

Richard Graham


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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



gpg-agent: only one trouble before succesfull building

2006-06-10 Thread [EMAIL PROTECTED]

Hello,
This is a detailed story about the try to build gpg-agent under cygwin
I whish to use gpg-agent under cygwin, that is contained in the 
gnupg-1.9 tree only.


Here is what I have done:

#Install prerequisites

## libpth-1.4.4
cd /usr/src/
wget ftp://ftp.gnu.org/gnu/pth/pth-1.4.1.tar.gz
tar xvzf pth-1.4.1.tar.gz
cd pth-1.4.1
./configure
make
make test
make install

#libassuan
cd /usr/src/
wget ftp://ftp.gnupg.org/gcrypt/alpha/libassuan/libassuan-0.6.10.tar.gz
tar xvzf libassuan-0.6.10.tar.gz
cd
./configure
make
make install

#Installed this from official archives with setup.exe
# this is needed by libksba
# gettext

#libksba
cd /usr/src/
wget ftp://ftp.gnupg.org/gcrypt/alpha/libksba/libksba-0.9.14.tar.bz2
tar xvjf libksba-0.9.14.tar.bz2
cd libksba-0.9.14
./configure
make
make install

#Installed this from official archives with setup.exe
#libgpg-error
#libgcrypt

## Now the big ball
cd /usr/src
wget ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.9.20.tar.bz2
tar xvjf gnupg-1.9.20.tar.bz2
cd gnupg-1.9.20
./configure --enable-agent-only
make

And now the funny part:
...
gcc   -I/usr/local/include -g -O2 -Wall   -o gpg-connect-agent.exe  
gpg-connect-agent.o no-libgcrypt.o ../jnlib/libjnlib.a 
../common/libcommon.a ../gl/libgnu.a -L/usr/local/lib -lassuan 
-lgpg-error -lintl -lz

/usr/local/lib/libassuan.a(assuan-io.o): In function `_assuan_simple_read':
/usr/src/libassuan-0.6.10/src/assuan-io.c:44: undefined reference to 
`_pth_read'

/usr/local/lib/libassuan.a(assuan-io.o): In function `_assuan_simple_write':
/usr/src/libassuan-0.6.10/src/assuan-io.c:55: undefined reference to 
`_pth_write'

collect2: ld returned 1 exit status
make[2]: *** [gpg-connect-agent.exe] Error 1
make[2]: Leaving directory `/usr/src/gnupg-1.9.20/tools'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/src/gnupg-1.9.20'
make: *** [all] Error 2

Ok, we lack "pthread support" ?
I investigated and found out that the make of libassuan said:
...
assuan-io.c:32: warning: weak declaration of 'pth_read' not supported
assuan-io.c:33: warning: weak declaration of 'pth_write' not supported
...

Mmmmh seems we need to add support when configuring
I read the docs of pth-1.4.1 and found the configure switch for this, but:

./configure --enable-pthread
...
make
...
./libtool --mode=compile --quiet gcc -c -I. -O2 -pipe pthread.c
In file included from pthread.c:42:
pthread.h:184: warning: useless keyword or type name in empty declaration
pthread.h:184: warning: empty declaration
pthread.h:347: error: conflicting types for 'pthread_kill'
/usr/include/sys/signal.h:163: error: previous declaration of 
'pthread_kill' was here

pthread.h:347: error: conflicting types for 'pthread_kill'
/usr/include/sys/signal.h:163: error: previous declaration of 
'pthread_kill' was here

make: *** [pthread.lo] Error 1

I cant' go out of this

Please help !

--
Diesis

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



unix 'at' command implementation

2006-06-10 Thread Yossi Cohen

Hi.

I have cygwin install but I can not find the
implementation of Unix 'at' command.

Is there a different way to get the 'at' function ?

thanks.

__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

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



Re: unix 'at' command implementation

2006-06-10 Thread Eric Blake
> I have cygwin install but I can not find the
> implementation of Unix 'at' command.

Because no one has ported an open source version of it
to cygwin yet.

> 
> Is there a different way to get the 'at' function ?

You could try using cron instead.  True, it's not POSIX,
but at least it is already ported.

-- 
Eric Blake



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



Re: Issue with Find command on windows NT

2006-06-10 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

According to [EMAIL PROTECTED] on 6/8/2006 1:18 PM:
>  
> Hi,
> I tried using find I:\ -noleaf -print ,but I am getting the
> same error .
> Part of the error is as follows.
> 
> D:\usr\meta\boxster\boxster_UNITw2kMixednew\boxster_UNITw2kMixednew_0245
>> find I:\ode.boxster_UNITw2kMixednew_0228 -noleaf -print

Since you are on cygwin, I would recommend using POSIX-style paths:
find /cygdrive/i/ode.boxster_UNITw2kMixednew_0228

> find: /cygdrive/i changed during execution of find (old inode number
> -506580184,
>  new inode number -509781400, filesystem type is system) [ref 1114]

This is a known issue with cygwin 1.5.19 which has been solved by using
snapshots.  It is not a bug in find, but in older remote drive samba
servers; CVS cygwin is able to work around this bug in samba but 1.5.19
was not.

- --
Life is short - so eat dessert first!

Eric Blake [EMAIL PROTECTED]
volunteer cygwin findutils maintainer
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.2.1 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEizHk84KuGfSFAYARAh9UAJ9c/QLhUtbHhBs9ojVyKnM6LsS7zwCcDlfo
CQv0AP1/fWd5KcBniMX4WUs=
=iKh1
-END PGP SIGNATURE-

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



Re: gpg-agent: only one trouble before succesfull building

2006-06-10 Thread René Berber
gabriele wrote:

> This is a detailed story about the try to build gpg-agent under cygwin
> I whish to use gpg-agent under cygwin, that is contained in the
> gnupg-1.9 tree only.
> 
> Here is what I have done:
> 
> #Install prerequisites
> 
> ## libpth-1.4.4
> cd /usr/src/
> wget ftp://ftp.gnu.org/gnu/pth/pth-1.4.1.tar.gz
> tar xvzf pth-1.4.1.tar.gz
> cd pth-1.4.1
> ./configure
> make
> make test

It's "make check".

> make install

Why use that old version? pth-2.0.6 is what I used.

> #libassuan
> cd /usr/src/
> wget ftp://ftp.gnupg.org/gcrypt/alpha/libassuan/libassuan-0.6.10.tar.gz
> tar xvzf libassuan-0.6.10.tar.gz
> cd
> ./configure
> make

Should also do "make check" just to be sure.

> make install
> 
> #Installed this from official archives with setup.exe
> # this is needed by libksba
> # gettext
> 
> #libksba
> cd /usr/src/
> wget ftp://ftp.gnupg.org/gcrypt/alpha/libksba/libksba-0.9.14.tar.bz2
> tar xvjf libksba-0.9.14.tar.bz2
> cd libksba-0.9.14
> ./configure
> make

Same here, "make check".

> make install
> 
> #Installed this from official archives with setup.exe
> #libgpg-error
> #libgcrypt
> 
> ## Now the big ball
> cd /usr/src
> wget ftp://ftp.gnupg.org/gcrypt/alpha/gnupg/gnupg-1.9.20.tar.bz2
> tar xvjf gnupg-1.9.20.tar.bz2
> cd gnupg-1.9.20
> ./configure --enable-agent-only
> make
> 
> And now the funny part:
> ...
> gcc   -I/usr/local/include -g -O2 -Wall   -o gpg-connect-agent.exe 
> gpg-connect-agent.o no-libgcrypt.o ../jnlib/libjnlib.a
> ../common/libcommon.a ../gl/libgnu.a -L/usr/local/lib -lassuan
> -lgpg-error -lintl -lz
> /usr/local/lib/libassuan.a(assuan-io.o): In function `_assuan_simple_read':
> /usr/src/libassuan-0.6.10/src/assuan-io.c:44: undefined reference to
> `_pth_read'
> /usr/local/lib/libassuan.a(assuan-io.o): In function
> `_assuan_simple_write':
> /usr/src/libassuan-0.6.10/src/assuan-io.c:55: undefined reference to
> `_pth_write'
> collect2: ld returned 1 exit status
> make[2]: *** [gpg-connect-agent.exe] Error 1
> make[2]: Leaving directory `/usr/src/gnupg-1.9.20/tools'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/usr/src/gnupg-1.9.20'
> make: *** [all] Error 2
> 
> Ok, we lack "pthread support" ?
[snip]

Wrong, it's not pthread support is pth as in portable threads, and obviously you
had just built it... the real problem is that the compile command is wrong, if
you try by hand the correct command it will work:

gcc -g -O2 -Wall -o gpg-connect-agent.exe  gpg-connect-agent.o no-libgcrypt.o
../jnlib/libjnlib.a ../common/libcommon.a ../gl/libgnu.a -lassuan -lpth
-lgpg-error -lintl -lz

The only difference is "-lpth" which is the output of "/usr/bin/pth-config
--libs" (or in your case /usr/local/bin/...).  So the problem was really an
error on the generated Makefile, you should report it to gnupg.

Regards.
-- 
René Berber


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



RPM's (was Re: unix 'at' command implementation)

2006-06-10 Thread Linda Walsh

Eric Blake wrote:

I have cygwin install but I can not find the
implementation of Unix 'at' command.


Because no one has ported an open source version of it
to cygwin yet.
  


   Some packages might be more easily ported if RPM's
became a common way to package cygwin packages.  Much
of the porting effort is in converting to the cygwin installer.
Someone asked about logrotation a while back and I was
surprised no one had ported a logrotate package.  I pulled
the source RPM from my SuSE distro, and was able to
produce a binary RPM in about 10 minutes, then I realized
RPM's weren't a desirable format for cygwin packages.

   I'm sure there's some good reason for converting all
packages to yet another installer, but I'm not sure I know
what they are.  One side effect, though -- it can  put a
damper on porting programs over when most (or all) of the
work is in converting to the a different installer.

-l





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



Re: RPM's (was Re: unix 'at' command implementation)

2006-06-10 Thread Larry Hall (Cygwin)

Linda Walsh wrote:

Eric Blake wrote:

I have cygwin install but I can not find the
implementation of Unix 'at' command.


Because no one has ported an open source version of it
to cygwin yet.
  


   Some packages might be more easily ported if RPM's
became a common way to package cygwin packages.  Much
of the porting effort is in converting to the cygwin installer.
Someone asked about logrotation a while back and I was
surprised no one had ported a logrotate package.  I pulled
the source RPM from my SuSE distro, and was able to
produce a binary RPM in about 10 minutes, then I realized
RPM's weren't a desirable format for cygwin packages.

   I'm sure there's some good reason for converting all
packages to yet another installer, but I'm not sure I know
what they are.  One side effect, though -- it can  put a
damper on porting programs over when most (or all) of the
work is in converting to the a different installer.



Support for RPM and DEB packages were always intended for setup.exe.
It's just no one has added this support yet.  Anyone who's interested
is certainly welcome to provide patches to reach this goal.  I'm sure
they will be thoughtfully considered.


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

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