I recently split up PATH into PATH and PATH_FS, where PATH_FS is the part that depends on FS being present. Sounds like that might have caused a bug somehow. If you build with -s VERBOSE=1 it should print the decisions it makes when adding symbols, and then it should say which ends up requiring PATH_FS. Then hopefully we can figure it out from there. (Or, if you can provide a testcase I can look at that directly.)
On Tue, May 7, 2019 at 10:01 PM Александр Гурьянов <[email protected]> wrote: > Hi guys! Just updated to latest incoming > (39158e5e344460d5c0a5da8913f87e4cb0db6e4a) and now have this error > that does not exists on previous version: > > error: undefined symbol: PATH_FS > warning: To disable errors for undefined symbols use `-s > ERROR_ON_UNDEFINED_SYMBOLS=0` > > Have no idea what is PATH_FS, and why it's not defined. I tried -s > FORCE_FILESYSTEM=1 but has no effect. > > Thanks. > > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/emscripten-discuss/CAKOm%3DVHeJFLrghSYHGD7ZoY8JKwK3c60ONXfryXUAFrjXO15fA%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/emscripten-discuss/CAEX4NpRNDsO51u85MMGrwz1zY28c6f-_zifwcUKKcEGuxQGddw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
