> On 20 Sep 2023, at 22:45, Marc Culler wrote:
>
> I learned by reading the release notes for XCode 15 that Apple rewrote the
> linker for XCode 15. They also made the old linker available by using -ld64
> as a linker option.
One should use -ld_classic as -ld64 is deprecated by a warning I
This appears to be a completely independent bug in Apple's new linker.
(You are linking with libgmp, but presumably that library was built with a
different linker. And the "error" is different.) Once I knew what to look
for I found lots of issues with the new linker reported on the Apple
> On 22 Sep 2023, at 00:10, Marc Culler wrote:
>
> This appears to be a completely independent bug in Apple's new linker. (You
> are linking with libgmp, but presumably that library was built with a
> different linker. And the "error" is different.)
It may be because I use atomic code,
Marc Culler writes:
If you read my earlier messages you will see that I did try that and that
it failed in exactly the same way. I am not trying to get the GMP
maintainers to do anything which is impossible (unless you count trying to
get Apple to fix bugs -- something which is
> On 20 Sep 2023, at 22:45, Marc Culler wrote:
>
> I learned by reading the release notes for XCode 15 that Apple rewrote the
> linker for XCode 15. They also made the old linker available by using -ld64
> as a linker option.
When I use the new linker, using MacPorts gcc12 and gmp-6.2.1, I
This message is just to make sure that the situation is clear.:
1. Building gmp with -enable-fat fails with the XCode 15 compiler and the
new XCode 15 linker. The error reported by the linker is impossible. It is
reporting an out of range branch instruction in a function which is written
in
On Wed, Sep 20, 2023 at 3:44 PM Torbjörn Granlund wrote:
> Marc Culler writes:
>
> It is not possible for the GMP maintainers to analyse the effects of
> various options which we do not know about. As I wrote before, please
> just use --enable-fat.
>
If you read my earlier messages you will
I have found a workaround -- NOT A FIX -- for this problem.
I learned by reading the release notes for XCode 15 that Apple rewrote the
linker for XCode 15. They also made the old linker available by using
-ld64 as a linker option. Sure enough, if I add
$ export LDFLAGS="-ld64"
then my build
Marc Culler writes:
The build fails in the same way when I remove --enable-fat but use
export CFLAGS="-arch x86_64 -mmacosx-version-min=10.9 -mno-avx -mno-avx2
-mno-bmi2"
If it "fails in the same way" without --enable-fat, your machine has
gremlins. The problem symbol is very specific to
Marc Culler writes:
With no CFLAGS and using
$ ./configure --with-pic --enable-fat --prefix=X
I get almost the same error (the difference being the distance of the
branch), namely:
It is not possible for the GMP maintainers to analyse the effects of
various options which we do not
And one more --
The build fails in the same way when I remove --enable-fat but use
export CFLAGS="-arch x86_64 -mmacosx-version-min=10.9 -mno-avx -mno-avx2
-mno-bmi2"
I am concluding that Apple has silently dropped support for old Intel CPUs
which are supported by OSX 10.9.
- Marc
On Wed, Sep
One more data point -- I do get a successful build if I omit the
--enable-fat option. That means no CFLAGS and configuring with:
$ ./configure --with-pic --prefix=XX
In this case the compiler options include:
-mtune=skylake -march=broadwell
- Marc
On Wed, Sep 20, 2023 at 11:49 AM Marc
With no CFLAGS and using
$ ./configure --with-pic --enable-fat --prefix=X
I get almost the same error (the difference being the distance of the
branch), namely:
ld: branch8 out of range 378633 in ___gmpn_add_nc_x86_64
- Marc
On Wed, Sep 20, 2023 at 11:25 AM Hans Åberg wrote:
>
>
> > On
> On 20 Sep 2023, at 16:36, Marc Culler wrote:
>
> …macOS Sonoma beta…
…
> …using: "Apple clang version 15.0.0
> (clang-1500.0.40.1)"
The same compiler version is now available on MacOS 13, together with Xcode 15.
___
gmp-bugs mailing list
I get exactly the same error with:
export CFLAGS="-arch x86_64 -mmacosx-version-min=10.9"
I will also try removing those options.
- Marc
On Wed, Sep 20, 2023 at 10:48 AM Marc Culler wrote:
> Thanks for replying!
>
> The reason for the options "-mno-avx -mno-avx2 -mno-bmi2" is that it is
>
Thanks for replying!
The reason for the options "-mno-avx -mno-avx2 -mno-bmi2" is that it is
important for us to have a gmp which runs on old intel hardware. And we
had no trouble with those options until this version of clang.
Also, the function in which ld claims to find the out-of-range
Marc Culler writes:
I am unable to build gmp-6.2.1 on macOS Sonoma beta using the command line
tools released for that system. The system is up to date. The hardware of
the build system is "1.6 GHz Dual-Core Intel Core i5".
The build commands I am using are:
$ export
I am unable to build gmp-6.2.1 on macOS Sonoma beta using the command line
tools released for that system. The system is up to date. The hardware of
the build system is "1.6 GHz Dual-Core Intel Core i5".
The build commands I am using are:
$ export GMPPREFIX=/a/path/on/my/system
$ export
18 matches
Mail list logo
