Then it would be worth to fail the configuration script if Nettle dependency is failed and add a doc on how to get Nettle support.

Well, since you are on the development list you should know about or plans to include Nettle in the dists.

About the autodoc, why building the autodoc by default ? Most users are not interested in building the autodoc anyway.

Bill thought it a good idea (exactly why you'll have to search the archives for). I don't think that we have to do this by default however.

/ Martin Nilsson (saturator)

Previous text:

2004-02-19 11:51: Subject: Re: Pike 7.5 - CVS installation problem

---

Then it would be worth to fail the configuration script if Nettle dependency is failed and add a doc on how to get Nettle support.

About the autodoc, why building the autodoc by default ? Most users are not interested in building the autodoc anyway.

Martin Nilsson (saturator) @ Pike (-) developers forum wrote:

...

The second backtrace is because your Pike lacks Nettle support.

/ Martin Nilsson (saturator)

Previous text:

...

2004-02-19 11:28: Subject: Pike 7.5 - CVS installation problem

---

Hello,

When trying to install Pike 7.5 - CVS on FreeBSD 4.3, I got this error:

%make install /home/david/Pike/7.5/src/pike -DNOT_INSTALLED -DPRECOMPILED_SEARCH_MORE -m/home/david/Pike/7.5/src/master.pike -x extract_autodoc -q --srcdir=/home/david/Pike/7.5/src --imgsrc=/home/david/Pike/7.5/refdoc/src_images --builddir=doc_build/src --imgdir=doc_build/images Bad argument 1. Unknown program: foreach(0) /home/david/Pike/7.5/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike:105:

Tools.Standalone.extract_autodoc()->recurse("/home/david/Pike/7.5/src/doc_

build/src/doc_build/src/doc_build"+[963],"/home/david/Pike/7.5/src/doc_bui

ld/src/doc_build/src/doc_build"+[977],0,({"predef::","doc_build","src","do c_build","src","doc_build","src",,,135}))

/home/david/Pike/7.5/lib/modules/Tools.pmod/Standalone.pmod/extract_autodoc.pike:119:

Tools.Standalone.extract_autodoc()->recurse("/home/david/Pike/7.5/src/doc_

build/src/doc_build/src/doc_build"+[954],"/home/david/Pike/7.5/src/doc_bui

ld/src/doc_build/src/doc_build"+[968],0,({"predef::","doc_build","src","do c_build","src","doc_build","src",,,134}))

...

After I tried to build Pike without the autodoc and I get compilation errors when using the Crypto module:

...

indices(Crypto);

/usr/local/pike/7.5.17/lib/modules/Crypto.pmod/cast.pike:4: Warning: Crypto.cast is deprecated. Use Crypto.CAST instead. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/module.pmod:12:Index 'crypt_md5' not present in module 'Crypto'. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/module.pmod:16:Index 'crypt_md5' not present in module 'Crypto'. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/aes.pike:4: Warning: Crypto.aes is deprecated. Use Crypto.AES instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/idea.pike:4: Warning: Crypto.idea is deprecated. Use Crypto.IDEA instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/sha.pike:4: Warning: Crypto.sha is deprecated. Use Crypto.SHA1 instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/hmac.pike:4: Warning: Crypto.hmac is deprecated. Use Crypto.HMAC instead. /usr/local/pike/7.5.17/lib/modules/Standards.pmod/PKCS.pmod/Signature.pmod:12:Index 'Hash' not present in module 'Crypto'. /usr/local/pike/7.5.17/lib/modules/Standards.pmod/PKCS.pmod/Signature.pmod:12:Illegal program identifier (type: int). /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/HMAC.pike:39:Error looking up 'Signature' in module 'PKCS'. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/HMAC.pike:77:Class definition failed. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/hmac.pike:6:Error looking up 'HMAC' in module 'Crypto'. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/hmac.pike:6:Illegal program pointer. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/hmac.pike:17:Class definition failed. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/hmac.pike:6:Error looking up 'hmac' in module 'Crypto'. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/hmac.pike:6:Illegal program pointer. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod.0:-: Warning: Compilation failed: Compilation failed. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/rsa.pike:4: Warning: Crypto.rsa is deprecated. Use Crypto.RSA instead. /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:221:Failed to index module 'Signature' with 'build_digestinfo' (module doesn't exist?) /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:291:Expected constant, got something else (438) /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:339:Expected constant, got something else (438) /usr/local/pike/7.5.17/lib/modules/Crypto.pmod/RSA.pike:349:Expected constant, got something else (438) /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/rsa.pike:6:Error looking up 'RSA' in module 'Crypto'. /usr/local/pike/7.5.17/lib/7.4/modules/Crypto.pmod/rsa.pike:6:Illegal program pointer. ...

/ David

/ Brevbäraren

/ Brevbäraren

On the contrary, I'd have to disagree. I use the modref _all_ the time and having a local copy saves me hours of waiting for potentially slow network connections. That it's available by default 1) encourages people to actually look at the documentation and see all of the wonderful features available and 2) makes pike that much less mysterious.

The reason that the autodocs are now built is because at the very least, we need to have autodoc.xml available for external modules to insert their documentation into.

I agree that building the refdocs takes a lot of time, and that as an impatient person, it takes forever. On an ultra 10 it takes a good 15 minutes, about 1 on a new SF280, but that's beside the point. Perhaps it would good to have a checkpoint so that we don't have to do the join and layout each time even if the documentation hasn't changed.

This, coupled with a pre-extraction for the distribution sources might be a good compromise. Alternately, an optional install-without-docs target might suit as well.

Any thoughts?

Bill

...

About the autodoc, why building the autodoc by default ? Most users are not interested in building the autodoc anyway.

Bill thought it a good idea (exactly why you'll have to search the archives for). I don't think that we have to do this by default however.

On the contrary, I'd have to disagree. I use the modref _all_ the time and having a local copy saves me hours of waiting for potentially slow network connections. That it's available by default 1) encourages people to actually look at the documentation and see all of the wonderful features available and 2) makes pike that much less mysterious.

Agreed.

The reason that the autodocs are now built is because at the very least, we need to have autodoc.xml available for external modules to insert their documentation into.

Also agreed.

I agree that building the refdocs takes a lot of time, and that as an impatient person, it takes forever. On an ultra 10 it takes a good 15 minutes, about 1 on a new SF280, but that's beside the point. Perhaps it would good to have a checkpoint so that we don't have to do the join and layout each time even if the documentation hasn't changed.

The joining used to be done one directory level at a time to avoid redoing too much. I'm not sure how it's done now that it doesn't use recursive Makefiles.

This, coupled with a pre-extraction for the distribution sources might be a good compromise. Alternately, an optional install-without-docs target might suit as well.

True, but note that autodoc.xml for Pike 7.5 currently is ~4.5MB, and only shrinks to ~600KB with gzip -9, so a gzipped Pike 7.5 source dist would increase in size to ~8MB.

An install-without-docs target would probably be good to have in any case.

/ Henrik Grubbström (Lysator)

Previous text:

2004-02-25 20:56: Subject: Re: Pike 7.5 - CVS installation problem

---

On the contrary, I'd have to disagree. I use the modref _all_ the time and having a local copy saves me hours of waiting for potentially slow network connections. That it's available by default 1) encourages people to actually look at the documentation and see all of the wonderful features available and 2) makes pike that much less mysterious.

