On Fri, Feb 09, 2018 at 11:34:12AM +0100, John Paul Adrian Glaubitz wrote:
> This is something that needs to be discussed. A single user alone shouldn't
> warrant such major change in a port. You always have to keep in mind that
> changing the default compiler options also has potential impact on t
Hi all,
On Fri, Feb 9, 2018 at 1:12 PM, Luuk van Dijk wrote:
> I apologize for the 'reply in 48 hours' spam my extcontacts mailinglist
> caused for any of you that replied here. I asked bas to keep us posted but
> i didn't realize it would send this out. I switched it off.
>
> thanks for all yo
Many thanks!
— Christian
Sent from my iPhone
> On 9. Feb 2018, at 13:26, Bas Vermeulen wrote:
>
> Sorry about the delay. You can find the glibc-2.26 compiled with powerpc64 at
> http://blackstar.xs4all.nl/glibc-2.26-ppc64-powerpc64.tgz
>
> Bas Vermeulen
>
>> On Tue, Feb 6, 2018 at 6:30 PM,
Just for posterity, I realized that system_profiler and /sys do not
provide exactly the same representation for the same information. For
comparison:
system_profiler:
Boot ROM Version: 4.8.9f4
Serial Number: YM5306NSTYX
But:
$ hexdump -C
"/sys/firmware/devicetree/base/rom@ff80/boot-ro
Sorry about the delay. You can find the glibc-2.26 compiled with powerpc64
at http://blackstar.xs4all.nl/glibc-2.26-ppc64-powerpc64.tgz
Bas Vermeulen
On Tue, Feb 6, 2018 at 6:30 PM, Christian Zigotzky
wrote:
> Hi Bas,
>
> Thank you. Could you please upload the libm when you are finished with
>
Taking extcont...@daedalean.ai out of the cc list (it has an auto replay I
didn't know about, sorry).
Bas Vermeulen
On Fri, Feb 9, 2018 at 12:56 PM, Bas Vermeulen wrote:
> diff of gcc -dM -E - without and with the patch applied:
>
> --- gcc-default 2018-01-28 18:06:14.11600 +
> +++ gcc-
diff of gcc -dM -E - without and with the patch applied:
--- gcc-default 2018-01-28 18:06:14.11600 +
+++ gcc-powerpc64 2018-01-28 18:03:06.57200 +
@@ -34,7 +34,6 @@
#define __FLT64_DECIMAL_DIG__ 17
#define __GCC_ATOMIC_CHAR32_T_LOCK_FREE 2
#define pixel pixel
-#define _ARCH_PPCS
We need this change too. We have e5500 CPU’s in our AmigaOnes.
— Christian
Sent from my iPhone
> On 9. Feb 2018, at 11:34, John Paul Adrian Glaubitz
> wrote:
>
>> On 02/09/2018 11:30 AM, Bas Vermeulen wrote:
>> mator on #debian-ports compiled gcc-7 for me with the attached patch.
>> With the
On Fri, Feb 9, 2018 at 11:34 AM, John Paul Adrian Glaubitz
wrote:
> On 02/09/2018 11:30 AM, Bas Vermeulen wrote:
>>
>> mator on #debian-ports compiled gcc-7 for me with the attached patch.
>> With the resulting gcc, I compiled glibc and got a library I can use
>> sqrtf without running into an ille
On 02/09/2018 11:30 AM, Bas Vermeulen wrote:
mator on #debian-ports compiled gcc-7 for me with the attached patch.
With the resulting gcc, I compiled glibc and got a library I can use
sqrtf without running into an illegal instruction exception.
Would it be possible to get this applied by default
Hi,
mator on #debian-ports compiled gcc-7 for me with the attached patch. With
the resulting gcc, I compiled glibc and got a library I can use sqrtf
without running into an illegal instruction exception.
Would it be possible to get this applied by default? The resulting binaries
work on e6500, an
11 matches
Mail list logo
