Here's the answer:
bash-3.00$ ldd /usr/local/lib/python2.6/lib-dynload/readline.so
libreadline.so.5 => (file not found)
libncurses.so.5 => /usr/local/lib/libncurses.so.5
libgcc_s.so.1 => /usr/local/lib/libgcc_s.so.1
libc.so.1 => /usr/lib/libc.so.1
libm.so.2 => /usr/lib/libm.so.2
/platform/SUNW,SPARC-Enterprise-T5120/lib/libc_psr.so.1
Which is quite consistent with the error message...
What about the other problem with waf? How could it be a problem not
to found "cc", when "gcc or cc" was found at previous step?
On Nov 7, 7:18 pm, Martin Zibricky <[email protected]> wrote:
> 2011/11/7 Joël Bourgault <[email protected]>
>
> > So now, as I'm testing of 1.5r1719:
> > (*) I'm not facing the issue I reported in my first message;
>
> > (*) waf will start, but will report a strange answer:
> > {{{
> > bash-3.00$ python waf configure build install
> > SunOS-32bit detected
> > Checking for program gcc or cc : /usr/local/bin/gcc
> > Checking for program cc : not found
> > /home/bourgaul/PyInstaller-1.5r1719/source/wscript:107: error:
> > could not configure a c compiler!
> > }}}
>
> > (*) Subsidiary question: I still get an error message:
> > {{{
> > E: cannot find libreadline.so.5 in path (needed by /usr/local/lib/
> > python2.6/lib-dynload/readline.so)
> > }}}
> > Any idea of what script is using this library?
>
> What is on your system output of command
>
> ldd /usr/local/lib/python2.6/lib-dynload/readline.so
>
> Maybe you could try set $LD_LIBRARY_PATH to point to directory where is
> libreadline.so.5 before running bootloader compilation.
--
You received this message because you are subscribed to the Google Groups
"PyInstaller" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/pyinstaller?hl=en.