The reason that the autodocs are now built is because at the very least, we need to have autodoc.xml available for external modules to insert their documentation into.

I agree that building the refdocs takes a lot of time, and that as an impatient person, it takes forever. On an ultra 10 it takes a good 15 minutes, about 1 on a new SF280, but that's beside the point. Perhaps it would good to have a checkpoint so that we don't have to do the join and layout each time even if the documentation hasn't changed.

This, coupled with a pre-extraction for the distribution sources might be a good compromise. Alternately, an optional install-without-docs target might suit as well.

Any thoughts?

Bill

...

...

About the autodoc, why building the autodoc by default ? Most users are not interested in building the autodoc anyway.

Bill thought it a good idea (exactly why you'll have to search the archives for). I don't think that we have to do this by default however.

/ Brevbäraren

Hello,

...

a good compromise. Alternately, an optional install-without-docs target might suit as well.

I vote for a --with-docs and without docs by default.

In my opinion, the default must be to build _without_ docs. Those who like to read the docs will read the README or INSTALL first, where necessary instructions and explanations may be placed.

Yes. Most poeple will use the websites. An alternative would be to give precompiled docs with "exported" or release versions and not build the doc by default. This will save time, avoid possible errors building docs and will assure that the doc is available to the first users of Pike without internet access but who can have a pike source anyway (first users will never use other versions since they will need a Pike binary for that). Also another way to make users read the doc would be to put a message at the end of the install telling "There is a very good doc in ../somewhere which you can read with your favorite HTML browser"

BTW, is this (autodoc generation) process fixed in 7.5? Few times I tried to build it and install (real install - i.e. not for verify target), and it hung somewhere in the middle, in endless loop generating recursive dirs (thus effectively blocking the build process)... :)

Yes this problem is fixed.

/ David