[tex-live] installing with custom binaries & making it

[Кирилл К]

Thanks,  'bin/*/man' is really the symlink

My new question:

Make world fails with this:

top-level make world: running texlinks in texk/texlive/tl_scripts ...
cd texk/texlive/tl_scripts && make  run-texlinks
make[1]: Entering directory
'/home/pil/latex/buildtexlive/source/Work/texk/texlive/tl_scripts'
PATH="/bin/x86_64-linux:/opt/texlive/2014/bin/custom:/opt/texlive/2014/bin/custom:/usr/local/sbin:/usr/local/bin:/usr/bin:/usr/bin/vendor_perl:/usr/bin/core_perl";
export PATH; /bin/x86_64-linux/texlinks -v -f
/opt/texlive/2014/texmf-dist/web2c/fmtutil.cnf -e "" /bin/x86_64-linux
/bin/sh: /bin/x86_64-linux/texlinks: No such file or directory
Makefile:856: recipe for target 'run-texlinks' failed
make[1]: *** [run-texlinks] Error 127
make[1]: Leaving directory
'/home/pil/latex/buildtexlive/source/Work/texk/texlive/tl_scripts'
Makefile:1006: recipe for target 'world' failed
make: *** [world] Error 2

Sources were configured with:

...
--prefix=/opt/texlive/2014 \
--bindir=/opt/texlive/2014/bin/custom \
...

so texlinks placed in 'bin/custom' and '/bin/x86_64-linux' directory not
exist.

Where in makefiles (or anywhere else) is texlinks invoke string? Where is
this 856th line actualy?

Should I manualy edit it some something else?


2014-07-23 23:32 GMT+00:00 Karl Berry <karl at freefriends.org>:

>     What is 'make world' actually doing?
>
> If you look at the top-level Makefile.am, it will be obvious.
> It runs three submakes: install-strip run-texlinks check
> That is it.
>
>     make world' has 1 fail test (bibtexmem),
>     however 'make && make check' has no ones.
>
> I can only surmise your available memory is on the verge of being
> exhausted during the tests, and depending on what else is running at the
> time of the test, the allocation by bibtex may or may not succeed.
>
> I know that bibtex does do a "big" (by the standards of small devices)
> allocation when it starts up.  The failure of this test is not
> important, as a practical matter.  Perhaps we can change the test to
> reduce how much gets allocated.
>
>     - Installer script installed another copy of manpages to
>     bin/custom/man directory.
>
> As far as I know, what is installed is not a copy of anything, but a
> symbolic link from bin/*/man to .../texmf-dist/doc/man.  It happens in
> source/texk/texlive/linked_scripts/Makefile.am.
>
> This is for the sake of man programs that automatically look for man/
> entries in PATH directories, a nice feature.  This exists notably but
> not only on MacOSX.
>
>     Is it differs of manpages that comes with own-making binaries?
>
> Thus: no.
>
>     How to prevent of install these mans correctly (*perfectionism style*)?
>
> It is operating as intended, for good reason, so I don't agree with the
> description of "imperfect".
>
> If you have some personal distaste for this bin/man, that's fine; you
> can either set the environment variable TL_INSTALL_OMIT_MAN_LINK to
> anything non-null before (or when) running the build, or just rm it
> afterward.
>
> hope this helps,
> karl
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://tug.org/pipermail/tex-live/attachments/20140724/b4554547/attachment.html>