On Sun, Dec 18, 2016 at 03:08:56PM +0300, Vadim Zhukov wrote: > 2016-12-18 13:23 GMT+03:00 Antoine Jacoutot <ajacou...@bsdfrog.org>: > >> Yes, I've seen it, and that wasn't enough. > >> > >> Try to remove patch-texk_kpathsea_Makefile_in and > >> patch-texk_ptexenc_Makefile_in, make sure that GNU libtool is not > >> installed (I suspect it could interfere) and try to build > >> print/texlive/base. > > > > Just did. > > It built and packaged fine for me... > > > > $ cvs diff > > cvs server: cannot find patches/patch-texk_kpathsea_Makefile_in > > cvs server: cannot find patches/patch-texk_ptexenc_Makefile_in > > $ make clean && make package > > <...> > > ===> Building package for texlive_base-2015p0 > > Create /hack/cvs/ports/packages/amd64/all/texlive_base-2015p0.tgz > > <...> > > o_O now it builds fine for me as well. I've ever checked that I had > the same Link.pm installed initially, with snapshot... Installation of > GNU libtool doesn't change anything as well (minus one theory). > > It looks that the problem triggers _sometimes_. Because, well, the two > patches mentioned above won't be enough if libtool is really passing > -bindir argument through: two more unpatched Makefile.in files, > containing -bindir, are processed during build. I.e., that at some > point build failed due to -bindir, the Makefile.in was patched, then > it failed second time, another patch, and then went smoothly. > > So I'll try investigate things more. I've seen this a few times: > > libtool: link: cc -shared -fPIC -DPIC -o .libs/libtexlua52.so.0.0 > -Wimplicit -Wreturn-type-Wdeclaration-after-statement > -Wno-unknown-pragmas -O2 -pipe -bindir /usr/local/bi > n lua-5.2.4/src/.libs/lapi.o lua-5.2.4/src/.libs/lauxlib.o > lua-5.2.4/src/.libs/lbaselib.o lua-5.2.4/src/.libs/lbitlib.o > lua-5.2.4/src/.libs/lcode.o lua-5.2.4/src/.libs/lcor > olib.o lua-5.2.4/src/.libs/lctype.o lua-5.2.4/src/.libs/ldblib.o > lua-5.2.4/src/.libs/ldebug.o lua-5.2.4/src/.libs/ldo.o > lua-5.2.4/src/.libs/ldump.o lua-5.2.4/src/.libs/lfun > c.o lua-5.2.4/src/.libs/lgc.o lua-5.2.4/src/.libs/linit.o > lua-5.2.4/src/.libs/liolib.o lua-5.2.4/src/.libs/llex.o > lua-5.2.4/src/.libs/lmathlib.o lua-5.2.4/src/.libs/lmem.o > lua-5.2.4/src/.libs/loadlib.o lua-5.2.4/src/.libs/lobject.o > lua-5.2.4/src/.libs/lopcodes.o lua-5.2.4/src/.libs/loslib.o > lua-5.2.4/src/.libs/lparser.o lua-5.2.4/src/.libs/ls > tate.o lua-5.2.4/src/.libs/lstring.o lua-5.2.4/src/.libs/lstrlib.o > lua-5.2.4/src/.libs/ltable.o lua-5.2.4/src/.libs/ltablib.o > lua-5.2.4/src/.libs/ltm.o lua-5.2.4/src/.libs/ > lundump.o lua-5.2.4/src/.libs/lvm.o lua-5.2.4/src/.libs/lzio.o -L.libs -lm > cc: unrecognized option '-bindir' > /usr/local/bin: file not recognized: Is a directory > collect2: ld returned 1 exit status > Error while executing cc -shared -fPIC -DPIC -o > .libs/libtexlua52.so.0.0 -Wimplicit -Wreturn-type > -Wdeclaration-after-statement -Wno-unknown-pragmas -O2 -pipe -bindir > /usr/ > local/binlua-5.2.4/src/.libs/lapi.o lua-5.2.4/src/.libs/lauxlib.o > lua-5.2.4/src/.libs/lbaselib.o lua-5.2.4/src/.libs/lbitlib.o > lua-5.2.4/src/.libs/lcode.o lua-5.2.4/src/.li > bs/lcorolib.o lua-5.2.4/src/.libs/lctype.o > lua-5.2.4/src/.libs/ldblib.o lua-5.2.4/src/.libs/ldebug.o > lua-5.2.4/src/.libs/ldo.o lua-5.2.4/src/.libs/ldump.o > lua-5.2.4/src/.li > bs/lfunc.o lua-5.2.4/src/.libs/lgc.o lua-5.2.4/src/.libs/linit.o > lua-5.2.4/src/.libs/liolib.o lua-5.2.4/src/.libs/llex.o > lua-5.2.4/src/.libs/lmathlib.o lua-5.2.4/src/.libs/ > lmem.o lua-5.2.4/src/.libs/loadlib.o lua-5.2.4/src/.libs/lobject.o > lua-5.2.4/src/.libs/lopcodes.o lua-5.2.4/src/.libs/loslib.o > lua-5.2.4/src/.libs/lparser.o lua-5.2.4/src/. > libs/lstate.o lua-5.2.4/src/.libs/lstring.o > lua-5.2.4/src/.libs/lstrlib.o lua-5.2.4/src/.libs/ltable.o > lua-5.2.4/src/.libs/ltablib.o lua-5.2.4/src/.libs/ltm.o lua-5.2.4/src > /.libs/lundump.o lua-5.2.4/src/.libs/lvm.o lua-5.2.4/src/.libs/lzio.o > -L.libs -lm > > And those were gone after tweaking Link.pm, so I got pretty sure the > problem was in there. Now I'd better to shut up and try to get more > details. Please disregard the patch... > > Oh, and what about whacking the two patches from print/texlive/base > mentioned above? :)
Yeah I am fine with that :-) -- Antoine
