Re: Fedora 19 comes with guile 2.0.9 - cannot use 2.17.22

[Jacques Menu]

Hello Frédéric,

If you install different versions of some software under different access 
paths/file names, you can use "module-init-tools" 
(https://modules.wiki.kernel.org/index.php/Main_Page) to switch from one 
version to another seamlessly.

This works behind the curtain by modifying environment variables such as PATH 
and MANPATH, and is available for both with bash and tcsh.

Can supply concrete examples if needed.

JM

Le 12 juil. 2013 à 01:47:52, David Kastrup <address@hidden> a écrit :

> Frédéric Bron <address@hidden> writes:
> 
>> I have just moved to fedora 19 and tried to build lilypond to
>> contribute to some bug fix to #3369.
>> However, when I run a simple example like { c }, below is what I get.
>> I guess this is because Fedora 19 comes with guile2, doesn't it?
> 
> So does Ubuntu.  That's not a problem.
> 
>> And I guess, there is nothing I can do against it?
> 
> On Ubuntu, you do
> 
> sudo apt-get install guile-1.8-dev
> 
> before compiling anything and are set.
> 
>> What is strange is that the same { c } example compile right with
>> 2.16.2 that comes with F19. Does it not use guile?
> 
> GNU/Linux is not Windows: you can usually have several different
> versions of libraries installed at the same time.
> 
> However, most distributions only allow one _development_ version to be
> installed at the same time.  If you are _developing_ more than one
> application that compiles with Guile libraries, you need to install the
> development libraries and headers back and forth when changing to
> _compiling+ for the other application.  But _using_ the compiled
> applications with conflicting major library versions in parallel is no
> problem.
> 
> -- 
> David Kastrup
> 
> 
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel