Pike-devel

pike-devel@lists.lysator.liu.se

3044 discussions

Re: pike 7.4 port and FreeBSD
by Xavier Beaudouin 12 May '04

12 May '04

> that's fine for me. I wasn't able to run Roxen on top of Pike 7.4 with > a working freetype2 support. Pike 7.6.66 was compiling easily and I'm > looking forward to have a port in /usr/ports/ soon. pike 7.6.6 is in /usr/ports/lang/pike76 :-) So just do a little cvsup for your port-supfile and you'll get it :) Enjoy and make me some feedback if you have some ! /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

1 0

pike 7.4 port and FreeBSD
by Xavier Beaudouin 12 May '04

12 May '04

Hello there, Since pike 7.6 is out (and mostly usable.... !), I have asked freebsd portmanagers to remove pike 7.4 from freebsd ports. You may think it is strange, but there is nothing that runs on 7.4 from the Caudium Group and maintaining 7.4 on FreeBSD is a fscking pain in the ass... :( Note that this doesn't notice that pike 7.4 is not usuable on freebsd, but make it up to date and compliant with freebsd port manager rules is really too difficult. Main problem is pthread compliance library selection that cannot be handled with 7.4, until pike 7.6/7.7 autoconf "--with-threads-lib" parameter be backported... /Xavier -- Xavier Beaudouin - Unix System Administrator & Projects Leader. President of Kazar Organization : http://www.kazar.net/ Please visit http://caudium.net/, home of Caudium & Camas projects

1 0

License question for contributed source
by Johan Sundstr�m (Achtung Liebe!) ＠ Pike (-) developers forum 10 May '04

10 May '04

Incorrect; the proposed version also treats leading spaces differently for numbers, similar to how leading zeroes already work in dwim_sort. For example, "pic4" < "pic 4" < "pic04". Otherwise they seem to do the same thing already.

2 2

Docs branching/tagging?
by Alexander Demenshin 09 May '04

09 May '04

Hi everybody, What about branching (or tagging) at least online docs (available on Pike's site), so that every particular change/feature/desription will not float in air? I mean, currently there is no way to distinguish which feature is implemented in which version, and if there will be some indicators (like "Added in 7.7) it would be a bit better... Or, perhaps, just splitting online docs into two (7.6/7.7) would do the trick? PS: Should I expect that everyone will suggest me to install local copy of docs instead? :) Regards, /Al

5 5

change log
by Bill Welliver 09 May '04

09 May '04

OK, now that 7.7 is open for business, how about a "rule" that developers that add or change functionality worth noting should add a description of the change to the change log file? For the record, this is _not_ the same as a cvs change log entry in that not every checkin will be reflected in the change log document. The caudium project has a rolling change log that might be worth looking at for inspiration. Does anyone have any opposition to the idea? Bill

3 2

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

Jump to page:

2026

2025

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