caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gabriel Scherer <gabriel.scherer@gmail.com>
To: "Soegtrop, Michael" <michael.soegtrop@intel.com>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] Building ocamlbuild with opam fails after opam switch <version>
Date: Sat, 25 Jun 2016 16:06:00 -0400	[thread overview]
Message-ID: <CAPFanBHnttkNgY0hcn77SQSnZ4+ov=LFLuxW=58Noh9hJ_CcRg@mail.gmail.com> (raw)
In-Reply-To: <0F7D3B1B3C4B894D824F5B822E3E5A172CF1B456@IRSMSX102.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 2165 bytes --]

The opam variables `foo` is accessed as %{foo}% in opam metadata, so you
should use

  "PREFIX=%{prefix}%"

On Sat, Jun 25, 2016 at 1:32 PM, Soegtrop, Michael <
michael.soegtrop@intel.com> wrote:

> Dear Gabriel,
>
>
>
> with your pointers I found it.
>
>
>
> I tried two things, one is to switch to a mingw64 4.03.0 compiler package
> I made myself. In this, as it looks, I messed up the transfer of the prefix
> to make (see my compiler file below), which results in the issues with
> building ocamlbuild.
>
>
>
> Then I tried, as a cross check, a switch to the original opam 4.03.0
> package and building ocamlbuild there. This also fails, but cause of a
> different reason (mantis #7268). Somehow I mixed things up in scrolling up
> my shell and thought it was the same bug.
>
>
>
> The .comp file I experimented with is copied below. I didn’t yet find the
> right syntax to combine a string and a variable into one argument
> ("PREFIX="prefix), need to read the opam manual …
>
>
>
> Best regards,
>
>
>
> Michael
>
>
>
> opam-version: "1"
>
> version: "4.03.0"
>
> src: "https://github.com/ocaml/ocaml/archive/4.03.0.tar.gz"
>
> build: [
>
>   [ "git" "clone" "https://github.com/alainfrisch/flexdll.git" ]
>
>   [ "cp" "flexdll/flexdll.h"
> "/usr/x86_64-w64-mingw32/sys-root/mingw/include" ]
>
>   [ "cp" "config/m-nt.h" "config/m.h" ]
>
>   [ "cp" "config/s-nt.h" "config/s.h" ]
>
>   [ "cp" "config/Makefile.mingw64" "config/Makefile" ]
>
>   [ make "-f" "Makefile.nt" "PREFIX="prefix "flexdll" ]
>
>   [ make "-f" "Makefile.nt" "PREFIX="prefix "world" ]
>
>   [ make "-f" "Makefile.nt" "PREFIX="prefix "opt" ]
>
>   [ make "-f" "Makefile.nt" "PREFIX="prefix "opt.opt" ]
>
>   [ make "-f" "Makefile.nt" "PREFIX="prefix "install" ]
>
> ]
>
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Christian Lamprechter
> Chairperson of the Supervisory Board: Nicole Lau
> Registered Office: Munich
> Commercial Register: Amtsgericht Muenchen HRB 186928
>

[-- Attachment #2: Type: text/html, Size: 7091 bytes --]

      reply	other threads:[~2016-06-25 20:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-25 13:57 Soegtrop, Michael
2016-06-25 15:37 ` Gabriel Scherer
2016-06-25 15:57   ` Soegtrop, Michael
2016-06-25 16:27     ` Gabriel Scherer
2016-06-25 17:32       ` Soegtrop, Michael
2016-06-25 20:06         ` Gabriel Scherer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAPFanBHnttkNgY0hcn77SQSnZ4+ov=LFLuxW=58Noh9hJ_CcRg@mail.gmail.com' \
    --to=gabriel.scherer@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=michael.soegtrop@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).