Mailing List Archive

site_perl ... and other configure things:
i'm really unsure that i like having `$prefix/site_perl' as the default.
it's another top-level directory under $prefix -- that i don't want. i
want it under `$prefix/perl' _somewhere_

i'm not even sure what the correct incantation (Configure command) is to
do this. it used to be simple with `sitelib'...but now `sitearch' has
confused things :-(

i ended up with:

Configure -D prefix=/local -D privlib=/local/lib/perl/5.002 -D sitearch=/local/lib/perl/site/sparc-netbsd -D sitelib=/local/lib/perl/site -des

to get this:

Pathname for the site-specific architecture-dependent library files? (~name ok)
[/local/lib/perl/site/sparc-netbsd]
Directory for your old 5.001 architecture-dependent libraries? (~name ok)
[none]
Pathname for the site-specific library files? (~name ok)
[/local/lib/perl/site]

ok, so the sitelib and sitearch dirs seem to be correct, though, i hate that i
had to put $archname (or whatever `sparc-netbsd' is) in there. can $sitearch
depend on $sitelib please? when i first compiled it, i had forgotten to check
this -- my script did `-D sitelib=/local/lib/perl/site' but that wasn't anywhere
in the binary -- i've blown away that now, but, it seemed that seeing sitelib
only didn't do anything for me...infact, it made me think things were correct
but they weren't.

what's the 3rd question i've dumped there for ?

why does configure do this:

mydomain='.eterna.com.au'
myhostname='splode'
myuname='netbsd splode.eterna.com.au 1.1_alpha netbsd 1.1_alpha (_splode_) #273: mon dec 4 09:36:37 est 1995 mrg@splode.eterna.com.au:orbqbuildsrcsysarchsparccompile_splode_ sparc '

ie, why does it split the hostname/domain name? my machine hostname *IS*
splode.eterna.com.au -- that's what hostname(1) and uname(1) return. i don't
think that Configure should be dictating policy on *that* issue :-)


also, has anyone thought about making Configure aware of the 4.4BSD stdio
stuff ? it currently doesn't know what to do with it... if anyone wants to
tell me which parts of stdio perl wants to peak at, i'll prolly be able to
work out what to do.. :-)

hmm... enough babbling from me for now :-)

.mrg.
Re: site_perl ... and other configure things: [ In reply to ]
On Tue, 5 Dec 1995, matthew green wrote:

> i'm really unsure that i like having `$prefix/site_perl' as the default.
> it's another top-level directory under $prefix -- that i don't want. i
> want it under `$prefix/perl' _somewhere_

I'm not committed strongly to this. I thought this is what emacs
did and that it might be clearer this way. I'm easily swayed on this,
so speak up quickly, folks, if you want a change.

> i'm not even sure what the correct incantation (Configure command) is to
> do this. it used to be simple with `sitelib'...but now `sitearch' has
> confused things :-(

> ok, so the sitelib and sitearch dirs seem to be correct, though, i hate that i
> had to put $archname (or whatever `sparc-netbsd' is) in there. can $sitearch
> depend on $sitelib please? when i first compiled it, i had forgotten to check

Yes, I'm planning to do this. Certainly the order of the questions is
backwards.

> why does configure do this:
>
> mydomain='.eterna.com.au'
> myhostname='splode'
> myuname='netbsd splode.eterna.com.au 1.1_alpha netbsd 1.1_alpha (_splode_) #273: mon dec 4 09:36:37 est 1995 mrg@splode.eterna.com.au:orbqbuildsrcsysarchsparccompile_splode_ sparc '
>
> ie, why does it split the hostname/domain name? my machine hostname *IS*
> splode.eterna.com.au -- that's what hostname(1) and uname(1) return. i don't
> think that Configure should be dictating policy on *that* issue :-)

Reliably finding out the hostname and domainname is a very hard problem.
Patches are welcome. However, it's also not a very interesting problem since
we don't use it for anything currently :-). It's just a placeholder until
someone puts together a full perlbug+supporting_utilities patch, and even
then, it's just a default CC: for perlbug.

> also, has anyone thought about making Configure aware of the 4.4BSD stdio
> stuff ? it currently doesn't know what to do with it... if anyone wants to
> tell me which parts of stdio perl wants to peak at, i'll prolly be able to
> work out what to do.. :-)

It's trying to use the _ptr, _cnt, and _base fields of the stdio FILE
structure. Check out USE_STDIO_PTR and USE_STDIO_BASE in config_h.SH,
and the corresponding code in Configure. It's supposed to be modular
and easy to extend. Right.

Andy Dougherty doughera@lafcol.lafayette.edu
Re: site_perl ... and other configure things: [ In reply to ]
On Tue, 5 Dec 1995, Andy Dougherty wrote:
>On Tue, 5 Dec 1995, matthew green wrote:
>
>> i'm really unsure that i like having `$prefix/site_perl' as the default.
>> it's another top-level directory under $prefix -- that i don't want. i
>> want it under `$prefix/perl' _somewhere_

I agree (unless $prefix contains the string "perl"). I don't like to
clutter up /local/lib/ more than necessary.

> I'm not committed strongly to this. I thought this is what emacs
> did and that it might be clearer this way.

Emacs puts everything in a common "emacs/" directory:
/local/lib/emacs/<site-lisp/, VERSION/<etc, lisp, ARCH>>.


Hallvard
Re: site_perl ... and other configure things: [ In reply to ]
It seems that Hallvard B Furuseth said:
> Emacs puts everything in a common "emacs/" directory:
> /local/lib/emacs/<site-lisp/, VERSION/<etc, lisp, ARCH>>.

Alas not any more. There are now :

$prefix/libexec/emacs/VERSION/ARCH for binaries
$prefix/share/emacs/VERSION/{etc,lisp} for the rest

It changed in 19.29.
--
Ollivier ROBERT -=-=- Herve Schauer Consultants -=-=- roberto@hsc.fr.net
-=-=-=-=-=- Support The Free UNIX Systems ! FreeBSD Linux NetBSD -=-=-=-=-=-