On 8/28/07, t0nedef <[EMAIL PROTECTED]> wrote:
>
>
> WORK_PATH=/etc/wpa_helper # Storage directory DO NOT MODIFY
> WORK_FILE=$WORKPATH/$ESSID.conf # Configuration file DO NOT MODIFY
> if [ ! -e $WORKPATH ]
> if [ ! -e $WORKFILE ]
also you use WORK_PATH WORKPATH WORKFILE WORK_FILE
On 8/28/07, t0nedef <[EMAIL PROTECTED]> wrote:
>
> Ok, i wrote this script to help with wpa wireless connections, but for some
> reason, it errors out. It says that the ESSID is empty. I've double checked
> my syntax, and it looks right to me. *yes, i did double check the syntax for
> the read comm
Ok, i wrote this script to help with wpa wireless connections, but for some
reason, it errors out. It says that the ESSID is empty. I've double checked
my syntax, and it looks right to me. *yes, i did double check the syntax for
the read command*
well heres the code:
#!/bin/bash
#
# Script: wpa_
On Monday 27 August 2007, Chet Ramey wrote:
> > cross-compiling bash is known to be broken as it'll mix your host signal
> > defs into the target binary
>
> This is no longer true; bash-3.2 builds the signal list at invocation time
> rather than compile time when cross-compiling.
ah, i missed that
Chet Ramey wrote:
Christian Boon wrote:
Hello,
i want to cross compile bash-3.2 for my pxa255 arm processor and its
working although i can't get job control working.
It tells you it won't be able to:
checking for presence of necessary job control definitions... configure:
WARNING
Christian Boon wrote:
> Hello,
>
> i want to cross compile bash-3.2 for my pxa255 arm processor and its
> working although i can't get job control working.
It tells you it won't be able to:
> checking for presence of necessary job control definitions... configure:
> WARNING: cannot check job con
Chet Ramey wrote:
cross-compiling bash is known to be broken as it'll mix your host signal defs
into the target binary
This is no longer true; bash-3.2 builds the signal list at invocation time
rather than compile time when cross-compiling.
Chet
so what do i need to have job control
Mike Frysinger wrote:
On Monday 27 August 2007, Christian Boon wrote:
i want to cross compile bash-3.2 for my pxa255 arm processor and its
working although i can't get job control working.
cross-compiling bash is known to be broken as it'll mix your host signal defs
into the target bi
> cross-compiling bash is known to be broken as it'll mix your host signal defs
> into the target binary
This is no longer true; bash-3.2 builds the signal list at invocation time
rather than compile time when cross-compiling.
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
On Monday 27 August 2007, Christian Boon wrote:
> i want to cross compile bash-3.2 for my pxa255 arm processor and its
> working although i can't get job control working.
cross-compiling bash is known to be broken as it'll mix your host signal defs
into the target binary
-mike
signature.asc
Des
Hello,
i want to cross compile bash-3.2 for my pxa255 arm processor and its
working although i can't get job control working.
i configure bash with:
bash-3.2]$ ./configure --host=arm-xscale-linux-gnueabi
--without-bash-malloc --enable-job-control
in the output i see:
checking if opendir(
11 matches
Mail list logo
