GCC errors: undefined __symbol_name; maybe you meant __symbol_name$non_lazy_ptr #41
Replies: 4 comments 7 replies
-
|
which GCC12 version ? |
Beta Was this translation helpful? Give feedback.
-
|
@iains I am pretty convinced now that something not working well with The case above, – build is broken on 10A190 and 10.6.8 Rosetta with Everything else identical (within each setup). On 10A190 the build fixed itself by installing and using P. S. This is not a question or request, I just report the finding, since it might be useful. |
Beta Was this translation helpful? Give feedback.
-
|
The problem turned out to be quite common in fact: I am seeing these linking failures with many ports recently (mostly on Rosetta, I am just back to native PPC machines). (P. S. This, ironically, turned out to be a rather unique case: I got the same failure with gcc11, first time on my memory. Also Rosetta, so I am quite puzzled now.) |
Beta Was this translation helpful? Give feedback.
-
|
@iains For the record, it seems that https://github.com/iains/gcc-12-branch/tree/gcc-12-2-darwin-pre-r1 branch does not fix the issue, though it expresses itself a bit differently, now at compile time: I understand that the branch in question is not a release, so just updating on results. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
To be clear, here I am not talking about 10.6 PPC with patched GCC, but about 10.6.8 with stock GCC.
I got the following failure now with
follyon Rosetta (somewhat surprising, since I have built it on Rosetta earlier):I remember to have gotten alike error with
fb303(unsolved), one offollydependents, and maybe somewhere else too.@iains Is this a recognizable pattern? (I do not suspect GCC bug here, it is either source code was having Clang in mind and nothing else, or fixes for PPC are needed.)
Beta Was this translation helpful? Give feedback.
All reactions