[cups.general] update to cups 1.1.21: /usr/lib/i686 no such file or directory

[ekkard gerlach]

Klaus Singvogel schrieb:
> ekkard gerlach wrote:
> 
>>Hi,
>>I updated Suse 8.2 to cups 1.1.21. Jobs are not printed,
>>no /var/log/cups/error_log is created (debug level set in cups.conf)
> 
> 
> Its cupsd.conf. Please note the "d".
you're right, of course. I've forgotten the d. I've always edited
the right  file, the cupsd.conf (I always use TAB-key to complete,
so I make no errors)

I deinstalled cups 1.1.21 and reinstalled cups from Suse 8.2-CD's
because I need to print  :-)
Now cupsd is working again an I get output to error_log.

I reinstalled gimp-print with

"
   1) Compile a fresh tarball using

  ./configure --disable-shared
  make
  make install

  to build statically linked copies of the binaries (in particular,
  genppd).

   2) Compile a fresh tarball using

  ./configure --prefix=/usr
  make
  make install
  make clean
  make
  make install
"

like advised in [Gimp-print-devel]  mailinglist. I wanted
to make a last attemp.
I remared this time, that make was interrupted:

/usr/lib/gcc-lib/i486-suse-linux/3.3/../../../../i486-suse-linux/bin/ld: 
cannot find -lssl

later:

/usr/lib/gcc-lib/i486-suse-linux/3.3/../../../../i486-suse-linux/bin/ld: 
cannot find -lcrypto

I didn't korrect that the first time!
Solution for Suse 8.2:

ln -s /usr/lib/libssl.so.0 /usr/lib/libssl.so
ln -s /usr/lib/libcrypto.so.0 /usr/lib/libcrypto.so

Now make produces much more output :-)

But the error rests the same:
/var/log/cups/error_log: (debug level)
[...]
Unable to convert file 0 to printable format for job 19!
Hint: Do you have ESP Ghostscript installed?
[...]

It's the same state like yesterday. This evening I'll
install cup 1.1.21 once again. Perhaps it's running ....

thx
Ekkard


> 
> 
>>/etc/ld.so.preload  doesn't exist either!
>>
>>I typed:
>>ln -s /usr/lib/libcups.so.2  /usr/lib/i686/libcups.so.2
>>ln -s /lib/ /usr/lib/i686/mmx
>>
>>and now there rests
>>open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or ...
>>
>>But no jobs are printed, no error_log is generated.
>>
>>Why didn't configure detect missing files?
> 
> 
> Sorry, but you are confusing. I doubt about your whole installation
> process.
> 
> Did you configure, compile, and install the package yourself or
> did you only install a ready RPM found somewhere for an abitrary
> Linux version (probably not for SuSE 8.2)?
> 
> Regards,
> 	Klaus.