Hi!
The attached shell-script causes cygpath to malfunction by trying to
convert a long string of z:s using 'cygpath -w'. It begins by trying "z",
then "zz", and so on.
When trying more than 240 z:s, the result becomes garbled. For example:
246
z
nes
certain symbols. This is why import libraries are used; to make sure all
symbols are resolved at link-time. As a result, Windows DLLs are not
allowed to contain unresolved symbols.
A much cleaner design, IMHO.
/Jesper
--
Jesper Eskilson
Virtutech
http://www.virtutech.com
--
Unsu
people who can help you. Otherwise
you'll just get a "because we're mean" response from CGF. ;-)
/Jesper
--
Jesper Eskilson
Virtutech
http://www.virtutech.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bu
"Kristopher Buschelman" <[EMAIL PROTECTED]> writes:
> Then, from the MS-VisualStudio c language code, I make DYNAMIC calls to the
> wrapper routine via GetProcAddress It works fine, but making the
> wrapper is a bit less than desirable, not because of the dynamic call --
> which I want anywa
"Norman Vine" <[EMAIL PROTECTED]> writes:
> Since this question comes up quite frequently
> maybe we could add the following 'tip' to the faq
>
> Q) What preprocessor symbols does Cygwin define
> A) Use the tool Luke :-)
>
> % echo > jnk.c
> % gcc -E -dM jnk.c
> % gcc -mno-cygwin -E -dM jnk.c
"Larry Hall (RFK Partners, Inc)" <[EMAIL PROTECTED]> writes:
> Check out Winsock capabilities in this area. Cygwin's socket support is
> dependent on Winsock functionality.
If you want to be able to send and receive raw ethernet frames, your best
be is to take a look at WinPcap. (Use Google; I
[EMAIL PROTECTED] writes:
> ot find -luser32
> collect2: ld returned 1 exit status
> make: *** [rom] Error 1
Check the mailing list archives, there has been a bunch of postings on this
topic the last week or so.
--
/Jesper
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bu
"Robert Collins" <[EMAIL PROTECTED]> writes:
> make -j serialises at directory borders (at a minimum). You might like
> to review the 'recursive make considered harmful' paper (if you haven't
> already).
'make -j' and recursive make are orthogonal issues.
--
/Jesper
--
Unsubscribe info:
"Gary R. Van Sickle" <[EMAIL PROTECTED]> writes:
> # Why should this...:
> rm //a/bunch/of/files/out/on/a/super/slow/server/*
> # ...block this:
> gcc hello.c
>
> Obviously you're never going to be able to take advatage of all
> non-dependencies, but as a wise man once told me, "you can't win if
Christopher Faylor <[EMAIL PROTECTED]> writes:
> Either that or something like (untested):
>
> mkdir c:\cygwin
> cd c:\cygwin
> c:\whereever\tar xjf /cygdrive/c/whereever/cygwin-*.tar.bz2
> mount -f -s -b c:/cygwin /
> mount -f -s -b c:/cygwin/lib /usr/lib
> mount -f -s -
10 matches
Mail list logo