Re: Linking Opus with emcc

['Sam Clegg' via emscripten-discuss]

You are correct to remove LINKABL=1.   You can also remove WASM=1 (its the
default).

To debug your segfault you can try building and linking with
`-fsanitize=address' or one of the debugging methods.

cheers,
sam

On Wed, Jun 17, 2020 at 5:27 PM lukewarmtea137 
wrote:

> Additionally I've discovered that removing the -s LINKABLE=1 argument
> fixes this issue, however immeidatelly causes the page to crash when I run
> it (SIGSEGV), so I assume this is not the way to go about it.
>
> On Thursday, June 18, 2020 at 1:24:26 AM UTC+1, lukewarmtea137 wrote:
>>
>> Hi,
>> I've recently been trying to compile a small propgram to decode opus
>> frames, and so have attempted to link the opus library for this.
>> I managed to get the opus library configured using:
>> emconfigure ./configure EMCONFIGURE_JS=1 --disable-intrinsics --disable-rtcd
>> CFAGS='-02' --disable-asm --disable-oggtest --disable-extra-programs --prefix
>> ~/emscripten_opus
>>
>> And then I simply did:
>> emmake make && emmake install
>>
>> So I then had the include/lib/share files in the directory
>> ~/emscripten_opus.
>>
>> I then attempted to compile my small program (which at present doesn't
>> actually do anything - just makes the decoder using opus_decoder_create),
>> and I compiled it with:
>> emcc main.c -s WASM=1 -Iinclude/opus -lopus -L$HOME/emscripten_opus/lib -s
>> LINKABLE=1 -s EXTRA_EXPORTED_RUNTIME_METHODS='["cwrap", "ccall"]'
>>
>> And running this causes the following issues:
>> [parse exception: attempted pop from empty stack / beyond block start
>> boundary at 398161 (at 0:398161)]
>> Fatal: error in parsing input
>> emcc: error: '/home/user/emsdk/upstream/bin/wasm-emscripten-finalize
>> --detect-features --global-base=1024 --check-stack-overflow
>> /tmp/emscripten_temp_5cqqc8q2/a.out.wasm -o
>> /tmp/emscripten_temp_5cqqc8q2/a.out.wasm.o.wasm' failed (1)
>>
>> Does anyone have any idea what could be going wrong?
>>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/2a14d39d-ced8-435a-bde6-fa4a991130dbo%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CAL_va28VT0i_EZpbV0T9GvYWYSLxNw3GBNxFGLU_UBEmL2Rp4w%40mail.gmail.com.

Re: Linking Opus with emcc

[lukewarmtea137]

Additionally I've discovered that removing the -s LINKABLE=1 argument fixes 
this issue, however immeidatelly causes the page to crash when I run it 
(SIGSEGV), so I assume this is not the way to go about it.

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/017a0eac-dc7e-4add-a20b-ba4e61c04c10o%40googlegroups.com.

Re: Linking Opus with emcc

[lukewarmtea137]

Additionally I've discovered that removing the -s LINKABLE=1 argument fixes 
this issue, however immeidatelly causes the page to crash when I run it 
(SIGSEGV), so I assume this is not the way to go about it.

On Thursday, June 18, 2020 at 1:24:26 AM UTC+1, lukewarmtea137 wrote:
>
> Hi,
> I've recently been trying to compile a small propgram to decode opus 
> frames, and so have attempted to link the opus library for this.
> I managed to get the opus library configured using:
> emconfigure ./configure EMCONFIGURE_JS=1 --disable-intrinsics --disable-rtcd 
> CFAGS='-02' --disable-asm --disable-oggtest --disable-extra-programs --prefix 
> ~/emscripten_opus
>
> And then I simply did:
> emmake make && emmake install
>
> So I then had the include/lib/share files in the directory 
> ~/emscripten_opus.
>
> I then attempted to compile my small program (which at present doesn't 
> actually do anything - just makes the decoder using opus_decoder_create), 
> and I compiled it with:
> emcc main.c -s WASM=1 -Iinclude/opus -lopus -L$HOME/emscripten_opus/lib -s 
> LINKABLE=1 -s EXTRA_EXPORTED_RUNTIME_METHODS='["cwrap", "ccall"]'
>
> And running this causes the following issues:
> [parse exception: attempted pop from empty stack / beyond block start 
> boundary at 398161 (at 0:398161)]
> Fatal: error in parsing input
> emcc: error: '/home/user/emsdk/upstream/bin/wasm-emscripten-finalize 
> --detect-features --global-base=1024 --check-stack-overflow 
> /tmp/emscripten_temp_5cqqc8q2/a.out.wasm -o 
> /tmp/emscripten_temp_5cqqc8q2/a.out.wasm.o.wasm' failed (1)
>
> Does anyone have any idea what could be going wrong?
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/2a14d39d-ced8-435a-bde6-fa4a991130dbo%40googlegroups.com.

Linking Opus with emcc

[lukewarmtea137]

Hi,
I've recently been trying to compile a small propgram to decode opus 
frames, and so have attempted to link the opus library for this.
I managed to get the opus library configured using:
emconfigure ./configure EMCONFIGURE_JS=1 --disable-intrinsics --disable-rtcd 
CFAGS='-02' --disable-asm --disable-oggtest --disable-extra-programs --prefix 
~/emscripten_opus

And then I simply did:
emmake make && emmake install

So I then had the include/lib/share files in the directory 
~/emscripten_opus.

I then attempted to compile my small program (which at present doesn't 
actually do anything - just makes the decoder using opus_decoder_create), 
and I compiled it with:
emcc main.c -s WASM=1 -Iinclude/opus -lopus -L$HOME/emscripten_opus/lib -s 
LINKABLE=1 -s EXTRA_EXPORTED_RUNTIME_METHODS='["cwrap", "ccall"]'

And running this causes the following issues:
[parse exception: attempted pop from empty stack / beyond block start 
boundary at 398161 (at 0:398161)]
Fatal: error in parsing input
emcc: error: '/home/user/emsdk/upstream/bin/wasm-emscripten-finalize 
--detect-features --global-base=1024 --check-stack-overflow 
/tmp/emscripten_temp_5cqqc8q2/a.out.wasm -o 
/tmp/emscripten_temp_5cqqc8q2/a.out.wasm.o.wasm' failed (1)

Does anyone have any idea what could be going wrong?

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/cef7f052-0591-4d71-acc1-d46eb886166do%40googlegroups.com.

Re: Compiler error in Emscripten v1.39.18 -no member named 'acos' in the global namespace

['Sam Clegg' via emscripten-discuss]

I think this is related to the adding of `emscripten/math.h`.   Is your
build system adding `system/include/emscripten` to the include path?The
recommended fix would be remove this from your include path.   Hopefully
that isn't a problem for you.   If it is we could potentially rename this
`math.h` header.

On Wed, Jun 17, 2020 at 12:16 PM Brian Gavin  wrote:

> After doing some more testing the problem first appears when using version
> 1.39.16 of Emscripten
>
> Brian Gavin
>
> --
> You received this message because you are subscribed to the Google Groups
> "emscripten-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to emscripten-discuss+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/emscripten-discuss/0e0100bd-a0ba-4f74-9a40-48832bbdbce0o%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CAL_va29WMwrNLZEA4eS8zOibzo2WFmeuv695FLzmUS9H6_6r8A%40mail.gmail.com.

Re: Compiler error in Emscripten v1.39.18 -no member named 'acos' in the global namespace

[Brian Gavin]

After doing some more testing the problem first appears when using version 
1.39.16 of Emscripten

Brian Gavin

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/0e0100bd-a0ba-4f74-9a40-48832bbdbce0o%40googlegroups.com.

Compiler error in Emscripten v1.39.18 -no member named 'acos' in the global namespace

[Brian Gavin]

Hello,
When I tried to upgrade from Emscripten version 1.39.15 to 1.39.18.   I am 
now getting some compiler error related to things in the cmath file.   Is 
there a new flag I need to add or something similar?

emsdk\upstream\EMEA44~1\system\include\libcxx\cmath(338,9): error 
G1A4676F8: no member named 'acos' in the global namespace

Thanks,
Brian Gavin

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/a0833f49-cde5-4d4b-b2eb-1dd43e244360o%40googlegroups.com.

Re: Planning to remove fastcomp

[Alon Zakai]

Ok, looks like 2 weeks and no concerns here, so I think we are ready to
move forward on removing fastcomp.

I'll post in that issue with the concrete next steps, please follow there
if you're interested.

On Tue, Jun 2, 2020 at 4:03 PM Alon Zakai  wrote:

> Hi everyone,
>
> As the new upstream backend has been the default for a long time, we would
> like to start planning the removal of the old fastcomp backend. See full
> details of what that means here:
>
> https://github.com/emscripten-core/emscripten/issues/11319
>
> Please let us know if there are any concerns about this.
>
> - Alon
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"emscripten-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to emscripten-discuss+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpTp1rOGeXnFJHN3vLteC3EEOoaecttCPzyk0_S8oSXw0A%40mail.gmail.com.