You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 7895 Reporter:@db4 Status: acknowledged (set by @nojb on 2019-01-17T13:03:56Z) Resolution: open Priority: normal Severity: major Platform: Windows OS: 10 Version: 4.06.1 Category: platform support (windows, cross-compilation, etc) Monitored by:@nojb
Bug description
I'm trying to setup MSVC-compiled OCaml toolchain via OPAM 2.0. In my case it means that the compiler is built from sources in "C:\Users\dbely.opam\4.06.1+vc15+x86.opam-switch\build\ocaml-variants.4.06.1+win32" folder. During opt build "utils/strongly_connected_components.ml" is compiled and the following line is generated for MASM:
camlStrongly... identifier is 251 character long. It is too much for MASM (the limit is 247 chars) and it reports
camlasm00e3f6.asm(919) : error A2043:identifier too long
Maybe knowing that limitation OCaml compiler should not include the full source path into identifier names? For instance, maybe use md5 digests instead?
The text was updated successfully, but these errors were encountered:
Original bug ID: 7895
Reporter: @db4
Status: acknowledged (set by @nojb on 2019-01-17T13:03:56Z)
Resolution: open
Priority: normal
Severity: major
Platform: Windows
OS: 10
Version: 4.06.1
Category: platform support (windows, cross-compilation, etc)
Monitored by: @nojb
Bug description
I'm trying to setup MSVC-compiled OCaml toolchain via OPAM 2.0. In my case it means that the compiler is built from sources in "C:\Users\dbely.opam\4.06.1+vc15+x86.opam-switch\build\ocaml-variants.4.06.1+win32" folder. During opt build "utils/strongly_connected_components.ml" is compiled and the following line is generated for MASM:
camlStrongly... identifier is 251 character long. It is too much for MASM (the limit is 247 chars) and it reports
camlasm00e3f6.asm(919) : error A2043:identifier too long
Maybe knowing that limitation OCaml compiler should not include the full source path into identifier names? For instance, maybe use md5 digests instead?
The text was updated successfully, but these errors were encountered: