Bug#708143: mips64 and mips64el support without multilib
I refreshed this patch to add multilib support for mips64(el) and mipsn32(el) The mips* ask for o32 libraries to be put in /lib and /usr/lib, which make the change to debian/rules2 a little longer. With this package gcc-4.8 can build successfully on amd64, mipsel and mips64el. Besides the mips64(el) and mipsn32(el) support, I add support of DEB_BUILD_OPTIONS=nocheck support. On Wed, May 15, 2013 at 10:57 AM, YunQiang Su wzss...@gmail.com wrote: On Tue, May 14, 2013 at 11:16 PM, Matthias Klose d...@debian.org wrote: Am 13.05.2013 15:37, schrieb YunQiang Su: Package: gcc-4.8 We are working on mips64(el) port. The support of these architectures are finished, while multilib is still to do. This is the patch. You are introducing a new configuration, separate from the existing mips64 configurations. Could you explain why? And you keep the same multiarch name My fault, I will merge them. for both configurations. How do the new mips64 targets and the existing mips64 multilib relate to each other? I will support multilib finally. As my understand, the multilib-less is a step to the multilib support. Is it? I am very not sure. Matthias -- YunQiang Su -- YunQiang Su mips64.diff Description: Binary data
Bug#708143: mips64 and mips64el support without multilib
Am 13.05.2013 15:37, schrieb YunQiang Su: Package: gcc-4.8 We are working on mips64(el) port. The support of these architectures are finished, while multilib is still to do. This is the patch. You are introducing a new configuration, separate from the existing mips64 configurations. Could you explain why? And you keep the same multiarch name for both configurations. How do the new mips64 targets and the existing mips64 multilib relate to each other? Matthias -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5192556a.7060...@debian.org
Bug#708143: mips64 and mips64el support without multilib
On Tue, May 14, 2013 at 11:16 PM, Matthias Klose d...@debian.org wrote: Am 13.05.2013 15:37, schrieb YunQiang Su: Package: gcc-4.8 We are working on mips64(el) port. The support of these architectures are finished, while multilib is still to do. This is the patch. You are introducing a new configuration, separate from the existing mips64 configurations. Could you explain why? And you keep the same multiarch name My fault, I will merge them. for both configurations. How do the new mips64 targets and the existing mips64 multilib relate to each other? I will support multilib finally. As my understand, the multilib-less is a step to the multilib support. Is it? I am very not sure. Matthias -- YunQiang Su -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKcpw6X36JyQ-OqfCQELS3U4HBdfCywvzc2h24=pojz3r-h...@mail.gmail.com
Bug#708143: mips64 and mips64el support without multilib
Package: gcc-4.8 We are working on mips64(el) port. The support of these architectures are finished, while multilib is still to do. This is the patch. -- YunQiang Su mips64-without-multilib.patch Description: Binary data
