At:
http://www.cygwin.com/ml/cygwin/2009-01/msg00848.html
Charles Wilson said:
Greg said
>>
>>I use '--build=i686-pc-mingw32 --host=i686-pc-mingw32'. Here:
>> http://lists.gnu.org/archive/html/libtool-patches/2009-01/msg00193.html
>>you say that's lying to 'configure', but you also observe that
>
Marco Atzeri yahoo.it> writes:
> RTFM
>
> man last
> touch /var/log/wtmp
uh - thanks!
Ronald
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: ht
Danny Smith wrote:
> The reasons I use "--build=mingw32 --host=mingw32 --target=mingw32"
> when building gcc are
> 1) I have, perhaps mistakenly, assumed that "--build=" referred to the OS of
> the compiler,
> not the ethnicity of the shell.
I've assumed it was describing the entire build enviro
Charles Wilson wrote:
[describe "old" libtool behavior; what I called "current gcc libtool"]
> 1) creates both a wrapper script foo and wrapper exe foo.exe in the
> build directory, and also (?) a copy of the wrapper script in .libs/
> 2) the wrapper exe execs the wrapper script via $SHELL
> 3)
Is there a way to get /sbin/sysctl -a running on cygwin? I get
error: unable to open directory "/proc/sys/"
and indeed, there is no sys under proc. Under what conditions is /proc/sys
created on cygwin?
Ronald
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem report
On Jan 29 11:14, Ronald Fischer wrote:
> Is there a way to get /sbin/sysctl -a running on cygwin? I get
>
> error: unable to open directory "/proc/sys/"
>
> and indeed, there is no sys under proc. Under what conditions is /proc/sys
> created on cygwin?
There's no implementation of a virtual /p
Hi Reini,
Reini Urban wrote:
> The importlib /usr/lib/w32api/libglut32.a has some problems. Linking
> to the dll directly works fine.
>
> $ cat test.c
> #include
> #include
> #include
> int main(int argc, char *argv[])
> {
> if(glutInit == NULL) {
> printf("glutInit is NULL\n"
On Jan 28 15:46, Gregory Sharp wrote:
> Hi,
>
> > That makes sense. I changed ENOSHARE to ENOENT throughout.
>
> I upgraded my cygwin 1.7 today, but cygwin+find+UDFS still
> reboots my windows 2000 computer.
Here's a question: Did you switch on case sensitivity as per
http://cygwin.com/1.7/cy
> I'm using a Perl script, available at
> http://www.frexx.de/xterm-256-notes/data/256colors2.pl, to test whether my
> terminal is giving me 256 colors.
Thanks, this is helpful.
> It works when I run it from a vanilla bash
> prompt, but not from within Screen, even after I installed your build.
Hi,
I want to read filenames from a file and manipulate this files with the windows
program "attrib".
Not easy to find how to read windows filenames from a file without lost of "\".
while IFS= read -r cLine
do
echo "$cLine"
done < restoreFiles.tmp
The above will work. BUT:
while IFS= re
On Thu, 29 Jan 2009, Matthias Meyer wrote:
while IFS= read -r cLine
do
echo "$cLine"
attrib +H "$cLine"
done < restoreFiles.tmp
rm -f restoreFiles.tmp
will stop the while loop after the first call of attrib:
+ echo 'C:\Dokumente und
Einstellungen\Administrator\Anwendungsdaten\Mic
What is up with the size of jmp_buf?
It appears that setjmp.h confuses bytes and ints.
_JBLEN should be 13, not 13*4.
or #define _JBTYPE to char, but that doesn't work as easily.
?
- Jay
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.c
Tim McDaniel wrote:
> Given that the debug output has "attrib +S" but the code at top has
> "attrib +H", and that the debug output has "test 0 -gt 0" that the
> code doesn't have just before the loop exit, it is probably necessary
> for you to publish the actual code that's failing, even if it has
For what it's worth, I've had intermittent problems with bash and
while read loops where the loop aborts after one iteration whenever
there's nontrivial code in the loop body, on multiple platforms, not
just Cygwin. So this might not be a Cygwin issue. I've never been
ble to isolate the problem e
On Thu, Jan 29, 2009 at 05:07:42PM +, Jay wrote:
>
>What is up with the size of jmp_buf?
>It appears that setjmp.h confuses bytes and ints.
>_JBLEN should be 13, not 13*4.
>or #define _JBTYPE to char, but that doesn't work as easily.
Huh. You would think that the fact that Cygwin's definition
Andrew Schulman writes:
> TERM=screen-256color screen
>
> gives 256 colors, at least in Cygwin 1.5. Can you confirm this?
Yes. Beautiful, Andrew.
You said you needed text for the release announcement. I'm not sure what it's
supposed to look like, but you can use this, if it works:
screen-
Lee D. Rothstein wrote:
Interesting feature or bug of MinTTY that does not obtain with any other
terminal emulator with which I'm familiar.
To wit:
If you have a running synchronous script or command to the screen and you
type ^l (Ctrl-l) it will immediately clear the screen before the ongoing
> screen-256color: GNU Screen compiled with the --enable-colors256 flag; without
> this flag, terminals launched from within Screen can only show 16 colors.
> Depending on your terminal, you may need to launch Screen as
> 'TERM=screen-256color screen' in order for 256 colors to work.
OK, thanks.
syllk wrote:
> I am hoping that there is a simple fix to this. I am new to cygwin and tinyos
> and when running cygwin it immediately runs with this first line 'bash: [:
> /home/Chris: binary operator expected'. With this problem I seem to get
> errors whenever I try to 'make' anything.
>
> If anyo
Mark J. Reed wrote:
> For what it's worth, I've had intermittent problems with bash and
> while read loops where the loop aborts after one iteration whenever
> there's nontrivial code in the loop body, on multiple platforms, not
> just Cygwin. So this might not be a Cygwin issue. I've never been
The text below is from a text file. If I type the commands line-by-line in
the bash then the commands work as expected. If I save the commands in a
text file and call the script I get the error message:
': not a valid identifier2: declare: 'Red
': not a valid identifier3: declare: 'Green
#! /cy
On Thu, 29 Jan 2009, whitewall wrote:
The text below is from a text file. If I type the commands
line-by-line in the bash then the commands work as expected. If I
save the commands in a text file and call the script I get the error
message:
': not a valid identifier2: declare: 'Red
': not a va
On Thu, Jan 29, 2009 at 5:54 PM, whitewall wrote:
>
> The text below is from a text file. If I type the commands line-by-line in
> the bash then the commands work as expected. If I save the commands in a
> text file and call the script I get the error message:
> ': not a valid identifier2: declar
Andrew Schulman writes:
> I'm curious: where do you use this?
Well, I'll admit to some degree that it's yak shaving
(http://projects.csail.mit.edu/gsb/old-archive/gsb-archive/gsb2000-02-11.html),
but the use case for me is running Screen locally and having multiple terminals
open remotely, with
On Thu, 29 Jan 2009, Mark J. Reed wrote:
On Thu, Jan 29, 2009 at 5:54 PM, whitewall wrote:
#! /cygdrive/c/cygwin/bin/bash
declare -i Red
declare -i Green
Red=10
Green=$Red+1
Since you've declared both Green and Red as integer, you should just
do Green=Red+1, without the dollar sign. Doing Gree
25 matches
Mail list logo
