Re: [Chicken-users] repository pathname, location and customisation, lib64

2019-03-24 Thread Marco Maggi
ko...@upyum.com wrote:

> Marco Maggi  wrote:
>>   Under  Slackware 32-bit  the  libraries'  directory is  "$prefix/lib",
>> while   underSlackware   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
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] How to I add (not override) compiler options/flags ?

2019-03-24 Thread Jeronimo Pellegrini
On Sun, Mar 24, 2019 at 11:18:48AM +0100, ko...@upyum.com wrote:
> Jeronimo Pellegrini  wrote:
> > But since C_COMPILER_OPTIONS is defined with ?=, if I set it
> > when running make, the default in Makefile.linux, for example,
> > would be ignored.
> > 
> > So if I use a script that wants to *add* flags, how should I do that?
> > (I see that CFLAGS is not used).
> 
> Hmm, this indeed doesn’t appear to be possible.
> 
> Maybe you could use C_COMPILER_OPTIMIZATION_OPTIONS ?

This seems to work! I can set C_COMPILER_OPTIMIZATION_OPTIONS
to CFLAGS before calling make, and compilation goes as
intended.

Thank you!
J.

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] How to I add (not override) compiler options/flags ?

2019-03-24 Thread kooda
Jeronimo Pellegrini  wrote:
> But since C_COMPILER_OPTIONS is defined with ?=, if I set it
> when running make, the default in Makefile.linux, for example,
> would be ignored.
> 
> So if I use a script that wants to *add* flags, how should I do that?
> (I see that CFLAGS is not used).

Hmm, this indeed doesn’t appear to be possible.

Maybe you could use C_COMPILER_OPTIMIZATION_OPTIONS ?

___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] repository pathname, location and customisation, lib64

2019-03-24 Thread kooda
Marco Maggi  wrote:
>   Under  Slackware 32-bit  the  libraries'  directory is  "$prefix/lib",
> while   underSlackware   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
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users


Re: [Chicken-users] installing breadline Was: is the readline egg dead?

2019-03-24 Thread Vasilij Schneidermann
Hello Erik,

> FWIW, breadline builds and loads flawlessly on the in-development
> version of Slackware.

That's interesting.  Could you please post the output of ldd run against
its .so file?  I did this on both Slackware 14.1 and Arch Linux, on
Slackware it wasn't linked against ncurses, on Arch Linux it was.  I got
the hint about linking to ncurses from this forum discussion [1].  Since
ncurses is a readline dependency in any case, I figured it wouldn't hurt
to always link to it.  But who knows, maybe I'll run into a user on
another distro which does things differently and expects them to link
against terminfo or so :)

Vasilij

[1] 
https://forum.segger.com/index.php/Thread/925-libreadline-so-5-undefined-symbol-PC/


signature.asc
Description: PGP signature
___
Chicken-users mailing list
Chicken-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/chicken-users