Pike-devel May 2004

pike-devel@lists.lysator.liu.se

11 participants
65 discussions

Pike 7.6
by Martin Nilsson (r�fsfiskal) ＠ Pike (-) developers forum 09 May '04

09 May '04

Pike 7.6.6 is in the FTP. Release notes are here http://pike.ida.liu.se/download/notes/7.6.xml We'll begin writing announcements and stuff after dinner...

9 23

Configure breaks under mingw32
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 08 May '04

08 May '04

I've just run into a problem. I am unable to configure 7.6 and 7.7. Configure fails a check or two after displaying the compiler summary. It checks the base directory, updates config.cache and then fails to create ./config.status. This is the error I get: configure: creating ./config.status ./config.status: line 197: syntax error near unexpected token `\"' ./config.status: line 197: ` "\" ) CONFIG_FILES="$CONFIG_FILES \" ;;' make: *** [configure] Error 1 Looking at the config.status, row 197, it seems like there are a few bogus lines in there. I'm a bit clueless to how to debug this and I'm desperate for some help...

2 5

win32 build failures
by Peter Bortas (Kein Paket!) ＠ Pike (-) developers forum 07 May '04

07 May '04

Has anyone looked at why win32 broke down on all available build-systems and all exported Pike-versions about two weeks ago? I know my enviroment has not been deliberately changed at least. What about kali?

2 4

Prepending paths in master.pike.in conversion?
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 07 May '04

07 May '04

Is it possible to prepend a string to all paths that are replaced within master.pike.in during compilation? When building in mingw, I use the path /home/sss668/Pike... which maps to c:/msys/1.0/home/sss668/Pike.. in the real fs..

1 0

Where is the test for the precense of fpclass?
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 07 May '04

07 May '04

In which file and at what line can I find the test that allows configure to define HAVE_FPCLASS in Pike 7.6.6 source-tarball? I'm a bit frustrated by the fact that the define is set in my machine.h but I don't have the needed values so it still doesn't work..

2 2

Pike 7.4.44 now native on Windows
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 07 May '04

07 May '04

I've just gotten a Hilfe prompt from a Pike 7.4.44 source dist on my win2k workstation using MinGW32. Since I lack a direct connection to internet at work, I will transfere all my work to my workstation at home tonight and start working out what patches that needs to be added to Mingw. As soon as that is done, I will start working on getting 7.7 to compile... Looks like we might have the first 8.0 feature done very soon... ;)

2 6

Autoconf behaviour
by Marcus Agehall (Scanian) ＠ Pike (-) developers forum 06 May '04

06 May '04

What happens if I put #undef FOO in my machine.h.in but never test for FOO in my configure script? I suspect configure will *define* FOO in the resulting machine.h, correct?

2 1

Re: change log
by Mirar ＠ Pike developers forum 06 May '04

06 May '04

No, agree. I think that it would be good if everyone kept the changelog up to date. / Mirar Previous text: >2004-05-06 19:39: >Subject: Re: change log >-------------------------------------------------------------------- >Was that voice opposition, or something else? > > > > > / Brevbäraren >

1 0

7.6
by Martin Nilsson (r�fsfiskal) ＠ Pike (-) developers forum 05 May '04

05 May '04

Two bugs left before 7.6. The mast-thread-bug and a serious optimization bug that turns string x(string i) { return i; }; return x("")+1+1; into "2".

5 10

Re: Building pike on windows
by Kaos 05 May '04

05 May '04

(topic from pike@roxen) Martin Nilsson (räfsfiskal) @ Pike (-) importmöte för mailinglistan wrote: >Looks like it tries to execute smartlink.exe instead of the shell script >smartlink (see the bin directory). > >Yes, the developer list is probably better. > > > I saw the smartlink shell script, but I get the exe version in the build dir during configure..? Haven't tried to fool configure by placing the shell script as smartlink.exe in the build dir prior to running configure though, will try that.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pike-devel May 2004