Pike-devel

pike-devel@lists.lysator.liu.se

4 participants
3044 discussions

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

Besides, even if you did a pike.m4, it would have to invoke pike with --show-paths or similar in order to find the files, since J Random disribution might have moved them to god-knows-where. ;-) So you'd need to launch the pike interpreter anyway.

1 0

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

The main reason is that you can have several pikes installed or semi-installed. The -x module systems lets you start up any pike of your choice with any additional flags you might need, and get the module compiled for that exact environment. And if you have .cmod:s, you do need pike to build the module. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-26 20:25: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 08:15:02PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> I don't think the build system needs to change. That it can't work if >> you put the files at place A but _tell the build system they are at >> place B_ isn't really a bug. There might be a point in allowing finer >If the build system was documented, then I wouldn't have to wait for >somebody to stumble upon the problem. If you confirm what I asked about in >the other posting and repeated below, then I'll fix it in no time. > >> granularity in the path specifications, so that certain files can be >> in one place and others in another, but that's not the problem here. >> Debian keeps all the files needed by the build system in one place, it >> just lies to said build system about what that place is. >If include_prefix is the only change that is _really_ needed, then it's >trivial. OTOH, why does the build system have to be a build system at all? >Why not just provide a simple pike.m4 file to be included in you module's >aclocal.m4? It seems to me to be a bit overdone to have to install and >launch the whole pike interpreter and the library in order to get a few >strings for the compilation process - especially that you don't need pike to >link your modules, all you need is the C headers. > >marek > > > > / Brevbäraren >

1 0

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

If master()->include_prefix points to the directory where the include files, dynamic_module_makefile, aclocal.m4 file, precompile.{pike,sh} files and specs file are, pike -x module should work yes. This is exactly what include_prefix is there for, and the only thing it is used for. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-26 20:20: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 08:10:02PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> It's not inflexible, but you have to inform it that it should flex. >> Like I said, it can't be clairvoyant. include_prefix must be set to >> where the include files are (the Pike build system does this when you >> build Pike normally). >And is this the only thing that needs to be done in order for it to work? > >marek > > > > / Brevbäraren >

1 0

Re: Pike @ Debian
by Per Hedbor () ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

One solution is to discontinue the debian port. / Per Hedbor () Previous text: >2004-01-26 18:40: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 06:25:01PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> pike -x module is _my_ friend, and it works everywhere except in >> Debian. >Well, your friend is inflexible then. If it has to be hacked to work in a >different environment, then something is wrong with it. Where is the build >system documentation? I'll be happy to hack it if I don't have to spend a >day or two learning it. > >thanks, > >marek > > > > / Brevbäraren >

3 3

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

It's not inflexible, but you have to inform it that it should flex. Like I said, it can't be clairvoyant. include_prefix must be set to where the include files are (the Pike build system does this when you build Pike normally). / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-26 18:40: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 06:25:01PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> pike -x module is _my_ friend, and it works everywhere except in >> Debian. >Well, your friend is inflexible then. If it has to be hacked to work in a >different environment, then something is wrong with it. Where is the build >system documentation? I'll be happy to hack it if I don't have to spend a >day or two learning it. > >thanks, > >marek > > > > / Brevbäraren >

1 0

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

${include_prefix} is the C include path. ${share_path}/include is the Pike include path. They are not the same in a normal installation. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-26 18:38: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 06:20:02PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> It is told, by the master. The path is passed through the variable >> master()->include_prefix, which is initialized to the value of >> ¤include_prefix¤ when master.pike is generated from master.pike.in. >> So as you can see, it's fully configurable. >So you say it can encompass a separate pike .h files path and a separate C >.h path? How? > >marek > > > > / Brevbäraren >

1 0

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

pike -x module is _my_ friend, and it works everywhere except in Debian. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-26 18:18: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 06:05:03PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> I don't mind if Debian mucks around with the files, as long as they >> make sure that everything _works_ afterwards. ;-) >Caudium compiles with pike on debian, so it works. pike7.4-config --cflags >is your friend. I cannot and will not try to change the debian standards to >fit the Pike standards file location wise. The thing to be fixed and made >more flexible is the build system which should be able to find the files >anywhere they are given certain tips as to their locations. A simple config >file in a well-known location would do just fine. > >marek > > > > / Brevbäraren >

1 0

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

It is told, by the master. The path is passed through the variable master()->include_prefix, which is initialized to the value of ¤include_prefix¤ when master.pike is generated from master.pike.in. So as you can see, it's fully configurable. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-26 18:12: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 06:00:03PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> Pike looks for the includes where it installs them. If Debian wants >> them installed somewhere else, it's their job to make sure Pike looks >> there instead. Pike can't be clairvoyant about these things. >Fix the build system then. It should be flexible enough to be told where the >includes are. > >marek > > > > / Brevbäraren >

1 0

Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

I'm trying to use the Debian Pike packages together with some Pike software, but it looks like the packages are broken somehow. Although I have pike7.4-dev installed, /usr/lib/pike/7.4.35/include/pike/ only contains the specs file. There are no headers, no makefiles, no aclocal files. Hence modules can not be build. What gives?

2 2

Re: Pike @ Debian
by Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) ＠ Pike (-) developers forum 26 Jan '04

26 Jan '04

>all the includes are in /usr/include/pike/PIKEVER/ That's not where they're supposed to be. The module build system doesn't look there, and so putting them there will not work. / Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) Previous text: >2004-01-26 17:37: >Subject: Re: Pike @ Debian >-------------------------------------------------------------------- >On Mon, Jan 26, 2004 at 03:40:01PM +0100, Marcus Comstedt (ACROSS) (Hail Ilpalazzo!) @ Pike (-) developers forum scribbled: >> I'm trying to use the Debian Pike packages together with some Pike >> software, but it looks like the packages are broken somehow. Although >> I have pike7.4-dev installed, /usr/lib/pike/7.4.35/include/pike/ only >> contains the specs file. There are no headers, no makefiles, no >> aclocal files. Hence modules can not be build. What gives? >all the includes are in /usr/include/pike/PIKEVER/ > >marek > > > > / Brevbäraren >

2 2

Jump to page:

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