On Sun, Mar 05, 2006 at 04:01:19AM -0500, Kris Kennaway wrote:
On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote:
* Kris Kennaway [EMAIL PROTECTED] [2006-03-05 03:41 -0500]:
On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote:
The problem seems to depend on
On Mon, Mar 06, 2006 at 04:59:42PM -0500, Kris Kennaway wrote:
On Sun, Mar 05, 2006 at 04:01:19AM -0500, Kris Kennaway wrote:
On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote:
* Kris Kennaway [EMAIL PROTECTED] [2006-03-05 03:41 -0500]:
On Sun, Mar 05, 2006 at 09:36:25AM
* Nicolas Rachinsky [EMAIL PROTECTED] [2006-03-03 18:56 +0100]:
Version 3.1.10 (which is the latest AFAIK) of the port contains the
problem, at least here using FreeBSD 4.11.
The problem seems to depend on the installed bison version. With no
bison or bison-2.1_1 installed it works fine, with
On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote:
* Nicolas Rachinsky [EMAIL PROTECTED] [2006-03-03 18:56 +0100]:
Version 3.1.10 (which is the latest AFAIK) of the port contains the
problem, at least here using FreeBSD 4.11.
The problem seems to depend on the installed
* Kris Kennaway [EMAIL PROTECTED] [2006-03-05 03:41 -0500]:
On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote:
The problem seems to depend on the installed bison version. With no
bison or bison-2.1_1 installed it works fine, with bison-1.75_2,1 it
doesn't.
Installed at
On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote:
* Kris Kennaway [EMAIL PROTECTED] [2006-03-05 03:41 -0500]:
On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote:
The problem seems to depend on the installed bison version. With no
bison or bison-2.1_1
Kris Kennaway wrote:
On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote:
* Kris Kennaway [EMAIL PROTECTED] [2006-03-05 03:41 -0500]:
On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote:
The problem seems to depend on the installed bison version. With no
bison
Rainer Alves wrote:
Yes, this fixes the problem. Using devel/bison2 instead of 1.75 also
works, but switching to the builtin YACC is indeed a better solution.
Ditto. Works here.
___
freebsd-stable@freebsd.org mailing list
Mike Jakubik wrote:
FYI.
This has been a known issue with bison-1.75 for over three years:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=167635;archive=yes
http://lists.gnu.org/archive/html/bug-bash/2003-01/msg00061.html
http://lists.gnu.org/archive/html/bug-bash/2004-09/msg00118.html
Chet
On 03/05/06 04:12, Rainer Alves wrote:
Kris Kennaway wrote:
On Sun, Mar 05, 2006 at 09:57:54AM +0100, Nicolas Rachinsky wrote:
* Kris Kennaway [EMAIL PROTECTED] [2006-03-05 03:41 -0500]:
On Sun, Mar 05, 2006 at 09:36:25AM +0100, Nicolas Rachinsky wrote:
The problem seems to depend on the
FYI, in case there was any doubt, this annoying bug is also present in
a recent 6.0-STABLE (Sat Jan 14) on amd 64.
CONFIG_SHELL=/bin/sh is a fix.
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
Sam Sirlin wrote:
FYI, in case there was any doubt, this annoying bug is also present in
a recent 6.0-STABLE (Sat Jan 14) on amd 64.
CONFIG_SHELL=/bin/sh is a fix.
Shouldn't the port be marked broken or reverted to a working copy in
that case?
On Sat, Mar 04, 2006 at 07:33:00PM -0500, Mike Jakubik wrote:
Sam Sirlin wrote:
FYI, in case there was any doubt, this annoying bug is also present in
a recent 6.0-STABLE (Sat Jan 14) on amd 64.
CONFIG_SHELL=/bin/sh is a fix.
Shouldn't the port be marked broken or reverted to a
Kris Kennaway wrote:
On Sat, Mar 04, 2006 at 07:33:00PM -0500, Mike Jakubik wrote:
Shouldn't the port be marked broken or reverted to a working copy in
that case?
The preference is to fix it, of course, but if that can't happen in
the next day or two we'll do one or the other for the
Hello!
I'm not sure when, but may be after last portupgrade configure
scripts began ignoring command-line parameters. E. g. each configure
script i started does (doesn't) the same.
Where the problem can hides?
---
bio3k
pgprzdes7FVSo.pgp
Description: PGP signature
* Elisey O. Savateev [EMAIL PROTECTED] [2006-03-03 15:47 +0500]:
I'm not sure when, but may be after last portupgrade configure
scripts began ignoring command-line parameters. E. g. each configure
script i started does (doesn't) the same.
Where the problem can hides?
Do you have
Fri, 3 Mar 2006 11:56:09 +0100
Nicolas Rachinsky [EMAIL PROTECTED] wrote:
Do you have shells/bash (bash-3.1.10) installed?
Yes. I have.
---
Elisey O. Savateev [EMAIL PROTECTED]
http://bio3k.softboard.ru | ICQ: 955583
PGP/GPG pubkey: http://bio3k.softboard.ru/uploads/etc/pubkey.asc
* Elisey O. Savateev [EMAIL PROTECTED] [2006-03-03 16:10 +0500]:
Fri, 3 Mar 2006 11:56:09 +0100
Nicolas Rachinsky [EMAIL PROTECTED] wrote:
Do you have shells/bash (bash-3.1.10) installed?
Yes. I have.
I had one problem here, but unfortunately not the time to really look
at
try begining yuor scripts with:
#!/bin/sh
:)
2006/3/3, Nicolas Rachinsky [EMAIL PROTECTED]:
* Elisey O. Savateev [EMAIL PROTECTED] [2006-03-03 16:10 +0500]:
Fri, 3 Mar 2006 11:56:09 +0100
Nicolas Rachinsky [EMAIL PROTECTED] wrote:
Do you have shells/bash (bash-3.1.10) installed?
* Alexey Karagodov [EMAIL PROTECTED] [2006-03-03 14:40 +0300]:
try begining yuor scripts with:
#!/bin/sh
:)
I'm not using the bash for my own scripts. But we're not talking
about mine or the OP's own scripts.
Nicolas
--
http://www.rachinsky.de/nicolas
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Nicolas Rachinsky
Sent: Friday, March 03, 2006 5:20 AM
To: freebsd-stable@FreeBSD.ORG
Subject: Re: configure scripts ignores parameters
* Elisey O. Savateev [EMAIL PROTECTED] [2006-03-03 16:10 +0500
On Fri, Mar 03, 2006 at 09:44:17AM -0600, Bill Milford wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
Nicolas Rachinsky
Sent: Friday, March 03, 2006 5:20 AM
To: freebsd-stable@FreeBSD.ORG
Subject: Re: configure scripts ignores
Milford wrote:
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
ebsd.org] On Behalf Of
Nicolas Rachinsky
Sent: Friday, March 03, 2006 5:20 AM
To: freebsd-stable@FreeBSD.ORG
Subject: Re: configure scripts ignores parameters
=20
* Elisey O. Savateev
On Fri, Mar 03, 2006 at 09:33:55AM -0800, Kevin Oberman wrote:
I hope someone has reported this error to the bash developers.
If te latest bash version fixes the problem, it's a bit too late to
report it.
Well, how about testing the latest version to see if it's fixed? :-)
Bottom line is:
* Kevin Oberman [EMAIL PROTECTED] [2006-03-03 09:33 -0800]:
Date: Fri, 3 Mar 2006 12:22:31 -0500
From: Kris Kennaway [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
I hope someone has reported this error to the bash developers.
I haven't yet. I was in a hurry and haven't been able to install
Date: Fri, 3 Mar 2006 12:39:25 -0500
From: Kris Kennaway [EMAIL PROTECTED]
On Fri, Mar 03, 2006 at 09:33:55AM -0800, Kevin Oberman wrote:
I hope someone has reported this error to the bash developers.
If te latest bash version fixes the problem, it's a bit too late to
report it.
* Kris Kennaway [EMAIL PROTECTED] [2006-03-03 12:39 -0500]:
On Fri, Mar 03, 2006 at 09:33:55AM -0800, Kevin Oberman wrote:
I hope someone has reported this error to the bash developers.
If te latest bash version fixes the problem, it's a bit too late to
report it.
Well, how about
Nicolas Rachinsky wrote:
* Elisey O. Savateev [EMAIL PROTECTED] [2006-03-03 16:10 +0500]:
Fri, 3 Mar 2006 11:56:09 +0100
Nicolas Rachinsky [EMAIL PROTECTED] wrote:
Do you have shells/bash (bash-3.1.10) installed?
Yes. I have.
I had one problem here, but unfortunately not the
* Claude Buisson [EMAIL PROTECTED] [2006-03-03 23:05 +0100]:
Here (bash built WITHOUT_NLS)
Using WITHOUT_NLS does not help here.
Nicolas
--
http://www.rachinsky.de/nicolas
___
freebsd-stable@freebsd.org mailing list
29 matches
Mail list logo
