Hello,
* Paul Eggert wrote on Wed, Apr 29, 2009 at 09:47:19PM CEST:
[
$ ( trap "echo foo" 0; :; true )
$ ( trap "echo foo" 0; true; : )
foo
]
>
>> Better it would be to say: "On Solaris 9, /bin/sh may not execute a
>> trap on exit if the trap is defined in a parenthesised sub-shell."
>>
>
On Wednesday 29 April 2009 16:22:08 Andreas Schwab wrote:
> Mike Frysinger writes:
> > http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#t
> >rap If the first operand is an unsigned decimal integer, the shell shall
> > treat all operands as conditions, and shall reset each co
Mike Frysinger writes:
> http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#trap
> If the first operand is an unsigned decimal integer, the shell shall treat
> all
> operands as conditions, and shall reset each condition to the default value.
> Otherwise, if there are oper
On Wednesday 29 April 2009 15:47:19 Paul Eggert wrote:
> > It seems that 'trap 1 2 13 15' (without any command) reset the traps
> > in a reasonably portable way,
>
> I'm afraid not. For example, on Ubuntu 9.04:
>
> $ dash
> !-penguin $ trap 1 2
> !-penguin $ kill -2 $$
> dash: 1: not found
>
> It'
It seems that 'trap 1 2 13 15' (without any command) reset the traps
in a reasonably portable way,
I'm afraid not. For example, on Ubuntu 9.04:
$ dash
!-penguin $ trap 1 2
!-penguin $ kill -2 $$
dash: 1: not found
It's hard to argue that this is a bug, since POSIX requires this behavior.
Be
Hello Thies,
* Thies Jochimsen wrote on Wed, Apr 29, 2009 at 08:22:41PM CEST:
>
> sorry, it was my mistake. It was a complex interplay between the cross
> compiler (for VxWorks), a (lousy) wrapper script for the compiler, and the
> new way autoconf checks for the executable bit off binaries. I
Hello Nicolas,
> On Wednesday 29 April 2009 12:20:05 ORMANCEY Nicolas wrote:
>
> > But it still not working and now I crash in the generated makefile...
> > Where is my mistake
You are providing far too little information in order to be able to help
you. Post at least the commands you used, plu
Dear Ralf,
sorry, it was my mistake. It was a complex interplay between the cross
compiler (for VxWorks), a (lousy) wrapper script for the compiler, and the
new way autoconf checks for the executable bit off binaries. I fixed the
wrapper and now everything is fine...
Thanks, however, for your
On Wednesday 29 April 2009 17:21:58 Zainab Qureshi wrote:
> This is the error i am getting. C:/check is where i have placed
> configure.ac
>
> autoconf configure.ac
> /mingw/bin/autoconf: /c/check/C:/MinGW/bin/autom4te: No such file
> or
This looks well messed up. Since your problem is very spec
Hi Nicolas,
you should keep the discussion in the mailing list, in order that others can
also help you.
That said,
On Wednesday 29 April 2009 12:20:05 you wrote:
> Hi Alberto,
>
> So I have declared
> CPPFLAGS and LDFLAGS on my Makefile.am
> And added in my configure.AC
> CPPFLAGS = -I/myPath/i
Thanks for the help John.
This is the error i am getting. C:/check is where i have placed configure.ac
autoconf configure.ac
/mingw/bin/autoconf: /c/check/C:/MinGW/bin/autom4te: No such file or
directory
/mingw/bin/autoconf: exec: /c/check/C:/MinGW/bin/autom4te: cannot exe
cute: No suc
All the instances of autoconf in config.log is what i have already mailed. When
i check for the versions of autoconf and automake they give me
autoconf --version
autoconf (GNU Autoconf) 2.59
Written by David J. MacKenzie and Akim Demaille.
automake --version
automake (GNU automake) 1.7.1
Writte
Hi.
I am referring to the autoconf manual that I found on savannah.org under path
/autoconf/manual/autoconf-2.63.
Some more issues, continuing the list I started in my previous mail:
Issue 3:
-
Another reason to be careful with "set -e" on Solaris 10: A failing command
substitution ma
Hi.
I am referring to the autoconf manual that I found on savannah.org under path
/autoconf/manual/autoconf-2.63.
Issue 1:
-
There it says in section "Limitation of Shell Builtins":
Posix says that trap - 1 2 13 15 resets the traps for the specified signals
to
their default valu
On 4/29/2009 9:05 AM, Zainab Qureshi wrote:
Hi,I am having problems while installing GNURadio on windows xp. The problem
lies with autoconf. In config.log i get the following error
AUTOCONF='${SHELL} /c/gnuradio-3.1.3/missing --run autoconf'
AUTOHEADER='${SHELL} /c/gnuradio-3.1.3/missing --run a
Hi,I am having problems while installing GNURadio on windows xp. The problem
lies with autoconf. In config.log i get the following error
AUTOCONF='${SHELL} /c/gnuradio-3.1.3/missing --run autoconf'
AUTOHEADER='${SHELL} /c/gnuradio-3.1.3/missing --run autoheader'
AUTOMAKE='${SHELL} /c/gnuradio-3.1.
16 matches
Mail list logo