Matthew Yee-King wrote:
> Hello!
>
> I am attempting to install a samsung ml-1520 usb printer on my debian
> etch amd64 system. I have only been able to install this printer on an
> i386 system using proprietary drivers in the past, and that is what I am
> using now. The thing is that the install script appears to detect a
> glibc 2.0 system and fail, telling me to install 2.1 or newer.
>
> I am using libc6 2.3.6-3 in the amd64 part and 2.3.6-3 in my 32 bit
> chroot. I'm running the script from within the amd 64 system, but have
> created symlink to /emul/ia32-linux/lib/ld-linux.so.2 in /lib.
>
> Heres the bit of the script that does the detection:
>
> DetectLIBC()
> {
> status=1
> if [ `uname -s` != Linux ]; then
> echo "detected glibc-2.1"
> return $status
> fi
> if [ -f `echo /lib/libc.so.6* | tail -1` ]; then
> if fgrep GLIBC_2.1 /lib/libc.so.6* 2> $NULL >> $NULL; then
> echo "glibc-2.1"
> status=0
> else
> echo "glibc-2.0"
> status=0
> fi
> elif [ -f /lib/libc.so.5 ]; then
> echo "libc5"
> status=0
> else
> echo "unknown"
> fi
> return $status
> }
>
> Though it is a gtk app that is launched later in the installer that
> actually fails with the 2.0 problem- but this script detects a glibc 2.0
> so I'm guessing it has the same problem as the gtk app.
>
> How might I convince this script I have a 2.1 glibc? Is it somehow
> testing my 32 bit emualted glibs and seeing it as version 2.0?
>
> cheers
>
> matthew
>
>
There is a note at the bottom of the ML-1510 entry at linuxprinting.org
[0] where some states that the the ML-1520 works perfectly by following
the setup instructions for the ML-1510. I would start there.
-Roberto
[0] http://linuxprinting.org/show_printer.cgi?recnum=Samsung-ML-1510
--
Roberto C. Sanchez
http://familiasanchez.net/~roberto
Attachment:
signature.asc
Description: OpenPGP digital signature