Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004957OCamlOCaml generalpublic2010-01-10 18:112014-09-04 00:25
Reportermatt 
Assigned To 
PrioritynormalSeverityminorReproducibilityalways
StatusacknowledgedResolutionopen 
PlatformOSOS Version
Product Version 
Target VersionundecidedFixed in Version 
Summary0004957: ocamlc -where, camlp4 -where, etc. add \r\n on mingw
DescriptionI may be wrong, but I would find it easier to use if the eol of the string returned by ocamlc -where etc. was \n, not \r\n

A lot of installers are broken or partially broken because of this.

Salutations.
TagsNo tags attached.
Attached Files

- Relationships

-  Notes
(0005226)
ygrek (reporter)
2010-01-11 11:07

Also keeping only forward slashes in these paths will make the life simpler. Currently there is the mix of forward and backslashes (msvc target).
(0006305)
matt (reporter)
2011-12-15 10:03

The problem is with mingw flavour of the distribution. Usually, it is used with "unix" tools (ocamlbuild, cygwin, …), while msvc flavour tend to use more "win" tools.

OCaml tools should be able to distinguish between msvc and mingw flavour, I would say, in order to adapt their ouptputs. I don't know if it is currently possible?

I'm aware of Sys.os_type. But it seems not enough detailed to me.
"Win32" is used both for mingw and MSVC.

Modifying Sys.os_type would break a lot of code. Maybe adding: Sys.os_flavour with more detailed information (mingw, msvc, unix, osx, …) would be a good first step?
(0006307)
ripoche (reporter)
2011-12-15 10:57

+1 for slashes in paths, even for msvc.
(0008041)
meyer (developer)
2012-09-10 05:09

I raise the severity to major as it breaks the installers. I think it would be sensible to expect from mingw port to return Unix style EOL delimiters.

However I think we don't expect it to fix it before 4.00.2, if you think it's a showstopper then please do let us know promptly, thanks.
(0008756)
frisch (developer)
2013-01-15 14:31

I'm not sure that the mingw and the msvc should behave differently. I understand that the current situation can break installers, but why is it specific to the mingw port? It makes perfect sense to use the msvc port even e.g. from Cygwin.

- Issue History
Date Modified Username Field Change
2010-01-10 18:11 matt New Issue
2010-01-11 11:07 ygrek Note Added: 0005226
2011-05-31 16:42 doligez Status new => acknowledged
2011-12-15 10:03 matt Note Added: 0006305
2011-12-15 10:57 ripoche Note Added: 0006307
2012-07-11 13:32 doligez Target Version => 4.01.0+dev
2012-07-31 13:36 doligez Target Version 4.01.0+dev => 4.00.1+dev
2012-09-10 05:09 meyer Note Added: 0008041
2012-09-10 05:09 meyer Severity minor => major
2012-09-10 05:09 meyer Target Version 4.00.1+dev => 4.00.2+dev
2013-01-15 14:31 frisch Note Added: 0008756
2013-06-06 23:08 frisch Severity major => minor
2013-06-06 23:08 frisch Target Version 4.00.2+dev => 4.02.0+dev
2013-07-12 18:15 doligez Target Version 4.02.0+dev => 4.01.1+dev
2014-05-25 20:20 doligez Target Version 4.01.1+dev => 4.02.0+dev
2014-07-31 15:59 doligez Target Version 4.02.0+dev => 4.02.1+dev
2014-09-04 00:25 doligez Target Version 4.02.1+dev => undecided


Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker