On Fri, 2003-09-26 10:41:19 -0700, Markus Mayer <[EMAIL PROTECTED]>
wrote in message <[EMAIL PROTECTED]>:
> On Thu, Sep 25, 2003 at 09:29:33AM -0700, Markus Mayer wrote:
>
> > I also tried to find an older version of libc (like 2.3.1-something).
> > Google still finds them, but they've all been pu
On Wed, 2003-09-24 19:24:00 -0700, Markus Mayer <[EMAIL PROTECTED]>
wrote in message <[EMAIL PROTECTED]>:
> Hi,
>
> I'm using Debian 'testing' on a SPARCstation 10 and getting really
> desperate since I'm experiencing a SIGILL problem with libc.
>
> The last update installed the newest libc (2.3.
Hi,
I'm using Debian 'testing' on a SPARCstation 10 and getting really
desperate since I'm experiencing a SIGILL problem with libc.
The last update installed the newest libc (2.3.2-7), but now each program
that uses sscanf (and maybe other functions, too) produces an illegal
instruction (SIGILL).
Ah, here's finally my first post on that matter. Since it didn't show up for
about 12 hours I re-posted. Sorry about that, but I thought the mail got
lost somewhere.
Markus
Hi,
I'm using Debian 'testing' on a SPARCstation 10 and getting really
desperate since I'm experiencing a SIGILL problem with libc.
The last update installed the newest libc (2.3.2-7), but now each program
that uses sscanf (and maybe other functions, too) produces an illegal
instruction (SIGILL).
On Thu, Sep 25, 2003 at 09:29:33AM -0700, Markus Mayer wrote:
> I also tried to find an older version of libc (like 2.3.1-something).
> Google still finds them, but they've all been pulled. Not a chance to
> download one anywhere. And using libc 2.2 is not possible as it would
> break *everything*
Hi,
I'm using Debian 'testing' on a SPARCstation 10 and getting really
desperate since I'm experiencing a SIGILL problem with libc.
The last update installed the newest libc (2.3.2-7), but now each program
that uses sscanf (and maybe other functions, too) produces an illegal
instruction (SIGILL).
7 matches
Mail list logo
