For those that are interested :-)
---------- Forwarded message ----------
From: Justin M. Forbes <jforbes(a)redhat.com>
Date: Fri, Aug 2, 2013 at 4:08 PM
Subject: Rawhide kernel nodebug now has arms
To: Mailing-List fedora-kernel <kernel(a)lists.fedoraproject.org>
For those of you interested in arm kernels, the rawhide kernel nodebug
repository now includes non debug versions of arm rawhide kernels.
Details on how to access the repository can be found at:
kernel mailing list
I hope this is the right place to ask questions about Pidora as well.
I am having trouble installing packages from the repo. Any package that I
know is there, and I try to install, yum says: "No package XXX available."
When I download the package, and do "yum localinstall", I get the error:
Cannot add package XXX to transaction. Not a compatible architecture:
When I "rpm -i" the package, it works fine.
I'm now doing quite a lot of compilation on my Chromebook and my Trim
Slice. It's OK, provided that two processes don't try to hit the disk
at the same time, at which point everything grinds to a halt.
I'm using cheap SanDisk cards in both (not exactly sure of the model,
but they're the cheapest branded ones).
Question is, would I be better to:
- Use cards such as the "SanDisk Extreme Pro"
(Does it make a difference, or is it designed to separate me from
my hard-earned money?)
- Try again with using network drive, eg. iSCSI? NFS? NBD? gluster ..?
(Note: the Chromebook kernel doesn't support NFS)
- Is there a good performing network device which is less horrible to
configure than iSCSI?
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
virt-top is 'top' for virtual machines. Tiny program with many
powerful monitoring features, net stats, disk stats, logging, etc.
2013/8/2 Adam Jackson <ajax(a)redhat.com>:
> On Fri, 2013-08-02 at 11:38 +0200, Florian Weimer wrote:
>> On 08/02/2013 09:45 AM, Richard W.M. Jones wrote:
>> > Judging by a google search for "qreal" "float" "arm" this difference
>> > causes endless problems. I even found a Fedora build bug related to it.
>> > However it's a matter for upstream to fix it. Not something we could
>> > carry around only in Fedora IMHO.
>> I would expect that consistency across Fedora architectures is more
>> important than alignment to upstream.
> If we're going to start casually disregarding binary portability between
> Fedora and other Linuxes, this is not where I'd start.
Last time I looked at it, it was not easy either, because there was too
much inline asm for 32 bit float, so, was not just switching some typedef.
qreal as float also causes a lot of other problems because everybody
expects qreal to be double, even when expanding those inline functions
with a constant argument, need to cast it to float or it will not compile.
Most trouble I had was python bindings, because there are too many
dynamically generated files, and it is not trivial to patch those to create
temporary vectors to convert float vectors to/from double vectors.
> - ajax