Invalid use of incomplete type vSIMDType
-
@d-healey Clanker found it for me:
HISE/hi_streaming/hi_streaming/MonolithAudioFormat.cppjuce::AudioFormatReader* HlacMonolithInfo::createUserInterfaceReader(int sampleIndex, int channelIndex, int64 realSampleLength) { if (isPositiveAndBelow(sampleIndex, sampleInfo.size())) { const auto& info = sampleInfo[sampleIndex]; const int64 start = info.start; // replace this (line 370): const int64 length = jmin<int64>(realSampleLength, info.length); // with this: const int64 length = std::min<int64>(realSampleLength, info.length); // or this: const int64 length = jmin((int64) realSampleLength, (int64) info.length); // rest of function } }@Christoph-Hart Simple fix above, not sure which version is better but the std::min one works for the latest Ubuntu LTS
-
-
@d-healey chatGPT lol
-
@iamlamprey said in Invalid use of incomplete type vSIMDType:
Clanker found it for me:
I think it's lying to you again. This is the line in my fork and it compiles without issue
-
@d-healey I'm not sure if it's lying necessarily, more likely there's multiple ways to skin a cat
Either way it worked on my end, tested on Ubuntu LTS and the latest Mint
-
@d-healey I think this is a Linux compiler thing. On Linux int64_t is defined as long int - whereas Windows and Mac it is defined as long long int.
The compiler is throwing a wobbly because of that.
I think.
-
@Orvillain said in Invalid use of incomplete type vSIMDType:
I think this is a Linux compiler thing.
Linux user here
-
@David-Healey said in Invalid use of incomplete type vSIMDType:
@Orvillain said in Invalid use of incomplete type vSIMDType:
I think this is a Linux compiler thing.
Linux user here
Yeah I know. You're getting the issue with the dev branch but not your fork right? Your error:
../../../../../hise/hi_streaming/../JUCE/modules/juce_dsp/containers/juce_SIMDRegister.h:85:11: error: invalid use of incomplete type ‘using juce::dsp::SIMDRegister<long long int>::NativeOps = struct juce::dsp::SIMDNativeOps<long long int>’ {aka ‘struct juce::dsp::SIMDNativeOps<long long int>’}That is telling you that SIMDRegister/SIMDNativeOps is being used incorrectly. The only thing I can think of is that it is being called with long long int, which is correct for Windows and Mac... but on Linux I think it should be called with long int - not long long int.
I'd check that line in your fork and dev branch and make sure it is the same, if you haven't already.
-
@Orvillain That line is in a JUCE module, we no touch those.
-
@David-Healey Well I don't know what else to tell you: https://forum.juce.com/t/int64-t-vs-juce-int64/45358
As reported here - it is a typedef issue, specifically affecting Linux compiles.
Actually, I might have that wrong. That thread is about juce:int_64.
-
@Orvillain That line is the same in my fork and in Christoph's so I don't think that's the cause