-
Notifications
You must be signed in to change notification settings - Fork 30.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aix: build failure with linker error in debug mode #14080
Comments
-bnoquiet flag produced this info:
|
|
smallest code that reproduces the error, with the class heirarchy retained: class TimezoneCache {
public:
virtual void foo() = 0;
virtual ~TimezoneCache() {}
};
class PosixTimezoneCache : public TimezoneCache {
public:
void foo() override;
~PosixTimezoneCache() override {}
};
class AIXTimezoneCache : public PosixTimezoneCache {
void foo() override;
~AIXTimezoneCache() override {}
};
void AIXTimezoneCache::foo() {}
int main() {
} Resolution of the function foo is what causes the issue - looks like PosixTimezoneCache is deemed abstract and no vtable is created for it. This code fails in Linux too with similar linker error:
But I guess the scenario does not affect Linux, as it uses PosixTimezoneCache, with no next level inheritance. If I define foo inline within the AIXTimezoneCache class the problem goes away, don't know what it means. |
|
Can this be closed? |
@bnoordhuis - no I guess, @jbajwa is working on this with v8 |
@gireeshpunathil |
@jbajwa Cherry-pick the patch to deps/v8 and open a PR. See |
@bnoordhuis |
@jbajwa FWIW I think this is the relevant section of the guide: https://github.com/nodejs/node/blob/master/doc/guides/maintaining-V8.md#backporting-to-abandoned-branches |
This was fixed by 8096791. |
The text was updated successfully, but these errors were encountered: