Followup-For: Bug #738575
X-Debbugs-Cc: raykinsell...@gmail.com
On Thu, 16 Nov 2023 12:47:40 +, James wrote:
> I've been thinking more about how to improve the chances that the
> package could be accepted into Debian -- my suggestion would be to
> rebuild it and upload it to the mentors[1]
On Thu, 16 Nov 2023 at 09:57, Ray Kinsella wrote:
>
> On Wed, 15 Nov 2023 at 22:30, James Addison wrote:
>>
>> On Wed, 15 Nov 2023 at 21:57, Ray Kinsella wrote:
> [...]
> I spent a not insignificant amount of time devising this solution, to get
> "Debian Support"
> After a few false starts and
On Wed, 15 Nov 2023 at 22:30, James Addison wrote:
> On Wed, 15 Nov 2023 at 21:57, Ray Kinsella
> wrote:
> >
> > Thanks for this - you are kind to look at this issue.
>
> You're welcome - I enjoyed learning a bit about the Quark hardware,
> and the esoteric lock bug. A shame I didn't learn
On Wed, 15 Nov 2023 at 21:57, Ray Kinsella wrote:
>
> Thanks for this - you are kind to look at this issue.
You're welcome - I enjoyed learning a bit about the Quark hardware,
and the esoteric lock bug. A shame I didn't learn about it five years
ago I suppose, but there we are.
> It's been a
Hi James,
Thanks for this - you are kind to look at this issue.
It's been a long time since Intel manufactured the X1000 / Quark, I am not
sure how many are left in the wild.
Do you think this is something that Debian might want to package and ship?
Thanks,
Ray K
On Wed, 15 Nov 2023 at 12:27,
Followup-For: Bug #738575
X-Debbugs-Cc: raykinsell...@gmail.com
If I understand correctly, then Ray's libx1000 library[1] provides a way to
work around this in software. It uses some LD_PRELOAD magic, and from what I
remember, it's worth being careful when using that approach.
I opened an
What version of glibc are you compiling? Can you offer some more
assistance as to how you compiled it? Are you cross-compiling or do have
a working set of tools on your galileo to compile natively?
I am attempting to compile from my Ubuntu 14.04 (64-bit) machine with
Hi,
FWIW: I've got a Galileo board and am running into similar issuse (while
running CentOS 5 on it ;))
Exact same error at the exact same location; it's not the instruction
that is not supported , a very small piece of test code that does
lock cmpxchgl %edx, (%eax)
works just fine - and
On Thu, May 08, 2014 at 04:45:00PM +0200, Jan Just Keijser wrote:
Hi,
FWIW: I've got a Galileo board and am running into similar issuse
(while running CentOS 5 on it ;))
Exact same error at the exact same location; it's not the
instruction that is not supported , a very small piece of
Hi,
On 08/05/14 22:11, Aurelien Jarno wrote:
On Thu, May 08, 2014 at 04:45:00PM +0200, Jan Just Keijser wrote:
Hi,
FWIW: I've got a Galileo board and am running into similar issuse
(while running CentOS 5 on it ;))
Exact same error at the exact same location; it's not the
instruction that is
On Mon, Jan 01, 2001 at 12:23:05AM +, Thomas Faust wrote:
Package: libc6
Version: 2.13-38
Severity: normal
File: pthread
Dear Maintainer,
I bootstrapped a Debian base system via debootstrap --arch i386 wheezy
./newfiles http://http.debian.net/debian/; and put it on a Galileo board.
The default toolchain (and thus libc) in Debian has been targetting
i586 for quite a while now. If this CPU doesn't provide *all* the
i586 instructions, I'd be pretty surprised if anything worked.
I was first trending in the same direction, but this is a different issue.
I compiled code with
Package: libc6
Version: 2.13-38
Severity: normal
File: pthread
Dear Maintainer,
I bootstrapped a Debian base system via debootstrap --arch i386 wheezy
./newfiles http://http.debian.net/debian/; and put it on a Galileo board. On
the Galileo board there new Intel Quark IA processor - which is
On Mon, Jan 01, 2001 at 12:23:05AM +, Thomas Faust wrote:
which is basically a 486 with some instructions extensions from Pentium.
The default toolchain (and thus libc) in Debian has been targetting
i586 for quite a while now. If this CPU doesn't provide *all* the
i586 instructions, I'd
14 matches
Mail list logo
