Hi!
On Mon, 25 Jun 2012 18:19:26 +0200, Matthias Klose d...@ubuntu.com wrote:
On 25.06.2012 15:56, Joseph S. Myers wrote:
On Mon, 25 Jun 2012, Matthias Klose wrote:
Please find attached the patch updated for trunk 20120625, x86 only,
tested on
x86-linux-gnu, KFreeBSD and the Hurd.
On 28.06.2012 12:01, Thomas Schwinge wrote:
Hi!
On Mon, 25 Jun 2012 18:19:26 +0200, Matthias Klose d...@ubuntu.com
wrote:
On 25.06.2012 15:56, Joseph S. Myers wrote:
On Mon, 25 Jun 2012, Matthias Klose wrote:
Please find attached the patch updated for trunk 20120625, x86 only,
tested on
Hi!
On Thu, 28 Jun 2012 12:42:23 +0200, Matthias Klose d...@ubuntu.com wrote:
On 28.06.2012 12:01, Thomas Schwinge wrote:
On Mon, 25 Jun 2012 18:19:26 +0200, Matthias Klose d...@ubuntu.com
wrote:
On 25.06.2012 15:56, Joseph S. Myers wrote:
On Mon, 25 Jun 2012, Matthias Klose wrote:
Please find attached the patch updated for trunk 20120625, x86 only, tested on
x86-linux-gnu, KFreeBSD and the Hurd.
I left in the comment about the multiarch names, but I'm fine to change/discard
it. It was first required by Joseph Myers, then not found necessary by Paolo
Bonzini.
Ok for the
On Mon, 25 Jun 2012, Matthias Klose wrote:
Please find attached the patch updated for trunk 20120625, x86 only, tested on
x86-linux-gnu, KFreeBSD and the Hurd.
This patch appears to include changes to config.gcc for other targets, not
mentioned in your ChangeLog entries. Please resubmit
On 25.06.2012 15:56, Joseph S. Myers wrote:
On Mon, 25 Jun 2012, Matthias Klose wrote:
Please find attached the patch updated for trunk 20120625, x86 only, tested
on
x86-linux-gnu, KFreeBSD and the Hurd.
This patch appears to include changes to config.gcc for other targets, not
Hi!
On Sat, 19 May 2012 18:05:30 +0200, I wrote:
On Wed, 09 May 2012 02:38:11 +0200, Matthias Klose d...@ubuntu.com wrote:
ok, the attached patch includes just the support for the x86 targets,
including
the kfreebsd and the hurd systems. The x32 multiarch tuple isn't yet
defined, so
Hi!
On Wed, 09 May 2012 02:38:11 +0200, Matthias Klose d...@ubuntu.com wrote:
ok, the attached patch includes just the support for the x86 targets,
including
the kfreebsd and the hurd systems. The x32 multiarch tuple isn't yet defined,
so
I'd like to keep it out of the first version.
I
Paolo Bonzini wrote:
Il 11/05/2012 07:13, Matthias Klose ha scritto:
+The multiarch tuples are defined
+in @uref{http://wiki.debian.org/Multiarch/Tuples}.
Is this needed? Aren't they defined simply by the GCC source code?
Surely if some other OS implements multiarch with different tuples
Il 11/05/2012 07:13, Matthias Klose ha scritto:
ok, I did clarify it in the existing documentation of MULTIARCH_DIRNAME in
fragments.texi, detailing the search order for the files. Should the search
order be mentioned in some user documentation as well? if yes, where?
Thanks! I don't think
On 11.05.2012 12:51, Paolo Bonzini wrote:
Il 11/05/2012 07:13, Matthias Klose ha scritto:
ok, I did clarify it in the existing documentation of MULTIARCH_DIRNAME in
fragments.texi, detailing the search order for the files. Should the search
order be mentioned in some user documentation as
Il 09/05/2012 19:19, Matthias Klose ha scritto:
these are referenced from the http://wiki.debian.org/Multiarch/Tuples
https://wiki.ubuntu.com/MultiarchSpec#Filesystem_layout
http://err.no/debian/amd64-multiarch-3
http://wiki.debian.org/Multiarch/TheCaseForMultiarch describes use cases for
On 10.05.2012 08:42, Paolo Bonzini wrote:
Il 09/05/2012 19:19, Matthias Klose ha scritto:
these are referenced from the http://wiki.debian.org/Multiarch/Tuples
https://wiki.ubuntu.com/MultiarchSpec#Filesystem_layout
http://err.no/debian/amd64-multiarch-3
Il 09/05/2012 02:38, Matthias Klose ha scritto:
Index: gcc/doc/invoke.texi
===
--- gcc/doc/invoke.texi (revision 187271)
+++ gcc/doc/invoke.texi (working copy)
@@ -6110,6 +6110,11 @@
@file{../lib32}, or if OS
On 09.05.2012 15:37, Paolo Bonzini wrote:
Il 09/05/2012 02:38, Matthias Klose ha scritto:
Index: gcc/doc/invoke.texi
===
--- gcc/doc/invoke.texi (revision 187271)
+++ gcc/doc/invoke.texi (working copy)
@@ -6110,6
Il 09/05/2012 17:34, Matthias Klose ha scritto:
So -print-multiarch is like --print-multi-os-directory?
the former prints the part before the `:' in the MULTILIB_OSDIRNAMES, the
latter
the part after the `':', e.g. ../lib32 and i386-linux-gnu.
Yes, of course.
What is the difference, and
On 09.05.2012 18:29, Paolo Bonzini wrote:
Il 09/05/2012 17:34, Matthias Klose ha scritto:
So -print-multiarch is like --print-multi-os-directory?
the former prints the part before the `:' in the MULTILIB_OSDIRNAMES, the
latter
the part after the `':', e.g. ../lib32 and i386-linux-gnu.
On Tue, 8 May 2012, Matthias Klose wrote:
On 20.08.2011 21:51, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a system
to
install and run applications of multiple different binary targets on the
same
system.
please find attached an updated
On 08.05.2012 15:20, Joseph S. Myers wrote:
On Tue, 8 May 2012, Matthias Klose wrote:
On 20.08.2011 21:51, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a system
to
install and run applications of multiple different binary targets on the
same
On 20.08.2011 21:51, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a system to
install and run applications of multiple different binary targets on the same
system.
please find attached an updated for the trunk (2012-05-08). The multiarch
triplets are
On Sun, 21 Aug 2011, Matthias Klose wrote:
On 08/20/2011 09:51 PM, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a system to
install and run applications of multiple different binary targets on the same
system. The idea and name of multiarch dates
On Tue, 1 Nov 2011, Marc Glisse wrote:
On Sun, 21 Aug 2011, Matthias Klose wrote:
On 08/20/2011 09:51 PM, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a
system to
install and run applications of multiple different binary targets on the
Hi!
On Sun, 21 Aug 2011 02:14:10 +0200, Matthias Klose d...@ubuntu.com wrote:
Non-text part: multipart/mixed
On 08/20/2011 09:51 PM, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a system
to
install and run applications of multiple different
On 08/21/2011 02:14 AM, Matthias Klose wrote:
On 08/20/2011 09:51 PM, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a system to
install and run applications of multiple different binary targets on the same
system. The idea and name of multiarch
On Sun, 21 Aug 2011, Matthias Klose wrote:
powerpc-linux-gnuspe
As noted, that's ambiguous; --enable-e500-double determines whether it's
e500v1 or e500v2, and since those have slightly different symbols exported
from libc I think they should be considered different here.
For MIPS, the
Multiarch [1] is the term being used to refer to the capability of a system to
install and run applications of multiple different binary targets on the same
system. The idea and name of multiarch dates back to 2004/2005 [2] (to be
confused with multiarch in glibc).
Multiarch defines new system
On Sat, Aug 20, 2011 at 09:51:33PM +0200, Matthias Klose wrote:
Tested on non-multilib'd and multilib'd systems, both native and cross builds.
Ok for the trunk?
I don't think we want to do this unconditionally, we already search way too
many directories by default. This is a Debian/Ubuntu
On Sat, 20 Aug 2011, Matthias Klose wrote:
The multiarch triplets are defined in the target specific tmake files, and
provided for all known existing multiarch implementations (currently Debian,
Ubuntu and derivatives). For non-multilib'd configurations, the triplet is
Is there a
On 08/20/2011 10:07 PM, Jakub Jelinek wrote:
On Sat, Aug 20, 2011 at 09:51:33PM +0200, Matthias Klose wrote:
Tested on non-multilib'd and multilib'd systems, both native and cross
builds.
Ok for the trunk?
I don't think we want to do this unconditionally, we already search way too
many
On 08/20/2011 10:39 PM, Joseph S. Myers wrote:
On Sat, 20 Aug 2011, Matthias Klose wrote:
The multiarch triplets are defined in the target specific tmake files, and
provided for all known existing multiarch implementations (currently Debian,
Ubuntu and derivatives). For non-multilib'd
On 08/20/2011 09:51 PM, Matthias Klose wrote:
Multiarch [1] is the term being used to refer to the capability of a system to
install and run applications of multiple different binary targets on the same
system. The idea and name of multiarch dates back to 2004/2005 [2] (to be
confused with
On Sat, Aug 20, 2011 at 5:11 PM, Matthias Klose d...@ubuntu.com wrote:
For MIPS, the hard-float and soft-float ABIs are incompatible. So you
need twelve triplets, not six.
yes. but I didn't see a soft-float mips port yet.
We at Cavium has a soft-float mips port and in fact use debian as a
32 matches
Mail list logo
