Hello,
Hans Hagen writes:
> well, i put the older in in the latest anyway
Rather belatedly, I tested this a few moments ago: it works flawlessly.
Many, many thanks.
Roger
___
If your question is of interest to
Hi Alan,
Alan Braslau via ntg-context writes:
> On Sun, 25 Feb 2024 14:23:10 +0100
> Henning Hraban Ramm wrote:
>
>> Am 25.02.24 um 13:12 schrieb Hans Hagen:
>> > We could add a flag to the installer that doesn't update the
>> > binaries but intead (advices) to build the bins but it assumes
>>
Hello Hans,
Hans Hagen writes:
>> Please do not go to this trouble on my account. I have decided to
>> give
>> up on context.
> well, i put the older in in the latest anyway
Many thanks, I will give it a try in the next day or so and respond to
the list.
Best wishes,
Roger
On Sun, 25 Feb 2024 14:23:10 +0100
Henning Hraban Ramm wrote:
> Am 25.02.24 um 13:12 schrieb Hans Hagen:
> > We could add a flag to the installer that doesn't update the
> > binaries but intead (advices) to build the bins but it assumes
> > Cmake and gcc to be installed (we could cheat and use
On 2/26/2024 2:21 PM, Roger Mason wrote:
Hello Hans,
Hans Hagen writes:
On 2/26/2024 12:22 PM, Roger Mason wrote:
Looks like the unset TEXMF and TEXMFCNF envars are a problem. What
should they be set to and where should they be set?
fwiw, i'll do an update oen fo these days with the old
Hello Hans,
Hans Hagen writes:
> On 2/26/2024 12:22 PM, Roger Mason wrote:
>
>> Looks like the unset TEXMF and TEXMFCNF envars are a problem. What
>> should they be set to and where should they be set?
> fwiw, i'll do an update oen fo these days with the old bin
>
> what you coudl do is
Hello Hraban,
Henning Hraban Ramm writes:
> Usually, you don’t need to set any variables.
> The default configuration file is also fine.
>
> Does "context --version" work?
No:
mtxrun | forcing cache reload
resolvers | resolving | configuration files already identified
resolvers
On 2/26/2024 12:22 PM, Roger Mason wrote:
Looks like the unset TEXMF and TEXMFCNF envars are a problem. What
should they be set to and where should they be set?
fwiw, i'll do an update oen fo these days with the old bin
what you coudl do is download the latest zip and unzip it in
Am 26.02.24 um 12:22 schrieb Roger Mason:
resolvers | resolving | variable 'SELFAUTOLOC' set to
'/usr/home/rmason/context/tex/texmf-freebsd-amd64/bin'
resolvers | resolving | variable 'SELFAUTODIR' set to
'/usr/home/rmason/context/tex/texmf-freebsd-amd64'
resolvers |
Hello,
Henning Hraban Ramm writes:
>
> I guess you’re lacking the main distribution package.
>
> My installation (tree -dL 4, partly shortened):
>
> .
> ├── bin (installation only)
> └── tex
> ├── texmf-cache (necessary, but auto-created?)
> │ ├── luametatex-cache
> │ │ └──
Am 25.02.24 um 20:24 schrieb Roger Mason:
Hello Hraban,
Henning Hraban Ramm writes:
Am 25.02.24 um 17:08 schrieb Roger Mason:
Do I need mtxrun? If so, where are the sources and how do I build
it?
Yes, you need it, but it’s just an alias to luametatex:
~/context/tex/texmf-osx-64/bin $
Hello Hraban,
Henning Hraban Ramm writes:
> Am 25.02.24 um 17:08 schrieb Roger Mason:
>> Do I need mtxrun? If so, where are the sources and how do I build
>> it?
>
> Yes, you need it, but it’s just an alias to luametatex:
>
> ~/context/tex/texmf-osx-64/bin $ ll
> total 7704
> -rw-r--r--@ 1
Am 25.02.24 um 17:08 schrieb Roger Mason:
I see that the build does not provide the mtxrun binary that the
installer uses. Does that mean I dont need mtxrun?
Do I need mtxrun? If so, where are the sources and how do I build it?
Yes, you need it, but it’s just an alias to luametatex:
Hello,
Roger Mason writes:
> Hello Henning, Mojca,
>
> Mojca Miklavec writes:
>
>> There were some troubles with our infrastructure which led Hans to
>> build the binaries himself without paying extra attention to
>> compatibility with older systems.
>>
>> You can find the binaries here:
>>
Am 25.02.24 um 13:12 schrieb Hans Hagen:
We could add a flag to the installer that doesn't update the binaries
but intead (advices) to build the bins but it assumes Cmake and gcc to
be installed (we could cheat and use an existing cmake made make file).
Yes please! A platform-independent
Hello Henning, Mojca,
Mojca Miklavec writes:
> There were some troubles with our infrastructure which led Hans to
> build the binaries himself without paying extra attention to
> compatibility with older systems.
>
> You can find the binaries here:
>
On Sun, 25 Feb 2024 at 13:12, Hans Hagen wrote:
>
> Can freebsd 14 work with older bins?
Yes, definitely.
> The previous method of these hard coded version numbers was a pain
You might be mixing up FreeBSD and OpenBSD.
FreeBSD is (fully) compatible, OpenBSD is totally incompatible.
(I'm even
On 2/24/2024 4:28 PM, Mojca Miklavec wrote:
Dear Roger,
On Sat, 24 Feb 2024 at 15:34, Roger Mason wrote:
After unpacking, running the install scripts results in:
ld-elf.so.1: /home/rmason/Software/Context/bin/mtxrun: Undefined symbol
"__libc_start1@FBSD_1.7"
I assume this is because mtxrun
Dear Roger,
On Sat, 24 Feb 2024 at 15:34, Roger Mason wrote:
>
> After unpacking, running the install scripts results in:
>
> ld-elf.so.1: /home/rmason/Software/Context/bin/mtxrun: Undefined symbol
> "__libc_start1@FBSD_1.7"
>
> I assume this is because mtxrun is compiled for FreeBSD 14.0.
There
Am 24.02.24 um 15:20 schrieb Roger Mason:
Hello,
I've been away from ConTeXt for some time but now I want to install it
on my FreeBSD 13.2 system(s) (I have not switched any machines to 14.0
yet). After unpacking, running the install scripts results in:
ld-elf.so.1:
20 matches
Mail list logo
