New Release Candidate at http://pike.ida.liu.se/pub/pike/beta/7.6.48/Pike-v7.6.48.tar.gz
Martin Nilsson (Opera) @ Pike (-) developers forum wrote:
New Release Candidate at http://pike.ida.liu.se/pub/pike/beta/7.6.48/Pike-v7.6.48.tar.gz
Still have problem with blooody bison and lexer....
http://kiwi.oav.net/7.6.48.txt
(Note that I have tested on serveral computers using FreeBSD 5.4, or 6.0RC1. Every machines cannot use the port system to build pike. If I cannot find a way to work around this nasty bug the new pike version cannot be updated on freebsd port tree which is bad for our community, so please help me to workaround this because I gonna be mad....)
/Xavier
But if you are running from source dist bison shouldn't be ran at all.
If noone has a fix for this in a day I'll release 7.6.48 as next stable. FreeBSD hasn't been supported so far (since no active Pike developer has had an interest in FreeBSD and no FreeBSD user has had an interest in Pike development), so this isn't a regression.
Martin Nilsson (Opera) @ Pike (-) developers forum wrote:
But if you are running from source dist bison shouldn't be ran at all.
Should not ... Yes this is the right term "should not"...
Can you help me to FORCE it to NEVER be run ? Even if I have patch this to never this run.
If noone has a fix for this in a day I'll release 7.6.48 as next stable. FreeBSD hasn't been supported so far (since no active Pike developer has had an interest in FreeBSD and no FreeBSD user has had an interest in Pike development), so this isn't a regression.
This is a regression. 7.6.24 work like a charm (I have tried today to recompile it to see if there is not a problem on my systems.... just in case...)... but 7.6.48 doesn't handle that.
This is a regression... Since pike was not too mutch supported on FreeBSD I didn't expect to mutch work on it.... Just compile and try to work a bit with it...
But if the FreeBSD port cannot be updated we can say that Pike is purely dead for the community because I have several user of Pike under FreeBSD for big sites that are asking me to update 7.6 port to run Caudium (in general) or other hand made scripts....
It is for my point of vue very sad that pike runs only on Linux, and Solaris, but not on freebsd.
Now I don't want to start a flame war, we had enougth of that. I am just asking help for me and the community to fix that and have a working pike on native Freebsd.
That's all, if there is no help, then just add "FreeBSD ports is now not supported".
I will not cry you are sure.
/Xavier
Can you help me to FORCE it to NEVER be run ? Even if I have patch this to never this run.
No. I have no expertise in neither FreeBSD nor bison (nor the configure/make process of Pike for that matter).
It is POSSIBLE to build Pike on your system, so Pike itself is ok. The problem is in your build process. This process can be fixed later and you can build a 7.6.48 Pike that behaves like any other 7.6.48 Pike. This is what we typically do with other difficult platform builds like the Windows port.
Hello,
Martin Nilsson (Opera) @ Pike (-) developers forum wrote:
Can you help me to FORCE it to NEVER be run ? Even if I have patch this to never this run.
No. I have no expertise in neither FreeBSD nor bison (nor the configure/make process of Pike for that matter).
It is POSSIBLE to build Pike on your system, so Pike itself is ok. The problem is in your build process. This process can be fixed later and you can build a 7.6.48 Pike that behaves like any other 7.6.48 Pike. This is what we typically do with other difficult platform builds like the Windows port.
Yes this is good it can be possible to build a Pike using sources.
The only problem as port manager is finding why 7.6.48 doesn't like ports enviroment from freebsd and not 7.6.24 ?
This is puzzling me :)
/Xavier
On Tue, Nov 01, 2005 at 10:27:14AM +0100, Xavier Beaudouin wrote:
Forbidden
You don't have permission to access /7.6.48.txt on this server. Apache/2.0.55 (FreeBSD) PHP/4.4.0 Server at kiwi.oav.net Port 80
greetings, martin.
Ooops... fixed... thanks martin :)
Martin � wrote:
On Tue, Nov 01, 2005 at 10:27:14AM +0100, Xavier Beaudouin wrote:
Forbidden
You don't have permission to access /7.6.48.txt on this server. Apache/2.0.55 (FreeBSD) PHP/4.4.0 Server at kiwi.oav.net Port 80
greetings, martin.
Still have problem with blooody bison and lexer....
http://kiwi.oav.net/7.6.48.txt
(Note that I have tested on serveral computers using FreeBSD 5.4, or 6.0RC1. Every machines cannot use the port system to build pike. If I
Can you build it if you don't use the port system?
cannot find a way to work around this nasty bug the new pike version cannot be updated on freebsd port tree which is bad for our community, so please help me to workaround this because I gonna be mad....)
From looking at your trace it looks like something has touched
y.tab.c:
| ===> Building for pike76-7.6.48 | mv /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/y.tab.h /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.h_src | cp /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.h_src /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.h [...] | gmake[1]: Entering directory `/usr/ports/lang/pike76.new/work/Pike-v7.6.48/src' | sed -e 's/YY_COUNT_TYPE/unsigned int/' \ | -e 's/YY_FROM_CONST//' \ | -e 's/short[ ]*int[ ]//* short */ int /g' \ | -e 's/(short[ ]*int)/(/* short */ int)/g' \ | < /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/y.tab.c > /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.c
What are the patches that are applied at the start?
| ===> Patching for pike76-7.6.48 | ===> pike76-7.6.48 depends on file: /usr/local/bin/perl5.8.7 - found | ===> Applying FreeBSD patches for pike76-7.6.48
Where have you hidden the bison?
| ===> pike76-7.6.48 depends on executable: bison - found [...] | checking for yacc clone that handles %pure_parser... Get bison if you want to do "make export"
/Xavier
Henrik Grubbström (Lysator) @ Pike (-) developers forum wrote:
Still have problem with blooody bison and lexer....
http://kiwi.oav.net/7.6.48.txt
(Note that I have tested on serveral computers using FreeBSD 5.4, or 6.0RC1. Every machines cannot use the port system to build pike. If I
Can you build it if you don't use the port system?
Yes.
cannot find a way to work around this nasty bug the new pike version cannot be updated on freebsd port tree which is bad for our community, so please help me to workaround this because I gonna be mad....)
From looking at your trace it looks like something has touched
y.tab.c:
| ===> Building for pike76-7.6.48 | mv /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/y.tab.h /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.h_src | cp /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.h_src /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.h [...] | gmake[1]: Entering directory `/usr/ports/lang/pike76.new/work/Pike-v7.6.48/src' | sed -e 's/YY_COUNT_TYPE/unsigned int/' \ | -e 's/YY_FROM_CONST//' \ | -e 's/short[ ]*int[ ]//* short */ int /g' \ | -e 's/(short[ ]*int)/(/* short */ int)/g' \ | < /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/y.tab.c > /usr/ports/lang/pike76.new/work/Pike-v7.6.48/src/language.c
What are the patches that are applied at the start?
The only patch applied is :
--- ../bin/install.pike.orig Sat Feb 21 03:14:53 2004 +++ ../bin/install.pike Sat Feb 21 03:12:41 2004 @@ -1380,7 +1380,7 @@
if(file_stat(vars->MANDIR_SRC)) { - install_dir(vars->MANDIR_SRC,combine_path(man_prefix,"man1"),0); + //install_dir(vars->MANDIR_SRC,combine_path(man_prefix,"man1"),0); } };
And ports make the following :
post-patch: @${REINPLACE_CMD} -e 's| -lgmp| -L${LOCALBASE}/lib -lgmp|' \ ${WRKSRC}/modules/Gmp/configure ${WRKSRC}/modules/_Image_XFace/configure @${REINPLACE_CMD} -e 's|%%PTHREAD_CFLAGS%%|${PTHREAD_CFLAGS}|' \ ${WRKSRC}/configure @${REINPLACE_CMD} -e 's|%%PTHREAD_LIBS%%|${PTHREAD_LIBS}|' \ ${WRKSRC}/configure
| ===> Patching for pike76-7.6.48 | ===> pike76-7.6.48 depends on file: /usr/local/bin/perl5.8.7 - found | ===> Applying FreeBSD patches for pike76-7.6.48
Where have you hidden the bison?
| ===> pike76-7.6.48 depends on executable: bison - found [...] | checking for yacc clone that handles %pure_parser... Get bison if you want to do "make export"
Bison is never found when pike is compiled on freebsd... whatever I compile using port or using normal tarball.
I can give access to this box if needed.
/Xavier
On Tue, 01 Nov 2005 10:27:14 +0100 Xavier Beaudouin kiwi@oav.net wrote:
Still have problem with blooody bison and lexer....
http://kiwi.oav.net/7.6.48.txt
(Note that I have tested on serveral computers using FreeBSD 5.4, or 6.0RC1. Every machines cannot use the port system to build pike. If I cannot find a way to work around this nasty bug the new pike version cannot be updated on freebsd port tree which is bad for our community, so please help me to workaround this because I gonna be mad....)
/Xavier
For what its worth, I have no build problems with the new version using the openbsd ports framework. I just changed the version number and removed the INSTALL_TARGET=install_nodoc line and it worked fine. I haven't tested the FLAVORS yet, but it seems ok so far.
Adam
Hi,
Still have problem with blooody bison and lexer....
http://kiwi.oav.net/7.6.48.txt
(Note that I have tested on serveral computers using FreeBSD 5.4, or 6.0RC1. Every machines cannot use the port system to build pike. If I cannot find a way to work around this nasty bug the new pike version cannot be updated on freebsd port tree which is bad for our community, so please help me to workaround this because I gonna be mad....)
/Xavier
For what its worth, I have no build problems with the new version using the openbsd ports framework. I just changed the version number and removed the INSTALL_TARGET=install_nodoc line and it worked fine. I haven't tested the FLAVORS yet, but it seems ok so far.
This changes nothing for me on freebsd... :/
/xavier
On Tue, 01 Nov 2005 22:08:24 +0100 Xavier Beaudouin kiwi@oav.net wrote:
For what its worth, I have no build problems with the new version using the openbsd ports framework. I just changed the version number and removed the INSTALL_TARGET=install_nodoc line and it worked fine. I haven't tested the FLAVORS yet, but it seems ok so far.
This changes nothing for me on freebsd... :/
Yeah, I didn't realize that freebsd's ports tree still doesn't use seperate build directories instead of compiling everything right in the source directory.
Adam
On Tue, 01 Nov 2005 22:08:24 +0100 Xavier Beaudouin kiwi@oav.net wrote:
For what its worth, I have no build problems with the new version using the openbsd ports framework. I just changed the version number and removed the INSTALL_TARGET=install_nodoc line and it worked fine. I haven't tested the FLAVORS yet, but it seems ok so far.
This changes nothing for me on freebsd... :/
Yeah, I didn't realize that freebsd's ports tree still doesn't use seperate build directories instead of compiling everything right in the source directory.
Same for me. I didn't realize that building pike inside src/ directory gave so mutch problems.
This is now fixed and PR has been sent... so this is ok for me....
/Xavier
Yeah, I didn't realize that freebsd's ports tree still doesn't use seperate build directories instead of compiling everything right in the source directory.
Same for me. I didn't realize that building pike inside src/ directory gave so mutch problems.
Well, it's supposed to work, but nobody does it, so it hasn't been tested.
Anyway, the bug has been fixed.
This is now fixed and PR has been sent... so this is ok for me....
/Xavier
pike-devel@lists.lysator.liu.se
-
Adam Montague -
Henrik Grubbstr�m (Lysator) ＠ Pike (-) developers forum -
Martin B�hr -
Martin Nilsson (Opera) ＠ Pike (-) developers forum
-
Xavier Beaudouin