-
Notifications
You must be signed in to change notification settings - Fork 813
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
error: 'operator=' is a private member of 'glslang::TPoolAllocator' #1869
Comments
Ah so I hadn't noticed this earlier, but this error will only be raised if The reason it might've gone unnoticed is because it seems Not sure if this needs to be changed, but I'll keep this issue open in the meantime. |
It seems like |
Backport a patch from glslang to fix a build error KhronosGroup/glslang#1869 Signed-off-by: Khem Raj <raj.khem@gmail.com>
Backport a patch from glslang to fix a build error KhronosGroup/glslang#1869 Signed-off-by: Khem Raj <raj.khem@gmail.com>
Backport a patch from glslang to fix a build error KhronosGroup/glslang#1869 Signed-off-by: Khem Raj <raj.khem@gmail.com>
Backport a patch from glslang to fix a build error KhronosGroup/glslang#1869 Signed-off-by: Khem Raj <raj.khem@gmail.com>
Source: meta-openembedded MR: 00000 Type: Integration Disposition: Merged from meta-openembedded ChangeID: 13b8e3f Description: Backport a patch from glslang to fix a build error KhronosGroup/glslang#1869 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
For the clang issue, see: KhronosGroup/glslang#1869
Backport a patch from glslang to fix a build error KhronosGroup/glslang#1869 Signed-off-by: Khem Raj <raj.khem@gmail.com>
Backport a patch from glslang to fix a build error KhronosGroup/glslang#1869 Signed-off-by: Khem Raj <raj.khem@gmail.com>
It seems that
pool_allocator
is attempting to assign aTPoolAllocator
even though theTPoolAllocator
assignment operator is private.Something else that's also weird: It seems that
PoolAlloc.h
hasn't been touched since 2017, so I'm wondering how this went uncaught for a while.The text was updated successfully, but these errors were encountered: