artifact_id;status_id;status_name;priority;submitter_id;submitter_name;assigned_to_id;assigned_to_name;open_date;close_date;last_modified_date;summary;details;"Due in version";"Product";"Operating System";"Component";"Version";"Severity";"Resolution";"URL" 690;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2010-07-24 09:48";"";"2010-07-24 09:48";"OASIS configure use setup.data";"For example, setup.data contains an old version of ocaml_version variable. ./configure runs 'ocamlc -config' but uses the predefined variable. $ ./configure --prefix ~/programmation/00build/ocaml-3.11.2-linux-amd64/ I: Running command '/usr/bin/ocamlc -config > /tmp/oasis-16c8c6.txt' W: Field 'ocaml_version_ge_3_11_0' is not set: Cannot satisfy version constraint on ocaml: >= 3.11.0 (version: 3.10.2) I: Running command '/usr/bin/ocamlfind query -format %d pcre > /tmp/oasis-a7d9bb.txt' E: OCaml version 3.10.2 doesn't match version constraint >= 3.11.0 E: 1 configuration error $ ocamlc -config version: 3.11.2 standard_library_default: /usr/lib/ocaml standard_library: /usr/lib/ocaml standard_runtime: /usr/bin/ocamlrun $ grep ocaml_version setup.data ocaml_version = ""3.10.2"" ocaml_version_ge_3_10_2 = ""3.10.2"" A simple distclean is enough to solve this error. ";"None";"OASIS";"None";"OASIS";"v0.1.0";"None";"None";"" 718;1;"Open";3;696;"Magnus Therning";102;"Sylvain Le Gall";"2010-08-21 23:20";"";"2010-08-24 10:35";"--prefix & --destdir aren't honoured by *all* things that are installed";"During my attempts of packaging OASIS and its dependencies for ArchLinux I basically performed the following steps: % ocaml ./setup.ml -configure --prefix /usr --destdir pkg_taging_dir % ocaml ./setup.ml -build % ocaml ./setup.ml -install Just to find that the destination dir I passed in at the configuration step wasn't honoured when the package included an ocaml library/module. In that case OASIS attempted to install the files in /usr/lib/ocaml/site-lib/. The expectation was that *exactly* the steps above would be all that's needed to stage a package using OASIS.";"None";"None";"None";"None";"None";"None";"None";"" 741;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-09-07 10:11";"";"2012-05-19 16:11";"OASIS puts full paths in setup.ml";"(* setup.ml generated for the first time by OASIS v0.2.0~alpha1 *) (* OASIS_START *) (* DO NOT EDIT (digest: 8313a40cd95c34db24e71587c1bf9e04) *) (* Regenerated by OASIS v0.2.0~alpha1 Visit http://oasis.forge.ocamlcore.org for more information and documentation about functions used in this file. *) module OASISGettext = struct # 21 ""/home/ygrek/work/contrib/oasis/src/oasis/OASISGettext.ml"" This is unfortunate cause different builds of OASIS (say different developers on different machines) will cause lots of meaningless changes when committing code. Solution: use paths relative to the oasis source directory or do not embed any paths at all. BTW the issue will still manifest itself if different OASIS versions are used in a single project";"0.2.1";"OASIS";"None";"OASIS";"v0.2.0";"normal";"Accepted As Bug";"" 742;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-09-08 09:56";"";"2010-09-10 14:57";"PreDistCleanCommand is not ""cumulative""";"i.e. after specifying several PreDistCleanCommand entries 'make distclean' will execute only the last one. The same goes for PostDistClean. And by the way it looks like both PreDistClean and PostDistClean are run _after_ actual distclean : $ cat _oasis |grep DistClean PreDistCleanCommand: $rm src/config.h PostDistCleanCommand: $rm src/config.ml $ OASIS setup [...] $ make distclean ocaml setup.ml -distclean I: Running command '/usr/bin/ocamlc.opt -config > /tmp/oasis-a29b67.txt' I: Running command '/usr/bin/ocamlbuild -clean -tag debug' Finished, 0 targets (0 cached) in 00:00:00. 00:00:00 0 (0 ) STARTING -------- |I: Remove '/home/ygrek/work/local/extunix/setup.log' I: Running command 'rm -f src/config.h' I: Running command 'rm -f src/config.ml' Removing setup.log is part of distclean, and my predistclean is run after it. And one more minor nitpick : generate Makefile has target for setup.dat and '.PHONY: configure' but no target for configure - is it ok?";"None";"OASIS";"None";"OASIS";"v0.2.0";"normal";"None";"" 755;1;"Open";3;227;"Kaustuv Chaudhuri";102;"Sylvain Le Gall";"2010-09-21 14:58";"";"2010-09-22 15:27";"Installer claims LGPL needs to be accepted";"The LGPL does not need to accepted to be applicable to all recipients. Therefore, it is false to have language to the effect that ""you need to accept the [LGPL] in order to proceed"". I don't think the LE changes this.";"None";"OASIS";"All";"OASIS";"v0.1.0";"trivial";"None";"" 756;1;"Open";3;227;"Kaustuv Chaudhuri";102;"Sylvain Le Gall";"2010-09-21 15:00";"";"2010-09-22 15:28";"Installer creates bin/OASIS.sh, contrary to docs";"The documentation such as the quickstart page says that the command is OASIS, but the installer actually creates ${prefix}/bin/OASIS.sh.";"None";"OASIS";"Linux";"General";"v0.1.0";"normal";"None";"" 757;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-09-22 15:11";"";"2012-05-23 17:22";"ocamlmktop needs -linkpkg";"Consider the patch below, it doesn't solve all the problems (e.g. path to local stubs) but it definitely makes life easier : --- myocamlbuild.ml 2010-09-22 18:06:54.000000000 +0300 +++ myocamlbuild.ml.ba1 2010-09-22 18:07:46.000000000 +0300 @@ -275,8 +275,9 @@ | After_rules -> - (* When one link an OCaml library/binary/package, one should use -linkpkg *) + (* When link produces an OCaml program/toplevel, one should use -linkpkg *) flag [""ocaml""; ""link""; ""program""] & A""-linkpkg""; + flag [""ocaml""; ""link""; ""toplevel""] & A""-linkpkg""; (* For each ocamlfind package one inject the -package option when * compiling, computing dependencies, generating documentation and ";"0.2.1";"OASIS";"None";"Plugin OCamlbuild";"v0.2.0";"normal";"Accepted As Bug";"" 758;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-09-22 15:59";"";"2010-09-22 16:19";"`make uninstall` doesn't work after `make distclean`";"$ cat > _oasis OASISFormat: 0.1 Name: test Version: 0.0.1 Synopsis: test Authors: me License: BSD3 Plugins: DevFiles, META BuildTools: ocamlbuild Library test Path: . Modules: Test $ cat > test.ml let test = print_endline $ OASIS setup [...] $ ./configure [...] $ make install ocaml setup.ml -install W: Nothing to install for findlib library 'test' $ ocamlfind list | grep test $ make && make install && make distclean [...] $ ocamlfind list | grep test test (version: 0.0.1) $ make uninstall ocaml setup.ml -uninstall $ ocamlfind list | grep test test (version: 0.0.1) i.e. make uninstall doesn't remove the library. (Note that install target doesn't depend on build target - this is probably not a bug but a feature wish) ";"None";"OASIS";"None";"OASIS";"v0.2.0";"normal";"Awaiting Response";"" 776;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2010-10-21 12:23";"";"2010-10-21 12:23";"Warn about plugin not able, when the plugin is not up to date";"W: Plugin ocamlbuild (0.1.0) doesn't match the latest version of this plugin. Please check plugin's changelog and upgrade to the latest version 0.2. W: Field XOCamlbuildLibraries is set but matching plugin is not enabled";"0.2.1";"OASIS";"None";"General";"v0.2.0";"None";"None";"" 779;1;"Open";3;224;"Pierre Chambart";102;"Sylvain Le Gall";"2010-10-22 08:30";"";"2010-10-22 09:05";"install/reinstall doesn't work when installation log unavailable. ";"This can happen when you installed a library using a downloaded .tar.gz and you want to install the darcs version for instance, and you removed the old directory. The problem is that ocamlfind doesn't allow to replace the old version. In case it happens, setup.ml should run ""ocamlfind remove"" and then retry ""ocamlfind install"".";"None";"OASIS";"All";"None";"v0.2.0";"minor";"None";"" 784;1;"Open";3;105;"Paolo Donadeo";102;"Sylvain Le Gall";"2010-10-22 22:10";"";"2012-07-06 08:34";"Oasis exits while loading libpcre.so.0";"I just installed OASIS 0.2.0 using the installer for Linux. The installation ran as expected and installed everything under /usr/local/oasis-0.2.0/*. When, from the shell, I invoke oasis, it exits complaining about a library. This is the transcript: paolo@atreides ~ ~ $ oasis /usr/local/oasis-0.2.0/bin/../libexec/oasis: error while loading shared libraries: libpcre.so.0: cannot open shared object file: No such file or directory It's actually true that on my system libpcre.so.0 is not present, but a /lib/libpcre.so.3 is present and it's a symlink to /lib/libpcre.so.3.12.1, as usual. I'm running on a Ubuntu 10.04.1 LTS, 64bit, and the libpcre installed is the default one for this architecture: libpcre3_7.8-3build1_amd64.deb The usual fix of creating a symlink works: # cd /lib # ln -s libpcre.so.3.12.1 libpcre.so.0 # cd lib32 # ln -s libpcre.so.3.12.1 libpcre.so.0 # ldconfig -v ";"0.2.1";"OASIS";"Linux";"OASIS";"v0.2.0";"blocker";"Fixed";"" 786;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-10-25 09:16";"";"2010-10-25 10:03";"comma character cannot be used in copyright field";"It is treated as separator";"None";"OASIS";"None";"OASIS";"v0.2.0";"minor";"None";"" 795;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2010-11-02 17:11";"";"2010-11-02 17:11";"Warning with certains plugin field in section";"For example, Using XMETAType: syntax, trigger a warning.";"0.2.1";"OASIS";"None";"OASIS";"v0.2.0";"minor";"Accepted As Bug";"" 798;1;"Open";3;172;"Mauricio Fernandez";102;"Sylvain Le Gall";"2010-11-02 19:43";"";"2010-11-02 21:14";"Information given by ""oasis manual"" ";"The documentation given by ""oasis manual"" is very extensive, leading the first time user to believe it represents all the available documentation there is. I think it'd be good to point to the info available on the web site. In particular, sample _oasis files could be included in the output from ""oasis manual"", or even promoted to a separate command such as ""oasis examples"", making it very easy to cut & paste into a new _oasis file. ";"None";"None";"All";"OASIS";"v0.2.0";"enhancement";"Accepted As Bug";"" 813;1;"Open";3;800;"A. G.";102;"Sylvain Le Gall";"2010-11-23 14:30";"";"2010-12-01 12:45";"Improved documentation";"When you start with oasis.exe quickstart, it is written on the web site to use the command oasis.exe -quickstart, but instead you have to type oasis.exe quickstart (no dash). Then a list of modules is asked, but the format is not given. It would be better to have something like: Give the list of ocaml Modules separated with comas. (so that we know what character to use to separate modules). Also a reminder that ocaml Modules should start with a capital letter wouldn't hurt (:-) Since there are internal and external modules, it is nice to alert the user that a list of internal modules will be asked later, and that for the time being only public modules are needed. Finally, (but I haven't checked it in the documentation yet), the tool assumes that ocaml is installed in a directory without any white space in the path. (especially for windows users, do not install ocaml in C:\Program Files). Maybe I should open another bug for this ? ";"None";"None";"Windows XP";"None";"v0.2.0";"None";"None";"" 828;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-12-14 12:57";"";"2010-12-14 13:23";"link to bug reports points to 'add' which is not abailable for anonymous users";"I think it is bettter to point to 'browse' so that anonymous users can view submitted bugs";"None";"OASIS";"None";"Website";"None";"None";"Accepted As Bug";"" 829;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-12-14 13:01";"";"2010-12-14 13:29";"Ctrl-C interrupt uninstall -> corrupt setup.log";"Pressing Ctrl-C during uninstall leads to half-written line in setup.log and at the next invocation setup.ml complains : E: Malformed log file '.../setup.log' at line 254 Better write to temporary file and rename to setup.log when finished.";"None";"OASIS";"Linux";"OASIS";"v0.2.0";"normal";"None";"" 830;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-12-15 10:33";"";"2010-12-17 12:31";"'$rm path/file' doesn't work on windows";"Here is the corresponding log - from http://build.ygrek.org.ua/hudson/job/extunix/label=qemu-i386-win2k,ocaml=default/78/console : + ocaml setup.ml -distclean I: Running command 'C:\prog\ocaml-3.11.0-mingw\bin\ocamlc.opt.EXE -config > .\oasis-f7c740.txt' I: Running command 'C:\prog\ocaml-3.11.0-mingw\bin\ocamlbuild.EXE -classic-display -no-log -no-links -install-lib-dir C:\prog\ocaml-3.11.0-mingw\lib\ocamlbuild -byte-plugin -clean -tag debug' mkdir _build + mkdir _build rm -Rf _build + rm -Rf _build I: Remove 'C:\hudson\workspace\extunix\label\qemu-i386-win2k\ocaml\default\setup.log' I: Running command 'del src/config.h' Invalid switch - ""config.h"". W: Command '$rm src/config.h' fail with error: Command 'del src/config.h' terminated with error code 1 I: Running command 'del src/config.ml' Invalid switch - ""config.ml"". W: Command '$rm src/config.ml' fail with error: Command 'del src/config.ml' terminated with error code 1 So either everybody should use utoh macro when using $rm (this won't happen) or $rm should implicitly convert paths or oasis should implement $rm with Sys.remove which perfectly accepts forward slashes on windows.";"None";"OASIS";"Windows XP";"Base";"v0.2.0";"normal";"Accepted As Bug";"" 832;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2010-12-16 11:49";"";"2010-12-16 11:49";"No check of findlib package name";" Even if they are "" "" in findlib package name, oasis don't fail. For example: Library ""rest-ocsigen"" FindlibParent: rest FindlibName: ocsigen Path: src/rest/ocsigen Modules: RESTOcsigen BuildDepends: rest, ocsigen markdown, markdown.html, threads ""ocsigen markdown"" is not a package and it generates an error in _tags Lexical analysis error: Bad key in configuration line at line 32 (from file: ""_tags"") Because of the blank.";"None";"OASIS";"All";"Plugin OCamlbuild";"v0.2.0";"minor";"Accepted As Bug";"" 834;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2010-12-21 20:28";"";"2010-12-23 09:20";"bytecode test targets with C stubs cannot find needed .so";"This is a well known issue, the solution is to either : 1) install library prior to running tests 2) set the CAML_LD_LIBRARY_PATH when running tests 3) use -dllpath at compilation time 4) compile bytecode binaries with -custom Ruling out options requiring user intervention (1) or compilation changes (3) and (4) we are left with option (2), i.e. `ocaml setup.ml -test` should setup CAML_LD_LIBRARY_PATH. The users who want to launch bytecode binaries ""manually"" can still install library or switch to custom compilation.";"None";"OASIS";"None";"OASIS";"v0.2.0";"normal";"None";"http://build.ygrek.org.ua/hudson/job/extunix/label=qemu-armel-debian,ocaml=default/82/console" 863;1;"Open";3;824;"Török Edwin";102;"Sylvain Le Gall";"2011-01-06 10:53";"";"2011-01-31 09:37";"oasis: some changes only take effect if setup.data is removed, even if configure is rerun";"If I set 'profile', or 'debug' environment variables, they don't take effect even if I rerun configure. Only removing setup.data (or make distclean) followed by a configure rerun changes it. I think there are more things that configure caches inappropriately, for example ocamlfind results (package presence and version). Here is a testcase for the env vars: OASISFormat: 0.2 Name: configure testcase Version: 0.1 Synopsis: bug testcase Plugins: DevFiles (0.2), StdFiles (0.2) License: GPL-2.0 Authors: Török Edwin BuildTools: ocamlbuild, make $ oasis setup $ ./configure ... Compile with ocaml debug flag on.: ............. true ... $ export debug=false; ./configure ... Compile with ocaml debug flag on.: ............. true ... $ rm setup.data; ./configure ... Compile with ocaml debug flag on.: ............. false ....";"None";"OASIS";"Linux";"None";"v0.2.0";"None";"None";"" 865;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2011-01-07 17:12";"";"2011-01-31 09:37";"`BuildTools: g++` results in broken setup.data";"_oasis: ... BuildTools: ocamlbuild, g++ ... $ oasis setup $ ./configure Configuration: ocamldoc: ...................................... /usr/bin/ocamldoc g++: ........................................... /usr/bin/g++ [...] E: Malformed data file '/home/ygrek/work/local/hypertable/setup.data' line 51 $ sed -n 51p setup.data g++ = ""/usr/bin/g++"" ";"None";"OASIS";"None";"OASIS";"v0.2.0";"normal";"None";"http://hypertable.forge.ocamlcore.org" 925;1;"Open";3;142;"Edgar Friendly";102;"Sylvain Le Gall";"2011-03-07 22:15";"";"2011-03-07 22:30";"Restrict package names";"Package names probably don't need to contain most special symbols, and allowing this can cause security problems in sloppily coded programs (including odb.ml). Let's restrict package names to something more like [-a-zA-Z0-9]+";"0.3.0";"OASIS";"None";"General";"None";"minor";"None";"" 935;1;"Open";3;835;"Joel Reymont";102;"Sylvain Le Gall";"2011-03-28 11:01";"";"2011-07-25 17:09";"Symbolic links created for only the first executable built";"When defining multiple executables in the _oasis file, only the first one is symlinked to the project directory from _build/_src. I would expect all the executables to be symlinked. ";"0.3.0";"OASIS";"MacOS X";"Plugin OCamlbuild";"v0.2.0";"None";"None";"" 940;1;"Open";3;889;"Roma Sokolov";102;"Sylvain Le Gall";"2011-03-31 20:02";"";"2011-04-04 07:56";"Oasis ignores XCustom fields";"ocaml batteries has custom build system. There are XCustomConf, XCustomInstall and XCustomUninstall fields in _oasis. But oasis setup doesn't generate right setup.ml for these fields: BaseSetup.configure = InternalConfigurePlugin.configure; install = InternalInstallPlugin.install; uninstall = InternalInstallPlugin.uninstall; only XCustomBuild from XCustomXXX fields handles by oasis. ";"0.2.1";"OASIS";"All";"Plugin Custom";"v0.2.0";"minor";"Accepted As Bug";"https://github.com/ocaml-batteries-team/batteries-included/blob/master/_oasis" 942;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2011-04-02 09:33";"";"2011-04-02 09:33";"Target all don't take into account built executable (make all or ocaml setup.ml -all)";"The tarball attached reproduce this bug. The output is: [...] I: Running build step E: Field 'test' is not set: Executable 'test' not yet built. ";"0.2.1";"OASIS";"None";"General";"v0.2.0";"major";"Accepted As Bug";"" 953;1;"Open";3;144;"Christophe Troestler";102;"Sylvain Le Gall";"2011-04-17 20:57";"";"2011-05-05 12:48";"Improve error of META already existing";"When one has two simple Library sections and one uses the plugin META, ""oasis setup"" reports that E: OASISFileTemplate.AlreadyExists(""./META"") which may surprise a beginner. A more complete error message pointing to a possible solution would be nice. Example: E: OASISFileTemplate.AlreadyExists(""./META""). If you have several Library section, did you forget to specify FindlibParent to indicate the one that is a child ?";"None";"OASIS";"All";"Plugin META";"v0.2.0";"enhancement";"None";"" 963;1;"Open";3;144;"Christophe Troestler";102;"Sylvain Le Gall";"2011-05-05 11:41";"";"2011-05-28 13:52";"Symbolic links for executables";"OASIS (with the ocamlbuild plugin) creates a symbolic link for the first executable. If there are more than one executable, there should be symbolic links for all or none of them.";"None";"OASIS";"All";"Plugin OCamlbuild";"v0.2.0";"minor";"None";"" 975;1;"Open";3;142;"Edgar Friendly";102;"Sylvain Le Gall";"2011-05-24 15:39";"";"2012-03-12 22:14";"Dependencies aren't tracker per repo in admin/odb page";"When I promote a package from unstable to testing, if its deps aren't in testing, I should get a dep error.";"None";"OASIS-DB";"None";"None";"None";"None";"None";"http://oasis.ocamlcore.org/dev/admin/odb" 979;1;"Open";3;205;"Daniel Bünzli";102;"Sylvain Le Gall";"2011-05-27 15:49";"";"2012-03-12 22:14";"oasis-db, public link is unclear ";"In the upload form it is unclear what ""Public link"" is. A better wording would be ""Public http link to tarball"". Better yet, we could just provide the public link and oasis-db could download it from there (instead of uploading). Best, Daniel ";"None";"None";"None";"None";"None";"None";"None";"" 981;1;"Open";3;144;"Christophe Troestler";102;"Sylvain Le Gall";"2011-05-28 12:34";"";"2012-03-12 22:14";"'ocaml setup.ml -reinstall' should not remove '/usr/local/share/doc'";"When running 'ocaml setup.ml -reinstall', oasis tries to 'rm -r '/usr/local/share/doc''. I believe this is wrong as this directory will also contain the documentation of other packages. It should only remove the dir usr/local/share/doc/. My _oasis setting is the usual one; InstallDir: $docdir/api ";"None";"OASIS";"All";"OASIS";"v0.2.0";"major";"None";"" 990;1;"Open";3;925;"Alexis Bernadet";102;"Sylvain Le Gall";"2011-06-07 12:12";"";"2012-03-12 22:14";"Problem with generated C headers";"In my project I need to generate C header files with an internal tool that uses C stub To illustrate this problem/bug/feature request I have made a simple example : The _oasis file describes a project as follow : There are two executables : Executable gen_header Path: . MainIs: gen_header.ml Install: false Custom: true CSources: add.c Executable test_header Path: . MainIs: test_header.ml BuildTools: gen_header Custom: true CSources: myconst.c, generated_header.h generated_header.h is produced by the executable gen_header. So I naturally add a rule in myocamlbuild.ml. The problem is that for building gen_header, it tries to build gen_header.h : so we naturally have an error message. /bin/sh: ./gen_header: not found We can notice that if we work with generated_header.c instead of generated header.h there is no problem. The only solution I have found to go around this problem is to : - remove generated_header.h in the _oasis file - add dep [""file:myconst.c""] [""generated_header.h""] in the myocamlbuild.ml file ";"None";"OASIS";"All";"Plugin OCamlbuild";"v0.2.0";"normal";"None";"" 993;1;"Open";3;142;"Edgar Friendly";102;"Sylvain Le Gall";"2011-06-09 18:29";"";"2012-03-12 22:14";"Failure uploading tarball";"The following tarball errored out on upload. I set the following values: Tarball: ocamlviz-r428.tar.gz Has _oasis file: false Public link: Package: ocamlviz Version: 0.0-r428 Order: 0 and then confirmed the upload. The result was: Unmanaged error, retry later and contact system administrator if it happens again. ";"None";"None";"None";"None";"None";"None";"None";"http://oasis.ocamlcore.org/dev/upload?id=15" 1008;1;"Open";3;112;"Hezekiah Carty";102;"Sylvain Le Gall";"2011-07-10 20:40";"";"2011-11-14 23:34";"Compilation flags in ByteOpt and NativeOpt are not applied to .c files";"For example: ... CSources: foo.c ByteOpt: -cc fake-gcc ... will not use fake-gcc to compile foo.c.";"0.2.1";"OASIS";"None";"OASIS";"v0.2.0";"normal";"None";"" 1011;1;"Open";3;738;"Romain Slootmaekers";102;"Sylvain Le Gall";"2011-07-13 16:41";"";"2012-03-12 22:14";"oasis-0.2.0-linux-installer.bin does not work on particular environment";"$> md5sum ./oasis-0.2.0-linux-installer.bin b72e9400ecbe362b5528783cbdab4a31 ./oasis-0.2.0-linux-installer.bin $> ls -alh ./oasis-0.2.0-linux-installer.bin ls -alh ./oasis-0.2.0-linux-installer.bin -rwxr--r-- 1 xxx xxx 5.2M 2011-07-13 18:29 ./oasis-0.2.0-linux-installer.bin $> ./oasis-0.2.0-linux-installer.bin: No such file or directory $> uname -a Linux lucid 2.6.32-21-server #32-Ubuntu SMP Fri Apr 16 09:17:34 UTC 2010 x86_64 GNU/Linux this particular machine is a virtual machine and the Ubuntu install has no X (don't know if that has anything to do with it.) ";"None";"None";"Linux";"OASIS";"v0.2.0";"None";"None";"" 1021;1;"Open";3;1020;"Andrew Psaltis";102;"Sylvain Le Gall";"2011-07-31 23:25";"";"2012-03-12 22:14";"Installation of localization does not honor DESTDIR";"Attempting to package oasis including localization results in the localization being installed to the file system root, not relative to the DESTDIR. This could be fixed by prefixing PODIR with $destdir within the localization Makefile.";"None";"OASIS";"None";"OASIS";"None";"minor";"None";"" 1027;1;"Open";3;1499;"Phil Hagelberg";102;"Sylvain Le Gall";"2011-08-09 19:42";"";"2012-03-12 22:14";"oasis-0.2.0-linux-installer.bin crashes with segmentation fault";"This is on a 64-bit Ubuntu 11.04 with ia32-libs. $ ./oasis-0.2.0-linux-installer.bin Segmentation fault I saw a similar bug report recommended running strace, so I've attached that output.";"None";"OASIS";"Linux";"General";"None";"None";"None";"" 1043;1;"Open";3;889;"Roma Sokolov";102;"Sylvain Le Gall";"2011-10-02 21:38";"";"2012-03-12 22:14";"Warning about disabled plugin, when it enabled.";"Oasis 0.2.1~alpha1 and _oasis file from https://forge.ocamlcore.org/anonscm/hg/type-conv/ produce following warning, when running oasis setup, or oasis setup-dev: W: Field XMETAType is set but matching plugin is not enabled. although META plugin is enabled. If I change XMETAType from 'syntax' to 'library', this warning vanishes. ";"None";"OASIS";"None";"Plugin META";"v0.2.0";"None";"None";"" 1044;1;"Open";3;889;"Roma Sokolov";102;"Sylvain Le Gall";"2011-10-02 21:42";"";"2012-03-12 22:12";"setup.ml in distribution files generated with old oasis";"Incorrect calculation of ocaml version has been already reported and fixed ( see [#888] ), but oasis archives on ocaml forge still contain setup.ml files, generated with old oasis. Then it's impossible to install oasis with dev version of ocaml without manual fixes. It will be good to regenerate setup.ml and corresponding files in distribution archives.";"None";"OASIS";"None";"OASIS";"None";"None";"None";"" 1050;1;"Open";3;294;"Philippe Veber";102;"Sylvain Le Gall";"2011-11-02 10:29";"";"2012-03-12 22:14";"Dependency on a library that is a syntax extension.";"Let's say we define a package with a library A that is a syntax extension, and another component B (library or executable) that depends on A. It is currently not possible to use the syntax extension A in B: the compilation of B fails at ocamldep stage, because the appropriate options are not set. In contrast, if A were a regular library, there would be no problem to use it in B. A workaround found in the LWT package (which offers several syntax extensions) is to modify myocamlbuild.ml manually (of course after the generated part so that it is kept between calls to oasis setup). Here is how I got it working (not sure this is a minimal solution, however), by adapting the ocamlbuild plugin found in LWT: open Ocamlbuild_plugin let () = dispatch (fun hook -> dispatch_default hook; match hook with | Before_options -> Options.make_links := false | After_rules -> (* Internal syntax extension *) List.iter (fun base -> let tag = ""pa_"" ^ base and file = ""src/syntax/pa_"" ^ base ^ "".cmo"" in flag [""ocaml""; ""compile""; tag] & S[A""-ppopt""; A file]; flag [""ocaml""; ""ocamldep""; tag] & S[A""-ppopt""; A file]; flag [""ocaml""; ""doc""; tag] & S[A""-ppopt""; A file]; dep [""ocaml""; ""ocamldep""; tag] [file]) [""syntax_ext1"";""syntax_ext2""]; (* add your syntax extensions here *) | _ -> ()) ";"None";"OASIS";"All";"OASIS";"v0.2.0";"enhancement";"None";"" 1061;1;"Open";3;3195;"Tom Prince";102;"Sylvain Le Gall";"2011-11-23 22:43";"";"2011-11-23 22:56";" output a warning when 2 files separated by space exists whereas one file with space in it doesn't exist";"e.g. W: file ""pycaml_stubs.c pycaml.h"" doesn't exist but ""pycaml_stubs.c"" and ""pycaml.h"" exists, maybe you should write ""pycaml_stubs.c, pycaml.h"" adrien | and maybe more generally warn about spaces in filenames?";"0.2.1";"OASIS";"None";"None";"None";"enhancement";"Accepted As Bug";"" 1063;1;"Open";3;3201;"Dmitry Astapov";102;"Sylvain Le Gall";"2011-11-24 09:49";"";"2012-03-12 22:14";"Generated setup.ml has unused variables";"Hi! I just tried to install several packages in the environment where ""ocaml"" by default has non-empty value of -warn-error and found out that every ""setup.ml"" generated by OASIS 0.2.0 fails to load with ""unused variable context"": % ocaml setup.ml -configure File ""/home/ante/Documents/dev/sharedprojects/ocaml/oasis/src/oasis/PropList.ml"", line 235, characters 18-26: Warning 27: unused variable context. File ""setup.ml"", line 1, characters 0-1: (note that filename here comes from line no. directives in setup.ml and does not correspond to actual file on my local box) To reproduce with vanilla ocaml: ocaml -w +27 -warn-error +27 setup.ml -configure To get the list of offending unused variables: ocaml -w +27 setup.ml -configure";"0.2.1";"OASIS";"All";"None";"v0.2.0";"None";"None";"" 1077;1;"Open";3;294;"Philippe Veber";102;"Sylvain Le Gall";"2012-01-06 12:24";"";"2012-03-12 22:14";"Bug in dependency calculations with flags";"The issue was described in relation to odb, please see the following bug report: https://github.com/thelema/odb/issues/27#issuecomment-3381970 It currently affects the ocaml-data-notation package in odb, whose installation fails if oUnit and fileutils are not previously installed. The oasis web service does not report dependencies on this packages to odb, causes the problem. ";"None";"None";"None";"None";"v0.2.0";"None";"None";"" 1078;1;"Open";3;4175;"Francois Berenger";102;"Sylvain Le Gall";"2012-01-11 02:31";"";"2012-03-12 22:14";"The OCaml Bioinformatics Library";"_THE_ library for bioinformatics applications written in OCaml. ;) ";"None";"OASIS";"Linux";"OASIS";"None";"None";"None";"http://biocaml.org/" 1089;1;"Open";3;294;"Philippe Veber";102;"Sylvain Le Gall";"2012-01-27 15:34";"";"2012-03-12 22:14";"Leading dot in library path value prevents compilation";"In the attached archive is a skeleton project for a C binding, which fails to compile if it is described in the _oasis file by: Library binding Path: ./src BuildTools: ocamlbuild Modules: Binding CSources: binding_stub.c Ocamlbuild fails to compile the project, but removing the leading ""./"" in the Path field fixes the problem. Steps to reproduce: - un tar.gz the archive - build by typing make (there should be an ocamlbuild error) - remove the ""./"" in the Path field of the ""binding"" library section - build (there should be no error anymore) ";"0.2.1";"OASIS";"None";"OASIS";"v0.2.0";"normal";"None";"" 1091;1;"Open";3;142;"Edgar Friendly";102;"Sylvain Le Gall";"2012-02-02 17:27";"";"2012-03-12 22:14";"Qtest from oasis";"Batteries new quicktest infrastructure is being built to be used in external projects - it'd be great to have this be trivial to turn on in an OASIS project, probably with a qtest plugin";"None";"OASIS";"None";"OASIS";"None";"None";"None";"" 1111;1;"Open";3;205;"Daniel Bünzli";102;"Sylvain Le Gall";"2012-03-08 14:41";"";"2012-03-12 22:14";"Static Document section";"A Document section as follows Document xmlm Title: ""Xmlm documentation and module reference"" Format: html Index: Xmlm.html Install: true InstallDir: $htmldir/xmlm DataFiles: README CHANGES doc/*.html, doc/*.css doesn't do anything. Apparently Sylvain thinks it should. Best, Daniel";"None";"None";"None";"None";"None";"None";"None";"" 1115;1;"Open";3;146;"Gabriel Scherer";102;"Sylvain Le Gall";"2012-03-13 13:08";"";"2012-07-06 08:33";"Provide a clear error message when `setup.ml` are not done in order (-configure missing)";"After ""oasis setup"", if I use ""ocaml setup.ml -build"", I get the following error message: E: Unable to load environment, the file '...../setup.data' doesn't exist. It would be nice if this error message was followed by something more useful for the user, such as You probably need to run ""ocaml setup.ml -configure"" first I have the same error if I try ""ocaml setup.ml -install"" first. However, if I first -configure then -install, I get: W: Nothing to install for findlib library '....' Maybe it would be possible to also give notice that maybe the ""-build"" step is missing in this case? I suspect that is less important (one often forget to -configure, assuming that there will be a default configuration, but forgetting to -build is less obvious...). It's strange that oasis does not notice that something is wrong in the -install case (where are the compiled files for the module?) and just outputs a warning and consider installation complete. ";"None";"OASIS";"None";"OASIS";"None";"enhancement";"None";"" 1116;1;"Open";3;146;"Gabriel Scherer";102;"Sylvain Le Gall";"2012-03-13 14:59";"";"2012-10-11 12:14";"oasis documentation unclear: does Library sections handle ocamldoc? Does XCustomDoc exist?";"The manual for the Library sections say: > Define an OCaml library. OCaml API is generated using ocamldoc > applied to Modules with BuildDepends required flags. Reading this, I would expect ""ocaml setup.ml -doc"" to generate ocamldoc for the Modules. However, ""ocaml setup.ml -doc"" has no effect on my system. Is this a bug? I had to add a specific Document section to get ocamldoc output. The documentation of the Custom plugin says: > This plugin allow to define a set of three commands to perform each steps, associated with the following fields: > XCustomXXX: main action to run. > XCustomXXXClean: action to run when clean is invoked. > XCustomXXXDistclean: action to run when distclean is invoked. > XXX stands for Conf, Build, Doc, Test, Install or Uninstall. However, XCustomDoc (or XCustomDocClean for that matter) do not seem to exist (... is not defined in schema Package). Can XXX really stand for Doc? ";"None";"OASIS";"None";"Website";"None";"minor";"None";"" 1125;1;"Open";3;437;"Florent Monnier";102;"Sylvain Le Gall";"2012-03-25 00:12";"";"2012-07-06 08:33";"setup.ml -configure --prefix is sometimes ignored";"In the package ocamlify-0.0.1 this process does work as expected: ocaml setup.ml -configure --prefix /tmp/my_custom_path ocaml setup.ml -build mkdir -p /tmp/my_custom_path ocaml setup.ml -install tree -fi /tmp/my_custom_path ## everything is there in the prefix path as expected but in uuidm-0.9.4 : ocaml setup.ml -configure --prefix /tmp/my_temp_lib ocaml setup.ml -build mkdir -p /tmp/my_temp_lib ocaml setup.ml -install tree -fi /tmp/my_temp_lib ## the install command still tries to install in /usr/lib/ocaml/uuidm instead of inside the prefix /tmp/my_temp_lib/usr/lib/ocaml/uuidm";"None";"None";"None";"None";"None";"None";"None";"" 1128;1;"Open";3;214;"Goswin Brederlow, von";102;"Sylvain Le Gall";"2012-03-26 11:45";"";"2012-07-06 08:33";"E: OASISFileTemplate.AlreadyExists(""src/META"") when building two libraries in the same dir";"When specifying two toplevel libraries in _oasis one gets a cryptic error message: Library extunix Path: src/ Modules: ExtUnix InternalModules: ExtUnixAll, ExtUnixSpecific if flag(strict) && ccomp_type(cc) CCOpt: -std=c89 -pedantic -Wno-long-long CSources: config.h, eventfd.c, dirfd.c, fsync.c, statvfs.c, atfile.c, ioctl_siocgifconf.c, uname.c, fadvise.c, fallocate.c, tty_ioctl.c, unistd.c, stdlib.c, signalfd.c, ptrace.c, resource.c, mman.c, time.c, pts.c, execinfo.c, malloc.c, endian.c BuildDepends: unix Library extunixba Path: src Modules: ExtUnixBA InternalModules: ExtUnixBAAll, ExtUnixBASpecific if flag(strict) && ccomp_type(cc) CCOpt: -std=c89 -pedantic -Wno-long-long CSources: config.h, memalign.c BuildDepends: unix, bigarray # FindlibParent: extunix # FindlibName: bigarray % oasis setup E: OASISFileTemplate.AlreadyExists(""src/META"") The problem was the missing FindlibParent/FindlibName so both libraries wanted their own src/META file instead of one being a sub-module of the other. The error message could say that it has multiple libraries trying to build the same file and hint that FindlibParent/FindlibName might be missing. ";"None";"None";"None";"None";"None";"None";"None";"" 1136;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2012-04-03 23:57";"";"2012-04-03 23:57";"oasis-db report that a non-installed exec is optionnaly provided.";"In the document pointed by the URL, it is said: Provide Tools: test (opt.), oasis But test is set to Install: false";"None";"OASIS-DB";"None";"None";"None";"None";"None";"http://oasis.ocamlcore.org/dev/view/oasis/0.3.0~rc3" 1143;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2012-04-24 22:09";"";"2012-04-24 22:09";"ocaml setup.ml -configure doesn't take into account a change in the version number";"In general -configure doesn't detect change in the configuration, like the version number in _oasis.";"None";"OASIS";"None";"OASIS";"v0.3.0~rc1";"None";"None";"" 1157;1;"Open";3;4175;"Francois Berenger";102;"Sylvain Le Gall";"2012-05-16 07:08";"";"2012-07-06 08:33";"No zip.cmxa generated in the zip package";"Hello, I'm not sure it's a bug though. But, my software can't compile without zip.cmxa, apparently, and my version of zip was installed using odb.ml. 'make allopt' is needed in order to build this target, 'make all' doesn't generate it. Regards, F. ";"None";"OASIS-DB";"All";"None";"None";"None";"None";"" 1159;1;"Open";3;4175;"Francois Berenger";102;"Sylvain Le Gall";"2012-05-17 06:41";"";"2012-07-06 08:33";"The camlzip oasis package doesn't install the zip.cmxa file";"Hello, To fix the _oasis file of the package: --- XCustomInstall: make install-findlib XCustomUninstall: make uninstall-findlib --- should become: --- XCustomInstall: make install XCustomUninstall: make uninstall --- Regards, F. ";"None";"OASIS-DB";"All";"OASIS";"None";"major";"None";"" 1170;1;"Open";3;884;"Jonathan Protzenko";102;"Sylvain Le Gall";"2012-06-12 08:21";"";"2012-07-12 19:10";"Oasis, when running commands, doesn't properly escape paths";"setup.ml doesn't work when the path to ocaml contains spaces (default configuration for the windows installer). I think the path to the executables should be run through Filename.quote, with the caveat that in a cygwin development environment using a native ocaml build, Sys.os_type is Win32 so Filename.quote will perform a windows-quote, whereas the expected quote is a unix-quote (I think).";"None";"None";"Windows XP";"None";"None";"None";"None";"" 1171;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2012-06-12 11:50";"";"2012-07-06 08:33";"Show line numbers in errors";"It is an absolute must.";"None";"OASIS";"None";"OASIS";"v0.3.0~rc1";"normal";"None";"" 1184;1;"Open";3;920;"Markus Mottl";102;"Sylvain Le Gall";"2012-07-06 12:09";"";"2012-07-06 12:24";"Variable substitution in fields does not work";"The following does not work: SourceRepository trunk Tag: release-$(pkg_version) The pkg_version will not be substituted. This requires continuously updating the field value whenever the version changes, which can be easily forgotten. Variable substitution in field values seems like an important feature.";"0.3.0";"OASIS";"All";"OASIS";"v0.3.0~rc1";"normal";"None";"" 1185;1;"Open";3;142;"Edgar Friendly";102;"Sylvain Le Gall";"2012-07-06 13:02";"";"2012-09-03 13:13";"Problem with version links on camlzip page";"Apparently + is used as part of camlzip's version numbers, is this causing the version links on the camlzip page to 404?";"None";"OASIS-DB";"None";"Website";"None";"None";"None";"http://oasis.ocamlcore.org/dev/view/camlzip/" 1188;1;"Open";3;4175;"Francois Berenger";102;"Sylvain Le Gall";"2012-07-10 10:05";"";"2012-09-03 13:13";"get a 404 isntead of downloading the package";"Hi, odb zip # fails to get the package A user can't get the zip package from http://oasis.ocamlcore.org/dev/odb/stable/pkg/ while for some other packages it is OK. Regards, F. ";"None";"OASIS-DB";"All";"Website";"None";"major";"None";"http://oasis.ocamlcore.org/dev/odb/stable/pkg//zip-1.04%2Bsvn~oasis3.tar.gz" 1196;1;"Open";3;142;"Edgar Friendly";102;"Sylvain Le Gall";"2012-08-05 04:00";"";"2012-09-03 13:13";"Oasis-db's odb deps don't include XMETARequires deps";"pa_pipebang has the lines: BuildDepends: camlp4.lib, camlp4.quotations, type_conv (>= 3.0.5) XMETARequires: camlp4,type_conv,oUnit in its _oasis file, but the deps for odb come out: deps=type_conv(>=3.0.5),ocamlbuild,camlp4o,camlp4 Having a META require that's not a build require is odd, but I assume that since camlp4 is involved, it's legit. This issue requests that the XMETARequires dependencies be included in the odb deps.";"None";"OASIS-DB";"None";"None";"v0.3.0~rc1";"normal";"None";"" 1197;1;"Open";3;142;"Edgar Friendly";102;"Sylvain Le Gall";"2012-08-05 04:05";"";"2012-09-03 13:13";"The derive operation seems to fail every time";"I've tried deriving two packages (can't recall the first and xstrp4) to update the version of oasis their build system is created with, and after the edit foo-oasis1, I get an error Error Unmanaged error, retry later and contact system administrator if it happens again. If this is supposed to work, let me know what I'm doing wrong.";"None";"OASIS-DB";"None";"Website";"None";"None";"None";"" 1199;1;"Open";3;112;"Hezekiah Carty";102;"Sylvain Le Gall";"2012-08-06 12:24";"";"2012-09-03 13:13";"Extra comma in InternalModules list gives vague error";"If the list of InternalModules ends with a comma, the error given when running ""oasis setup"" is: E: lexing: empty token It would be nice if this error were more descriptive.";"None";"OASIS";"None";"OASIS";"None";"normal";"None";"" 1200;1;"Open";3;112;"Hezekiah Carty";102;"Sylvain Le Gall";"2012-08-06 15:29";"";"2012-09-03 13:13";"oasis-db breaks on packages with '+' in their version";"For example, the zip package is version ""1.04+svn~oasis3"". This worked under earlier versions of oasis-db, but it is broken under 0.1.0~alpha5. ""Broken"" in this case means that the package can not be viewed or modified under the web interface and the package can not be installed from odb.ml.";"None";"OASIS-DB";"None";"General";"None";"normal";"None";"" 1205;1;"Open";3;144;"Christophe Troestler";102;"Sylvain Le Gall";"2012-08-17 12:09";"";"2012-08-17 16:04";"""oasis setup -setup-update dynamic"" must ""empty"" myocamlbuild.ml";"When myocamlbuild.ml exists and ""oasis setup -setup-update dynamic"" is run, the content of this file between (* OASIS_START *) and (* OASIS_STOP *) should be removed. One could also remove the file entirely if no customizations were done — to return to the state where one runs the setup command with no previous files created.";"None";"OASIS";"All";"OASIS";"v0.3.0~rc1";"normal";"None";"" 1209;1;"Open";3;116;"ygrek ";102;"Sylvain Le Gall";"2012-09-03 12:28";"";"2012-09-03 13:13";"quiet install";"oasis's own `make install` doesn't show which binaries are installed";"None";"OASIS";"None";"OASIS";"v0.3.0~rc1";"None";"None";"" 1213;1;"Open";3;144;"Christophe Troestler";100;"Nobody";"2012-09-03 17:11";"";"2012-09-03 17:11";"if ocaml_version does not work.";"The conditional if ocaml_version(3.12.1) does not work (oasis reports a syntax error). A workatound for some cases is to do this in myocamlbuild.ml: https://github.com/agarwal/ocamlweb/commit/f95a5556b744b9663cbef1fb912c92af35091529";"None";"OASIS";"All";"General";"v0.3.0~rc1";"normal";"None";"" 1215;1;"Open";3;112;"Hezekiah Carty";102;"Sylvain Le Gall";"2012-09-06 13:19";"";"2012-09-06 14:48";"Pack: true and FilesAB: foo.ml.ab do not work properly";"If a module is listed in FilesAB and the resulting module is listed under Modules in a Library section with Pack: true the module will not be compiled with -for-pack. An example: FilesAB: src/config.ml.ab Library: foo Path: src/ Pack: true Modules: Config Compilation will fail in this case due to -for-pack not being specified when config.ml is compiled.";"None";"OASIS";"All";"OASIS";"v0.3.0~rc1";"normal";"None";"" 1219;1;"Open";3;188;"Dawid Toton";100;"Nobody";"2012-09-19 09:27";"";"2012-09-19 13:21";"OASIS-DB API seems down";"Got 404 at http://oasis.ocamlcore.org/api/ I'd like do ask the API for URLs of all new tarballs created since some particular time.";"None";"OASIS-DB";"None";"Website";"None";"normal";"None";"http://oasis.ocamlcore.org/api/" 1220;1;"Open";3;188;"Dawid Toton";100;"Nobody";"2012-09-19 09:40";"";"2012-09-19 09:40";"The info about OASIS-DB sources leads down the garden path";"The link to OASIS-DB sources seems outdated: http://oasis.forge.ocamlcore.org/oasis-db.html points to http://darcs.ocamlcore.org/cgi-bin/darcsweb.cgi?r=oasis/oasis-db;a=summary It looks like the development has moved to git? ";"None";"OASIS-DB";"None";"Website";"None";"normal";"None";"http://oasis.forge.ocamlcore.org/oasis-db.html" 1224;1;"Open";3;144;"Christophe Troestler";294;"Philippe Veber";"2012-09-29 08:14";"";"2012-09-29 08:14";"Object: ""Install: false"" not acted upon properly";"When declaring an Object section that must not be installed (using ""Install: false""), oasis should not report conflicts for the META file: E: The file 'src/META' generated for the library 'A' is already used for the library 'B'. You can make one a child of the other to solve this (field `FindlibParent:`). 'B' being the object section. Moreover, the advice is wrong because ""FindlibParent:"" and ""FindlibName:"" are not supported by Object sections — either they should or Object sections should never be in the META file.";"None";"OASIS";"All";"OASIS";"v0.3.0~rc1";"normal";"None";"" 1234;1;"Open";3;7847;"Jacques-Pascal Deplaix";100;"Nobody";"2012-11-21 21:46";"";"2012-11-21 21:46";"Tags in _tags are not precises";"For examples: : pkg_batteries should be (for a library that contains Module1, Module2, …): : pkg_batteries : pkg_batteries … Because if severals Libraries are in src (in this case), they all receive the tags from others.";"0.3.0";"OASIS";"None";"Plugin OCamlbuild";"None";"normal";"None";"" 1236;1;"Open";3;7322;"Gerd Stolpmann";100;"Nobody";"2012-12-01 14:31";"";"2012-12-01 14:31";"Lowercase module name leads to ""lexing: empty token""";"For the attached _oasis file: $ oasis setup E: lexing: empty token Changing the module name into Lib is the fix. oasis version is 0.3.0.";"None";"OASIS";"Linux";"OASIS";"None";"minor";"None";"" 1239;1;"Open";3;294;"Philippe Veber";294;"Philippe Veber";"2012-12-11 21:44";"";"2012-12-15 17:52";"Warning when linking an executable with a internal packed library";"Compilation of the packedlib example issues a warning: cochinois:~/oasis/examples/packedlib 22:36]$ocaml setup.ml -build Finished, 1 target (0 cached) in 00:00:00. + ocamlfind ocamlc -g -linkpkg src/packedlib.cma src/packedlib.cmo test/main.cmo -o test/main.byte File ""src/packedlib.cmo"", line 1: Warning 31: files src/packedlib.cmo and src/packedlib.cma(Packedlib) both define a module named Packedlib Finished, 21 targets (0 cached) in 00:00:00. which is due to trying to compile main.ml adding both the cma and the cmo of the packed library. The cma is correct (and is added via the use_* tag, which is the intended behavior). Now I'm not sure why the cmo gets added. It seems to me that the module PackedLib is seen by ocamldep, then ocamlbuild sees the mlpack file and tries to be smart by adding the cmo automatically. There is no problem when the packed library is findlib-installed, and this is only a warning but still. The only fix I see is in myocamlbuild.ml, refrain from adding the rule [use_foo => add foo.cma] when the library is packed. Is there a better way to fix this issue? ";"None";"OASIS";"None";"None";"v0.3.0~rc1";"None";"Accepted As Bug";"" 1244;1;"Open";3;102;"Sylvain Le Gall";102;"Sylvain Le Gall";"2012-12-28 10:23";"";"2013-01-02 18:05";"Cannot download tarballs that contains a ~ in the name.";" - 2 packages not downloadable    * this seems to be a problem with oasis-db API. Sometimes tarballs      contain escape characters (%7E instead of ~)";"None";"OASIS-DB";"None";"None";"None";"None";"None";"" 1245;1;"Open";3;10038;"Christopher Zimmermann";100;"Nobody";"2013-01-03 16:44";"";"2013-01-03 16:44";"ounit test failures on OpenBSD";"Hi, I just ported oasis (and all dependencies) to OpenBSD. Running the ounit regression tests reveals several test failures. But I have no idea how to further deal with them. The test log is attached. Christopher";"None";"OASIS";"OpenBSD";"OASIS";"v0.3.0~rc1";"None";"None";"" 1249;1;"Open";3;857;"Jérôme Vouillon";102;"Sylvain Le Gall";"2013-01-18 13:22";"";"2013-01-18 13:59";"""ocamlc -config"" invoked before ""-override ocamlc XXX"" takes effect";"For cross-compilation, I need to use an ocaml compiler different from the standard one. It seems that the ""-override ocamlc XXX"" directive should be the right way to do that. However, Oasis invokes the ocamc compiler with the ""-config"" option to get OCaml configuration information before the ""-override"" directive takes effect. As a consequence, the file ""setup.data"" gets filled with wrong data. ";"0.4.0";"OASIS";"None";"Base";"None";"major";"Accepted As Bug";"" 1250;1;"Open";3;857;"Jérôme Vouillon";100;"Nobody";"2013-01-18 13:46";"";"2013-01-18 13:46";"Sys.os_type, os_type variable and cross-compilation";"When cross-compiling, one needs to make a difference between the target os type and the build os type. It seems to me that Sys.os_type could refer to the build os type, and then the os_type variable in setup.data could be free to refer to the target os type. For instance, to compile Lwt for Windows, I need to set the variable os_type to Win32 for proper configuration, but then oasis complains: ""Cannot handle os_type Win32 filename concat"". The work-around I use is to provide an initial setup.data file with just the variables ""prefix"" and ""datarootdir"", so that oasis does not have to concatenate filenames. But it seems to me that oasis should just ignore variable os_type and always use Sys.os_type instead. Do we ever need to run setup.ml on one OS using the ocamlc binary from another OS? ";"None";"None";"None";"OASIS";"None";"None";"None";"" 1251;1;"Open";3;857;"Jérôme Vouillon";100;"Nobody";"2013-01-18 14:09";"";"2013-01-21 14:30";"The OCamlbuild plugin assumes that dynamic linking is supported.";"Cross compilers cannot support dynamic linking as ocamlc needs to load the shared library when linking to find C symbols. However, the OCamlbuild plugin systematically requests the compilation of shared libraries dll%s_stubs.dll. The current work-around is to pretend that dynamic linking is supported: shared libraries are produced by ocamlmklib, but they cannot be used, and ocamlc has to be invoked with the ""-custom"" option when linking. The fix might be simply to not ever request the compilation of shared libraries dll%s_stubs.dll (see attached patch). When dynamic linking is supported, ocamlmklib will produce them anyway.";"None";"None";"None";"Plugin OCamlbuild";"None";"None";"None";"" 1252;1;"Open";3;857;"Jérôme Vouillon";100;"Nobody";"2013-01-18 14:24";"";"2013-01-19 19:40";"The OCamlbuild plugin should look-up in setup.data the ocamlfind program to use";"At the moment, the OCamlbuild plugin does not look up in setup.data which ocamlfind program to use. Here is a patch that fixes that. There is a pitfall with this patch, though: ocamlfind only supports ocamlmklib since version 1.3.1, and the current version (1.3.3) has a performance bug (the performance is quadratic in the number of arguments, which can be quite slow). So, one should probably wait for a new release of ocamlfind, or drop the last change in the patch for the moment. In the second case, ocamlmklib should probably be looked up in setup.data anyway, as there is currently no way to override the OCamlbuild ocamlmklib settings (there is no -ocamlmklib option). ";"None";"None";"None";"Plugin OCamlbuild";"None";"enhancement";"None";"" 1253;1;"Open";3;1231;"Sergei Lebedev";100;"Nobody";"2013-01-23 15:42";"";"2013-01-23 15:42";"Stack_overflow with circular dependencies";"The following '_oasis' causes a stack overflow, during 'oasis setup': Library binary Path: src BuildDepends: binary, num Modules: Binary";"None";"OASIS";"All";"OASIS";"v0.3.0~rc1";"None";"None";"" 1271;1;"Open";3;11453;"Chet Murthy";102;"Sylvain Le Gall";"2013-04-02 19:17";"";"2013-04-02 20:07";"a Module directive with directory (e.g. ""bar/Bar"") does not work with a Path of "".""";"I created a trivial project with a Library this: Library bar Path: . FindlibName: foo_bar buildTools: ocamlbuild Modules: bar/Bar and when I build, I get an error: E: Failure(""No one of expected built files '_build/bar.cma' exists"") If I then move _oasis up a directory, e.g. Library bar Path: foo FindlibName: foo_bar buildTools: ocamlbuild Modules: bar/Bar the build works fine. In the attached file, the ""foo"" directory has the first _oasis file; the ""ugh"" directory has the second. ";"0.4.0";"OASIS";"Linux";"OASIS";"v0.4.0";"normal";"Accepted As Bug";"" 1273;1;"Open";3;824;"Török Edwin";100;"Nobody";"2013-04-24 09:15";"";"2013-04-24 10:08";"cmxs build error on OCaml 3.11.2: only supported since ocamlbuild 3.12.0";"According to http://caml.inria.fr/pub/distrib/ocaml-4.00/notes/Changes ocamlbuild support for .cmxs was introduced in 3.12.0. OASIS enables building of cmxs for 3.11.2 though, which results in this error for example: Solver failed: Ocamlbuild knows of no rules that apply to a target named src/uutf.cmxs. This can happen if you ask Ocamlbuild to build a target with the wrong extension (e.g. .opt instead of .native) or if the source files live in directories that have not been specified as include directories. Backtrace: - Failed to build the target src/uutf.cmxs - Building src/uutf.cmxs The fix would be probably to change ocaml_lt_312 to ocaml_lt_320 for cmxs support.";"None";"OASIS";"Linux";"Plugin OCamlbuild";"None";"None";"None";""