[PlanetCCRMA] Major problem / confusion

[Bernardo Barros]

I can see that I get this error, but fomus produce a .ly file, it just
doesn't call lilypond to render it.
The error message is annoying but I can live with that

that's what I get:

[smoge at localhost ~]$ ldd /usr/bin/fomus
	linux-vdso.so.1 =>  (0x00007fff569dc000)
	libfomus.so => /usr/lib64/libfomus.so (0x00007ffd71d8a000)
	libncurses.so.5 => /lib64/libncurses.so.5 (0x0000003aac400000)
	libtinfo.so.5 => /lib64/libtinfo.so.5 (0x0000003e3da00000)
	libboost_program_options-mt.so.1.44.0 =>
/usr/lib64/libboost_program_options-mt.so.1.44.0 (0x0000003b09c00000)
	libdl.so.2 => /lib64/libdl.so.2 (0x0000003b06800000)
	libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003b09400000)
	libm.so.6 => /lib64/libm.so.6 (0x0000003b07000000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003b07800000)
	libc.so.6 => /lib64/libc.so.6 (0x0000003b06400000)
	libboost_system-mt.so.1.44.0 =>
/usr/lib64/libboost_system-mt.so.1.44.0 (0x0000003aad000000)
	libboost_filesystem-mt.so.1.44.0 =>
/usr/lib64/libboost_filesystem-mt.so.1.44.0 (0x0000003aad800000)
	libboost_thread-mt.so.1.44.0 =>
/usr/lib64/libboost_thread-mt.so.1.44.0 (0x00000032e9e00000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003b06c00000)
	librt.so.1 => /lib64/librt.so.1 (0x0000003b07400000)
	/lib64/ld-linux-x86-64.so.2 (0x0000003b06000000)
[smoge at localhost ~]$ whereis fomus
fomus: /usr/bin/fomus /usr/lib64/fomus /usr/include/fomus.h
/usr/include/fomus /usr/share/fomus
[smoge at localhost ~]$


2010/12/9 Fernando Lopez-Lezcano <nando at ccrma.stanford.edu>:
> On 12/09/2010 02:56 PM, Bernardo Barros wrote:
>> $  rpm -q -a | grep boost
>> boost-math-1.44.0-1.fc14.x86_64
>> boost-graph-1.44.0-1.fc14.x86_64
>> boost-1.44.0-1.fc14.x86_64
>> boost-static-1.44.0-1.fc14.x86_64
>> boost-system-1.44.0-1.fc14.x86_64
>> boost-date-time-1.44.0-1.fc14.x86_64
>> boost-doc-1.44.0-1.fc14.noarch
>> boost-wave-1.44.0-1.fc14.x86_64
>> boost-filesystem-1.44.0-1.fc14.x86_64
>> boost-serialization-1.44.0-1.fc14.x86_64
>> boost-thread-1.44.0-1.fc14.x86_64
>> boost-regex-1.44.0-1.fc14.x86_64
>> boost-signals-1.44.0-1.fc14.x86_64
>> boost-iostreams-1.44.0-1.fc14.x86_64
>> boost-devel-1.44.0-1.fc14.x86_64
>> boost-python-1.44.0-1.fc14.x86_64
>> boost-program-options-1.44.0-1.fc14.x86_64
>> boost-test-1.44.0-1.fc14.x86_64
>>
> Same version I used. In fact there were no updates since fc14 came out.
> Maybe it is a bug in fomus after all? Or maybe there is some leftover
> files somewhere from your previous install? What do you see if you do an
> "ldd /usr/bin/fomus"? What if you do a "whereis fomus"?
>
> This is what gets installed when I install fomus in my mock chroot build
> environment:
>
> ----
> DEBUG:
> ================================================================================
> DEBUG:  Package                Arch    Version
> Repository    Size
> DEBUG:
> ================================================================================
> DEBUG: Installing:
> DEBUG:  fomus                  x86_64  0.1.13-1.alpha.fc14.ccrma
> planetccrma  3.9 M
> DEBUG: Installing for dependencies:
> DEBUG:  boost-filesystem       x86_64  1.44.0-1.fc14
> fedora        45 k
> DEBUG:  boost-iostreams        x86_64  1.44.0-1.fc14
> fedora        46 k
> DEBUG:  boost-program-options  x86_64  1.44.0-1.fc14
> fedora       144 k
> DEBUG:  boost-system           x86_64  1.44.0-1.fc14
> fedora        24 k
> DEBUG:  boost-thread           x86_64  1.44.0-1.fc14
> fedora        46 k
> DEBUG: Transaction Summary
> DEBUG:
> ================================================================================
> ----
>
> -- Fernando
>
> _______________________________________________
> PlanetCCRMA mailing list
> PlanetCCRMA at ccrma.stanford.edu
> http://ccrma-mail.stanford.edu/mailman/listinfo/planetccrma
>