FYI, I have moved this discussion to the TeX Live ML as it
is not texinfo related.
On Tue, 01 Nov 2016, Liviu Ionescu wrote:
> no, I don't *need* to recompile the binaries, but past experience with many
> other packages showed that some tools are not very happy when moved to a
> different folder
> On 1 Nov 2016, at 02:57, Norbert Preining wrote:
>
> Do you *need* to recompile the binaries?
>
> There are options, without any problem: Debian ships TeX Live packages since
> more than 10 years,
> and all of them are build from source, no binaries included. It can be done,
> but
> it need
Hi Liviu,
> I know what went wrong, I missed the "detail" that I need to install
> something :-( (or, more correctly, more than "make install").
>
> Up to now I successfully installed tens of other unix/linux packages, and all
> required nothing more than source packages. tex is different, it
> On 31 Oct 2016, at 01:56, Karl Berry wrote:
>
> you're missing tons of stuff. Without knowing how you
> installed it, no way to guess what went wrong.
I know what went wrong, I missed the "detail" that I need to install something
:-( (or, more correctly, more than "make install").
Up to no
Can't locate TeXLive/TLConfig.pm
As surmised, you're missing tons of stuff. Without knowing how you
installed it, no way to guess what went wrong.
You might be able to recover with "update-tlmgr-latest.sh".
See the "disaster recovery" section in:
http://tug.org/texlive/tlmgr.html
Or you migh
> On 31 Oct 2016, at 01:12, Karl Berry wrote:
>
> try "tlmgr reinstall tetex"
ilg-mbp:bin ilg$ ./tlmgr reinstall tetex
Can't locate TeXLive/TLConfig.pm in @INC (you may need to install the
TeXLive::TLConfig module) (@INC contains:
/Users/ilg/Work/no-backup/texlive/texmf-dist/scripts/texlive
That's strange, unless this file is dynamically generated,
It isn't.
I could not find it or any reference to it in the
texlive-source-20160605 distribution.
The "source" tarball for TL does not include the runtime files (hundreds
of megabytes of stuff), only the compilable sources.
> On 30 Oct 2016, at 23:58, Liviu Ionescu wrote:
>
>> mktexlsr.pl
That's strange, unless this file is dynamically generated, I could not find it
or any reference to it in the texlive-source-20160605 distribution.
Any idea where does it come from?
Liviu
> On 30 Oct 2016, at 23:40, Karl Berry wrote:
>
>Can't locate mktexlsr.pl
>
> mktexlsr.pl is (should be) in texmf-dist/scripts/texlive/mktexlsr.pl,
> which seems to be in your @INC. I can't explain it. Maybe your
> installation failed partway through.
>
> You can run mktexfmt pdfetex.fmt
Can't locate mktexlsr.pl
mktexlsr.pl is (should be) in texmf-dist/scripts/texlive/mktexlsr.pl,
which seems to be in your @INC. I can't explain it. Maybe your
installation failed partway through.
You can run mktexfmt pdfetex.fmt (or whatever) on its own to test.
I can't find the format
On 10/30/2016 2:31 PM, Liviu Ionescu wrote:
kpathsea: Running mktexfmt etex.fmt
Can't locate mktexlsr.pl in @INC (@INC contains:
/Users/ilg/Work/no-backup/texlive/tlpkg
/Users/ilg/Work/no-backup/texlive/texmf-dist/scripts/texlive
[...]
It looks like there's something wrong with your TeX Live in
> On 30 Oct 2016, at 20:25, Gavin Smith wrote:
>
> $ pdfetex /Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/doc/openocd.texi
>
> or
>
> $ etex /Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/doc/openocd.texi
>
> and see if a log file is created.
both commands fail with similar messages:
On 30 October 2016 at 17:43, Liviu Ionescu wrote:
>
>> On 30 Oct 2016, at 10:16, Gavin Smith wrote:
>>
>> ... Is etex creating a log file?
>
> apparently not.
>
> I tried with the following lines, from the openocd build:
>
> ilg-mbp:tmp ilg$ mkdir tex
> ilg-mbp:tmp ilg$ cd tex
> ilg-mbp:tex ilg$
> On 30 Oct 2016, at 10:16, Gavin Smith wrote:
>
> ... Is etex creating a log file?
apparently not.
I tried with the following lines, from the openocd build:
ilg-mbp:tmp ilg$ mkdir tex
ilg-mbp:tmp ilg$ cd tex
ilg-mbp:tex ilg$ export PATH=/Users/ilg/Work/no-backup/texlive/install/bin:$PATH
ilg
On 27 October 2016 at 23:08, Liviu Ionescu wrote:
> after some debugging sessions, it looks like texi2dvi expects etex to
> generate an output log, or something like this, and if this does not happen,
> fails with "TeX neither supports -recorder nor outputs \openout lines in its
> log file".
>
I'm running some builds which also create pdf manuals, and I ran into the
following problem:
Making install-pdf in doc
TEXINPUTS="/Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/doc:$TEXINPUTS" \
MAKEINFO='makeinfo -I
/Users/ilg/Work/openocd/gnuarmeclipse-openocd.git/doc' \
t
16 matches
Mail list logo
