Oh I knew this would happen... the send-button is a magic
memory-enhancer in disguise. One (of probably many) forgotten bits, this
time hopefully with working address for Dennish too:
On 09/15/2011 01:55 PM, Jon Masters wrote:
All of the existing stuff assumes that if we have vfpv3 on
On Fri, 2011-09-16 at 12:46 +0300, Panu Matilainen wrote:
One simple brute-force solution that should work right now is to just
keep the softfp/hardfp architectures incompatible from rpm POV and
make the assumption that hardfp ABI will be used if the system is
capable of it. And if
On Fri, 2011-09-16 at 12:02 +0300, Panu Matilainen wrote:
On 09/15/2011 01:55 PM, Jon Masters wrote:
1) Location of libraries and the like: the libraries for different ABI's
need to go to separate paths. Currently the non-debian world knows /lib
and /lib64, and while it's of course possible
Resending i posted to list from address not subscibed
On Friday, September 16, 2011 04:46:33 AM Panu Matilainen wrote:
Oh I knew this would happen... the send-button is a magic
memory-enhancer in disguise. One (of probably many) forgotten bits, this
time hopefully with working address for
On 9/16/11 4:02 AM, Panu Matilainen wrote:
On 09/15/2011 01:55 PM, Jon Masters wrote:
...
What I want out of this discussion is a decision around how multiple
ABIs within an architecture will be handled in general. If you're
allergic to ARM, consider that in the Intel space there is now
