-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[EMAIL PROTECTED] wrote:
> After a Google search, my results did not return a tutorial for
> installing lame. One cygwin thread mentioned compiling the lame source
> code. Other people mentioned using mplayer, which presents the same
> request for a
I want to develop a simple script for converting wave files to mp3s
using the lame encoder. I need too automate the process, which takes
to much time with helper applications like iTunes (opening iTunes,
import the wave files, convert them, populate the ID3 tags). The
script would also take the fi
On Sat 3/10/07 15:55 MST Eric Blake wrote:
> According to Tom Rodman on 3/10/2007 8:14 AM:
> > ~ $ /tmp/foo <(echo ABC)
> > + test -s /proc/self/fd/63
> > + echo 1
> >
> > The 'test -s "$file"' in the test run above should return 0.
>
> How do you figure? pipes are special file types, and
Dave Korn wrote:
>
>> http://www.nabble.com/file/7076/cygcheck.out cygcheck.out
> " Warning: There are multiple cygwin1.dlls on your path "
>
> That's a guaranteed disaster zone right there. Looks like you've been
> nabbled by some http://cygwin.com/acronyms#3PP. Get rid of these files:
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Tom Rodman on 3/10/2007 8:14 AM:
> ~ $ /tmp/foo <(echo ABC)
> + test -s /proc/self/fd/63
> + echo 1
>
> The 'test -s "$file"' in the test run above should return 0.
How do you figure? pipes are special file types, and st_size is
u
On 10 March 2007 21:20, Bogus Bill wrote:
>> Also, do you have any of Norton/MacAffee/Symantec antivirus, Logitech
>> webcam software, Kerio, Agnitum or ZoneAlarm Personal Firewall, LanDesk,
>> or Windows Defender installed?
>>
>
> No, none of those.
STOPzilla could in theory cause problems
Dave Korn wrote:
>
> That's very odd, it should at least have spit out some text. How about
> something simpler: does "/usr/lib/gcc/i686-pc-cygwin/3.4.4/cc1plus.exe
> --help"
> produce any output at all?
>
None.
> Hmm, it's unusual that you haven't got the top-level 'gcc' package
> ins
Norton Allen wrote:
>
>>> I have the same problem. I tried to compile the requisite "Hello,
>>> world!"
>>> program, but gcc didn't give any messages, nor generate any output.
>
> Are you sure this failed, or were you perhaps expecting to find an
> executable called hello.exe? The output I g
On Sat, Mar 10, 2007 at 02:55:54PM -, Dave Korn wrote:
>On 10 March 2007 14:41, seema r j wrote:
>> We are upgrading our application with latest cygwin-1.5.24-2 on windows
>> 2003. we built cygwin against few changes to the IPC system calls. The
>> build was successfull with no errors. But when
test script "/tmp/foo", and test run showing the problem:
~ $ cat /tmp/foo
#!/bin/bash
file=$1
TMPF=$(mktemp /tmp/XX)
set -x
test -s "$file" || echo $?
cp $file $TMPF
cat $TMPF
~ $ /tmp/foo <(echo ABC)
+ test -s /proc/self/fd/63
+ echo 1
1
+ cp /proc/self/fd/63 /tmp
On 10 March 2007 14:41, seema r j wrote:
> Hi All,
> We are upgrading our application with latest cygwin-1.5.24-2 on windows
> 2003. we built cygwin against few changes to the IPC system calls. The
> build was successfull with no errors. But when we made 'make install' we
> encountered the followi
Hi All,
We are upgrading our application with latest cygwin-1.5.24-2 on windows 2003.
we built cygwin against few changes to the IPC system calls. The build was
successfull with no errors. But when we made 'make install' we encountered the
following errors.
make[3]: *** [cygserver.exe] Error 1
m
Hi all,
I'm getting a conflict on several different machines between ruby and
cygssl-0.9.8.dll. Here's an example:
8 [main] ruby 3280 E:\cygwin\bin\ruby.exe: *** fatal error - unable to
remap E:\cygwin\bin\cygssl-0.9.8.dll to same address as parent(0x34)
!= 0x473
9 [main] ruby 3392
13 matches
Mail list logo
