Send Moses-support mailing list submissions to
moses-support@mit.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/moses-support
or, via email, send a message with subject or body 'help' to
moses-support-request@mit.edu
You can reach the person managing the list at
moses-support-owner@mit.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Moses-support digest..."
Today's Topics:
1. Installation: symlinks created at the wrong place when using
--prefix? (Yves Scherrer)
2. Re: Installation: symlinks created at the wrong place when
using --prefix? (Hieu Hoang)
3. Re: Installation: symlinks created at the wrong place when
using --prefix? (Hieu Hoang)
4. Re: Installation: symlinks created at the wrong place when
using --prefix? (Yves Scherrer)
----------------------------------------------------------------------
Message: 1
Date: Tue, 20 Feb 2018 10:20:12 +0200
From: "Yves Scherrer" <yves.scherrer@helsinki.fi>
Subject: [Moses-support] Installation: symlinks created at the wrong
place when using --prefix?
To: "" <moses-support@mit.edu>
Message-ID: <3faa3811-8086-47b2-b994-0ade99ad0fbc@getmailbird.com>
Content-Type: text/plain; charset="utf-8"
Hi all,
My first attempt at testing moses2 failed because CreateProbingPT2 could not be found...
On the last line of mosesdecoder/Jamroot, CreateProbingPT2 is created as a symlink to CreateProbingPT, but this is done in the $(TOP)/bin directory (same for moses_chart BTW). However, $(TOP) refers to the build directory, which may differ from the final install directory, namely when --prefix is used and set to something else than the current directory. In this case, the symlinks are indeed created, but in a directory from which the executables have already been moved out of...
Can somebody confirm that behavior? I'm a little surprised that this hasn't come up earlier...?For me, replacing $(TOP) by $(PREFIX) in the last couple of lines of the Jamroot file did the trick both when using --prefix and when not using it, but maybe there is a better way to handle this.
Best,
Yves
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20180220/db3580e5/attachment-0001.html
------------------------------
Message: 2
Date: Tue, 20 Feb 2018 09:20:16 +0000
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Installation: symlinks created at the
wrong place when using --prefix?
To: Yves Scherrer <yves.scherrer@helsinki.fi>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbgTXuT2iek91K6cxL5Yk5hNa82Gn=2fwC1-zzb8VNX4NQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Hieu Hoang
Sent while bumping into things
On 20 Feb 2018 8:25 a.m., "Yves Scherrer" <yves.scherrer@helsinki.fi> wrote:
Hi all,
My first attempt at testing moses2 failed because CreateProbingPT2 could
not be found...
On the last line of mosesdecoder/Jamroot, is created as a symlink to
CreateProbingPT, but this is done in the $(TOP)/bin directory (same for
moses_chart BTW). However, $(TOP) refers to the build directory, which may
differ from the final install directory, namely when --prefix is used and
set to something else than the current directory. In this case, the
symlinks are indeed created, but in a directory from which the executables
have already been moved out of...
Can somebody confirm that behavior? I'm a little surprised that this hasn't
come up earlier... For me, replacing $(TOP) by $(PREFIX) in the last couple
of lines of the Jamroot file did the trick both when using --prefix and
when not using it, but maybe there is a better way to handle this.
Do a git pull for your changes.
I don't think a lot of people use --prefix so the bug was missed.
Btw, you can use CreateProbingPT instead of CreateProbingPT2. The soft link
was added for backyard compatibility when the two used to be different
Best,
Yves
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20180220/f19fd900/attachment-0001.html
------------------------------
Message: 3
Date: Tue, 20 Feb 2018 10:24:07 +0000
From: Hieu Hoang <hieuhoang@gmail.com>
Subject: Re: [Moses-support] Installation: symlinks created at the
wrong place when using --prefix?
To: Yves Scherrer <yves.scherrer@helsinki.fi>
Cc: moses-support <moses-support@mit.edu>
Message-ID:
<CAEKMkbhUGdPd9thVF1me5ZFdUL1tkm92LYUhuTOPOyT3Aij8pA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
I would actually advised against using --prefix
The moses scripts are written with the assumption that the directories
bin
scripts
are side-by-side. --prefix seems to move bin, but not scripts
Hieu Hoang
http://moses-smt.org/
On 20 February 2018 at 09:20, Hieu Hoang <hieuhoang@gmail.com> wrote:
>
>
> Hieu Hoang
> Sent while bumping into things
>
> On 20 Feb 2018 8:25 a.m., "Yves Scherrer" <yves.scherrer@helsinki.fi>
> wrote:
>
> Hi all,
>
> My first attempt at testing moses2 failed because CreateProbingPT2 could
> not be found...
>
> On the last line of mosesdecoder/Jamroot, is created as a symlink to
> CreateProbingPT, but this is done in the $(TOP)/bin directory (same for
> moses_chart BTW). However, $(TOP) refers to the build directory, which may
> differ from the final install directory, namely when --prefix is used and
> set to something else than the current directory. In this case, the
> symlinks are indeed created, but in a directory from which the executables
> have already been moved out of...
>
> Can somebody confirm that behavior? I'm a little surprised that this
> hasn't come up earlier... For me, replacing $(TOP) by $(PREFIX) in the
> last couple of lines of the Jamroot file did the trick both when using
> --prefix and when not using it, but maybe there is a better way to handle
> this.
>
> Do a git pull for your changes.
>
> I don't think a lot of people use --prefix so the bug was missed.
>
> Btw, you can use CreateProbingPT instead of CreateProbingPT2. The soft
> link was added for backyard compatibility when the two used to be different
>
>
> Best,
> Yves
>
> _______________________________________________
> Moses-support mailing list
> Moses-support@mit.edu
> http://mailman.mit.edu/mailman/listinfo/moses-support
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20180220/6291605a/attachment-0001.html
------------------------------
Message: 4
Date: Tue, 20 Feb 2018 13:59:46 +0200
From: "Yves Scherrer" <yves.scherrer@helsinki.fi>
Subject: Re: [Moses-support] Installation: symlinks created at the
wrong place when using --prefix?
To: "Hieu Hoang" <hieuhoang@gmail.com>
Cc: moses-support@mit.edu
Message-ID: <9e7fd32d-dde4-45b9-9b10-c5a1f089f0dc@getmailbird.com>
Content-Type: text/plain; charset="utf-8"
Hi,
Thanks for your comments. I've created a pull request - do whatever you like with it ;)
For the scripts, I've been using --install-scripts to move them. This did the job, at least in my environment...
Yves
On 20/02/2018 12:24:25, Hieu Hoang <hieuhoang@gmail.com> wrote:
I would actually advised against using --prefix
The moses scripts are written with the assumption that the directories
?? bin
?? scripts
are side-by-side. --prefix seems to move bin, but not scripts
Hieu Hoang
http://moses-smt.org/ [http://moses-smt.org/]
On 20 February 2018 at 09:20, Hieu Hoang <hieuhoang@gmail.com [mailto:hieuhoang@gmail.com]> wrote:
Hieu Hoang
Sent while bumping into things
On 20 Feb 2018 8:25 a.m., "Yves Scherrer" <yves.scherrer@helsinki.fi [mailto:yves.scherrer@helsinki.fi]> wrote:
Hi all,
My first attempt at testing moses2 failed because CreateProbingPT2 could not be found...
On the last line of mosesdecoder/Jamroot,? is created as a symlink to CreateProbingPT, but this is done in the $(TOP)/bin directory (same for moses_chart BTW). However, $(TOP) refers to the build directory, which may differ from the final install directory, namely when --prefix is used and set to something else than the current directory. In this case, the symlinks are indeed created, but in a directory from which the executables have already been moved out of...
Can somebody confirm that behavior? I'm a little surprised that this hasn't come up earlier...?For me, replacing $(TOP) by $(PREFIX) in the last couple of lines of the Jamroot file did the trick both when using --prefix and when not using it, but maybe there is a better way to handle this.
Do a git pull for your changes.
I don't think a lot of people use --prefix so the bug was missed.?
Btw, you can use?CreateProbingPT instead of?CreateProbingPT2. The soft link was added for backyard compatibility when the two used to be different
Best,
Yves
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu [mailto:Moses-support@mit.edu]
http://mailman.mit.edu/mailman/listinfo/moses-support [http://mailman.mit.edu/mailman/listinfo/moses-support]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/mailman/private/moses-support/attachments/20180220/4ac3edf4/attachment.html
------------------------------
_______________________________________________
Moses-support mailing list
Moses-support@mit.edu
http://mailman.mit.edu/mailman/listinfo/moses-support
End of Moses-support Digest, Vol 136, Issue 6
*********************************************
Subscribe to:
Post Comments (Atom)
0 Response to "Moses-support Digest, Vol 136, Issue 6"
Post a Comment