Getting a weird linker error in my cpp code

[Aarnav-JP]

hi everyone , I am getting this error in my code I have never seen this before please help me resolve it -

0  0x1003e81a0  __assert_rtn + 140
1  0x10026fa8c  mach_o::relocatable::Parser<arm64>::parse(mach_o::relocatable::ParserOptions const&) + 4536
2  0x100241d38  mach_o::relocatable::Parser<arm64>::parse(unsigned char const*, unsigned long long, char const*, long, ld::File::Ordinal, mach_o::relocatable::ParserOptions const&) + 148
3  0x1002aa4ac  ld::tool::InputFiles::makeFile(Options::FileInfo const&, bool) + 1468
4  0x1002ad360  ___ZN2ld4tool10InputFilesC2ER7Options_block_invoke + 56
5  0x1a67101f4  _dispatch_client_callout2 + 20
6  0x1a6724f8c  _dispatch_apply_invoke_and_wait + 224
7  0x1a672426c  _dispatch_apply_with_attr_f + 1152
8  0x1a672447c  dispatch_apply + 108
9  0x1002ad1f4  ld::tool::InputFiles::InputFiles(Options&) + 616
10  0x10022f6c0  main + 552
A linker snapshot was created at:
        /tmp/prac-2022-09-16-202054.ld-snapshot
ld: Assertion failed: (_file->_atomsArrayCount == computedAtomCount && "more atoms allocated than expected"), function parse, file macho_relocatable_file.cpp, line 2061.
collect2: error: ld returned 1 exit status

code -

#include <bits/stdc++.h>

#define ll long long int
#define fori(a, b) for (ll i = a; i < b; i++)

#define all(x) (x).begin(), (x).end()

#define endl "\n"
#define fastinp                       \
    ios_base::sync_with_stdio(false); \
    cin.tie(NULL);

using namespace std;

void solve()
{
    ll n;
    cin >> n;
    vector<pair<ll, ll>> v(n);
    fori(0, n)
    {
        ll a;
        cin >> a;
        v.push_back({a, i + 1});
    }
    sort(all(v), greater<pair<ll, ll>>());
    ll sum = 0;
    ll cans = 0;
    fori(0, n)
    {
        sum += ((cans * v[i].first) + 1);
        cans++;
    }
    cout << sum << endl;
    for (auto it : v)
    {
        cout << it.second << " ";
    }
    cout << endl;
}

int main()
{
    fastinp;

    int t = 1;

    if (0)
    {
        cin >> t;
    }
    for (; t != 0; --t)
        solve();

    return 0;
}

[danjin250]

I don't think it's an issue with your code, I think there's just an actual linker bug.

You haven't mentioned your OS and XCode version but I'm guessing MacOS Monterey and XCode 13 or 14?
Perhaps you're suffering the same issue as these ones

iains/gcc-12-branch#6
spack/spack#32640

[Aarnav-JP]

thanks for your reply. yeah I am using Monterey and Xcode 14. So there is nothing that can be done from my side?

[teshields]

I am getting the same link error during portability tests of my application using the Homebrew GNU C++ compilers (version 11.3.0 & 12.2.0), after upgrading to Xcode 14.0 on macOS Monterey 12.6 (M1 chip). The application compiles & links & runs AOK with the Xcode 14 C++ compiler (Xcode is the development environment).

Probably unsurprisingly, the portability tests using the Homebrew LLVM C++ compilers (versions 11.1.0, 12.0.1, 13.0.1 & 14.0.6) see no problems.

[Satyam230ct]

Same error i'm getting after updating my macOs to Monterey 12.6 (M1 chip) and using Xcode 14.0

[Satyam230ct]

Please notify me if you find any solution for this

[amitsingh0823]

use gnu++14

[theharshpat]

Having the same issue after the Xcode update. macOS 12.5.1, Xcode Version 14.0 (14A309), M1 processor.

[Bo98]

Yes, this is a Xcode 14 bug. Apple are working on this. It should be fixed in a future Xcode beta (not 14.1 beta 1).

The only known workaround is downgrading to Xcode 13.4.

[LuisMiguelSS]

@NikithGanga your link seems to be pointing at a Github Homebrew discussion

Here's the link, for everyone's comfort: https://developer.apple.com/download/all/ ;)

[Techie232]

@NikithGanga thank you very much brother!!

[jatin1510]

After upgrading to macOs sonoma, the issue remains. If we try to reinstall the old command line tools, package installer gives the error macOs is too new.

Any suggestions or quick fixes?

[NikithGanga]

@jatin1510 Relink or join the system link, which you intially used to compile your programs with.It should work now

[jatin1510]

Can not understand what you are saying...

[seye11]

I used -O2 to compile my cpp file, and it works!

• Xcode 14.0.1 on macOS Monterey 12.6(intel)

Hope it can help you.

[thinkyhead]

Under the MacPorts package system this did the trick for my purposes today (to be able to do a native build under PlatformIO):

sudo port install gcc12
cd /opt/local/bin
sudo rm -f gcc g++ cc
sudo ln -s gcc-mp-12 gcc ; sudo ln -s g++-mp-12 g++ ; sudo ln -s g++ cc
cd -
rehash

The same general idea should also work for Homebrew. We'll see if it continues to work under macOS 13 Ventura.

[chriselrod]

I get the same error with 14.2: https://github.com/JuliaSIMD/LoopModels/actions/runs/3777632683/jobs/6421565544

[egorpugin]

@chriselrod
Look at line 335, you are using 14.0.1 xcode.
-isysroot /Applications/Xcode_14.0.1.app

Anyways github CI has 14.1 only at the moment.

[chriselrod]

Okay, I had an action that ran

> echo $(pkgutil --pkg-info=com.apple.pkg.CLTools_Executables)
package-id: com.apple.pkg.CLTools_Executables version: 14.2.0.0.1.1668646533 volume: / location: / install-time: 1671153287 groups: com.apple.FindSystemFiles.pkg-group

which is why I said 14.2.
But looking at the logs, you're obviously right.

[carlocab]

@chriselrod try

sudo xcode-select --switch /Library/Developer/CommandLineTools

to use the newer CLT SDK.

[chriselrod]

Great, that worked! No more linker error, but many tests segfault for some reason: https://github.com/JuliaSIMD/LoopModels/actions/runs/3784846071/jobs/6434459661