repository pathname, location and customisation, lib64

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

repository pathname, location and customisation, lib64

Marco Maggi
Ciao,

  I would  really like to customise  the location of the  installed eggs
for  my  Slackware64 on  a  x86_64-pc-linux-gnu  running Chicken  5.0.0.
First I go to the Wiki[1] and try this:

$ csi -p "(repository-path)"

Error: unbound variable: repository-path

        Call history:

        <syntax>  (##core#begin (##core#require library scheme#) (##core#require library chicken.base#) (##core#requir...
        <syntax>  (##core#require library scheme#)
        <syntax>  (##sys#load-library (##core#quote library))
        <syntax>  (##core#quote library)
        <syntax>  (##core#require library chicken.base#)
        <syntax>  (##sys#load-library (##core#quote library))
        <syntax>  (##core#quote library)
        <syntax>  (##core#begin (##core#require expand chicken.syntax#))
        <syntax>  (##core#require expand chicken.syntax#)
        <syntax>  (##sys#load-library (##core#quote expand))
        <syntax>  (##core#quote expand)
        <eval>  (##sys#load-library (##core#quote library))
        <eval>  (##sys#load-library (##core#quote library))
        <eval>  (##sys#load-library (##core#quote expand))
        <syntax>  (repository-path)
        <eval>  (repository-path) <--

but   I  read,   and  see   on  my   system,  that   the  directory   is
"${prefix}/lib/chicken/9".

  Under  Slackware 32-bit  the  libraries'  directory is  "$prefix/lib",
while   under    Slackware   64-bit   the   libraries'    directory   is
"$prefix/lib64".  On a  64-bit platform: it is possible  to install both
32-bit  and   64-bit  packages  and   their  files  go   into  different
installation  directories.  It  is  not right  to  put everything  under
"lib", I would like to use "lib64".

  Searching the Wiki, the bugs database and the mailing list archive: it
seems that this  is not currently supported?  But in  some old messages,
someone *is* using "lib64"...

TIA

[1] <http://wiki.call-cc.org/chicken-projects/egg-index-5.html>
--
Marco Maggi

_______________________________________________
Chicken-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/chicken-users
Reply | Threaded
Open this post in threaded view
|

Re: repository pathname, location and customisation, lib64

Kooda
Marco Maggi <[hidden email]> wrote:
>   Under  Slackware 32-bit  the  libraries'  directory is  "$prefix/lib",
> while   under    Slackware   64-bit   the   libraries'    directory   is
> "$prefix/lib64".  On a  64-bit platform: it is possible  to install both
> 32-bit  and   64-bit  packages  and   their  files  go   into  different
> installation  directories.  It  is  not right  to  put everything  under
> "lib", I would like to use "lib64".

You can change the library directory by passing a LIBDIR variable to make,
like so: `make PLATFORM=linux PREFIX=/usr LIBDIR=/usr/lib64`

Be sure to run `make PLATFORM=linux confclean` before that so the config
file is reset.

In case you need to change other specific directories, you can look for
the list of variables at the beginning of defaults.make.

I hope this helps!

_______________________________________________
Chicken-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/chicken-users
Reply | Threaded
Open this post in threaded view
|

Re: repository pathname, location and customisation, lib64

Marco Maggi
[hidden email] wrote:

> Marco Maggi <[hidden email]> wrote:
>>   Under  Slackware 32-bit  the  libraries'  directory is  "$prefix/lib",
>> while   under    Slackware   64-bit   the   libraries'    directory   is
>> "$prefix/lib64".  On a  64-bit platform: it is possible  to install both
>> 32-bit  and   64-bit  packages  and   their  files  go   into  different
>> installation  directories.  It  is  not right  to  put everything  under
>> "lib", I would like to use "lib64".

> You can change the library directory by passing a LIBDIR variable to make,
> like so: `make PLATFORM=linux PREFIX=/usr LIBDIR=/usr/lib64`

This has worked while installing Chicken itself, with the commands:

   $ make PLATFORM=linux \
       PREFIX=/opt/chicken/5.0.0 LIBDIR=/opt/chicken/5.0.0/lib64
   $ (umask 0 ; sudo make install \
       PLATFORM=linux PREFIX=/opt/chicken/5.0.0 LIBDIR=/opt/chicken/5.0.0/lib64)

and now  "chicken-install" puts the eggs  in "/opt/chicken/5.0.0/lib64".
I see that the documentation on the Wiki for accessing "repository-path"
has been fixed.  Thanks!

  Am I  correct in saying that  the README in Chicken's  distribution is
missing  a  note saying  that  we  should  *not* "strip"  the  installed
binaries?  If I strip them I get errors later when installing eggs.

--
Marco Maggi

_______________________________________________
Chicken-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/chicken-users
Reply | Threaded
Open this post in threaded view
|

Re: repository pathname, location and customisation, lib64

Evan Hanson-4
Hi Marco,

On 2019-03-25  6:08, Marco Maggi wrote:
> Am I  correct in saying that  the README in Chicken's  distribution is
> missing  a  note saying  that  we  should  *not* "strip"  the  installed
> binaries?  If I strip them I get errors later when installing eggs.

What are the errors?

I don't think it matters one way or the other, but would be interested
to know if it does.

Evan

_______________________________________________
Chicken-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/chicken-users
Reply | Threaded
Open this post in threaded view
|

Re: repository pathname, location and customisation, lib64

Marco Maggi
Evan Hanson wrote:

> Hi Marco,

> On 2019-03-25  6:08, Marco Maggi wrote:
>> Am I  correct in saying that  the README in Chicken's  distribution is
>> missing  a  note saying  that  we  should  *not* "strip"  the  installed
>> binaries?  If I strip them I get errors later when installing eggs.

> What are the errors?

> I don't think it matters one way or the other, but would be interested
> to know if it does.

I do not get any error now.  If I recall correctly it was a segmentation
fault.   I  cannot   be  sure,  but  most  likely:   while  trying  some
installations to correctly select the  libdir and the repository path, I
forgot to rebuild and reinstall an egg.

Thanks anyway.
--
Marco Maggi

_______________________________________________
Chicken-users mailing list
[hidden email]
https://lists.nongnu.org/mailman/listinfo/chicken-users