[Context] update before building & fixing some issues
![](https://secure.gravatar.com/avatar/6114858d84b0f40cf715f12237ab67a1.jpg?s=120&d=mm&r=g)
Hello, Just in case - please update the building script before executing it since location of metapost binary has changed. Taco - we had to re-add dvitomp binary a while ago for some reason I forgot. Is that file still needed and why (not)? One more thing: I'll try to fix a few issues in the minimals next week (the most important one would be sorting out which luatex binary to use and to enable choosing "experimental" version of luatex, but there are definitely more issues). I need to prepare a list, but I'll start concentrating on the issue next week. You may put your ideas on the wiki or to the tracker or just reply here. Mojca
![](https://secure.gravatar.com/avatar/db1ef66b49c350c2c3d0054a37e8098c.jpg?s=120&d=mm&r=g)
2009/4/22 Mojca Miklavec: > Hello, > > Just in case - please update the building script before executing it > since location of metapost binary has changed. > > Taco - we had to re-add dvitomp binary a while ago for some reason I > forgot. Is that file still needed and why (not)? > > One more thing: I'll try to fix a few issues in the minimals next week > (the most important one would be sorting out which luatex binary to > use and to enable choosing "experimental" version of luatex, but there > are definitely more issues). I need to prepare a list, but I'll start > concentrating on the issue next week. You may put your ideas on the > wiki or to the tracker or just reply here. Could be totally unrelated, but I'm dealing with freebsd-amd64 and mtxrun needs this patch in order to work --- mtxrun 2009-04-23 01:34:57.000000000 +0200 +++ mtxrun.modified 2009-04-23 01:34:33.000000000 +0200 @@ -1622,7 +1622,12 @@ return "solaris-intel" end elseif name == "freebsd" then + local architecture = os.arch() + if architecture:find("amd64") then + return "freebsd-amd64" + else return "freebsd" + end end end return default or name Regards -- Diego Depaoli
![](https://secure.gravatar.com/avatar/6114858d84b0f40cf715f12237ab67a1.jpg?s=120&d=mm&r=g)
On Thu, Apr 23, 2009 at 01:39, Diego Depaoli wrote:
Could be totally unrelated, but I'm dealing with freebsd-amd64 and mtxrun needs this patch in order to work --- mtxrun 2009-04-23 01:34:57.000000000 +0200 +++ mtxrun.modified 2009-04-23 01:34:33.000000000 +0200 @@ -1622,7 +1622,12 @@ return "solaris-intel" end elseif name == "freebsd" then + local architecture = os.arch() + if architecture:find("amd64") then + return "freebsd-amd64" + else return "freebsd" + end end end return default or name
I'm sorry, I thought that this has been fixed already. (Do you manage to run the minimals at all?) Hans, can you please fix this? Thanks, Mojca
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Mojca Miklavec wrote:
On Thu, Apr 23, 2009 at 01:39, Diego Depaoli wrote:
Could be totally unrelated, but I'm dealing with freebsd-amd64 and mtxrun needs this patch in order to work --- mtxrun 2009-04-23 01:34:57.000000000 +0200 +++ mtxrun.modified 2009-04-23 01:34:33.000000000 +0200 @@ -1622,7 +1622,12 @@ return "solaris-intel" end elseif name == "freebsd" then + local architecture = os.arch() + if architecture:find("amd64") then + return "freebsd-amd64" + else return "freebsd" + end end end return default or name
I'm sorry, I thought that this has been fixed already. (Do you manage to run the minimals at all?) Hans, can you please fix this?
i added it but no update today as i'm in the middle of a partial structure rewrite ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
![](https://secure.gravatar.com/avatar/db1ef66b49c350c2c3d0054a37e8098c.jpg?s=120&d=mm&r=g)
2009/4/23 Mojca Miklavec
On Thu, Apr 23, 2009 at 01:39, Diego Depaoli wrote:
Could be totally unrelated, but I'm dealing with freebsd-amd64 and mtxrun needs this patch in order to work
I'm sorry, I thought that this has been fixed already. No problem (Do you manage to run the minimals at all?) I need more time to answer this question.
Regards -- Diego Depaoli
![](https://secure.gravatar.com/avatar/db1ef66b49c350c2c3d0054a37e8098c.jpg?s=120&d=mm&r=g)
2009/4/23 Diego Depaoli
2009/4/23 Mojca Miklavec
: On Thu, Apr 23, 2009 at 01:39, Diego Depaoli wrote:
Could be totally unrelated, but I'm dealing with freebsd-amd64 and mtxrun needs this patch in order to work
I'm sorry, I thought that this has been fixed already. No problem (Do you manage to run the minimals at all?) I updated binaries for freebsd-amd64. Until now all works well.
Cheers -- Diego Depaoli
![](https://secure.gravatar.com/avatar/565476157eb3895a9c928ffce26d988d.jpg?s=120&d=mm&r=g)
Mojca Miklavec wrote:
Hello,
Just in case - please update the building script before executing it since location of metapost binary has changed.
Trick: all luatex builds now also build mpost as part of the process, you can as well use that one.
Taco - we had to re-add dvitomp binary a while ago for some reason I forgot. Is that file still needed and why (not)?
You can copy 'mpost' (1.200) to 'dvitomp', and it will behave like dvitomp. It is needed by texexec when it is asked to generate labels. Best wishes, Taco PS Mojca: this is a resend to the list, my first reply went to you only
![](https://secure.gravatar.com/avatar/6114858d84b0f40cf715f12237ab67a1.jpg?s=120&d=mm&r=g)
On Thu, Apr 23, 2009 at 08:34, Taco Hoekwater wrote:
Mojca Miklavec wrote:
Hello,
Just in case - please update the building script before executing it since location of metapost binary has changed.
Trick: all luatex builds now also build mpost as part of the process, you can as well use that one.
Interesting :) I wanted to ask you if there's some simple way to figure out which version of mpost comes with luatex, but maybe that's not relevant. We can delete the mpost version entry and just assume that it matches whatever version has been shipped with luatex. Is there some way to check if metapost has been changed at all when you update luatex? And what do you do when you only release a new metapost and no new luatex?
Taco - we had to re-add dvitomp binary a while ago for some reason I forgot. Is that file still needed and why (not)?
You can copy 'mpost' (1.200) to 'dvitomp', and it will behave like dvitomp. It is needed by texexec when it is asked to generate labels.
OK, so I'll just make a symlink for all architectures then. Mojca
![](https://secure.gravatar.com/avatar/49e63acb01f2ca80efce7eed08310ce8.jpg?s=120&d=mm&r=g)
Mojca Miklavec wrote:
On Thu, Apr 23, 2009 at 08:34, Taco Hoekwater wrote:
Hello,
Just in case - please update the building script before executing it since location of metapost binary has changed. Trick: all luatex builds now also build mpost as part of the
Mojca Miklavec wrote: process, you can as well use that one.
Interesting :) I wanted to ask you if there's some simple way to figure out which version of mpost comes with luatex, but maybe that's not relevant. We can delete the mpost version entry and just assume that it matches whatever version has been shipped with luatex.
Is there some way to check if metapost has been changed at all when you update luatex? And what do you do when you only release a new metapost and no new luatex?
fyi ... mkiv ha sits own metafun format so in principle mpost and luatex-mplib might differ ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
participants (4)
-
Diego Depaoli
-
Hans Hagen
-
Mojca Miklavec
-
Taco Hoekwater