https://bugzilla.novell.com/show_bug.cgi?id=426392
User dieter.jurzitza@t-online.de added comment
https://bugzilla.novell.com/show_bug.cgi?id=426392#c34
Dieter Jurzitza changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dieter.jurzitza@t-online.de
--- Comment #34 from Dieter Jurzitza 2008-12-03 02:59:19 MST ---
Building latest texlive from repositories/Publishing on one of my 64-Bit
platforms always gives me an error (2008 - 9.1):
rm -f libpdf.a
ar rc libpdf.a epdf.o mapfile.o utils.o vfpacket.o pkin.o writefont.o writet1.
ranlib libpdf.a
make[3]: Leaving directory `/usr/src/packages/BUILD/texlive/texk/web2c/pdftexdi
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I./.. -I../../libs/obsdcompat -I../../libs/
/bin/sh ../libtool --mode=link g++ -o pdftex -Wl,-warn-common -Wl,-warn-common
g++ -o pdftex -Wl,-warn-common -Wl,-warn-common pdftexini.o pdftex0.o pdftex1.o
/usr/lib/libpng12.so: could not read symbols: File in wrong format
collect2: ld returned 1 exit status
make[2]: *** [pdftex] Fehler 1
make[2]: Leaving directory `/usr/src/packages/BUILD/texlive/texk/web2c'
make[1]: *** [all] Fehler 1
make[1]: Leaving directory `/usr/src/packages/BUILD/texlive/texk'
make: *** [all] Fehler 1
error: Bad exit status from /var/tmp/rpm-tmp.21506 (%build)
the reason is that /usr/lib/libpng12.so is used instead of
/usr/lib64/libpng12.so. If I manually patch libtool in texlive/texk directory
so that the paths point to /usr/lib64, things are working, however, this is not
the way it is meant to be.
/etc/ld.so.conf looks ok. This is a machine that had had been upgraded from
10.3, another system with a similar configuration but fresh 11.0 install does
not show this behaviour. Anything you know of I could have made wrong? If you
need the full log, please let me know. I have the output
rpmbuild -ba texlive.spec > log 2>&1 at hand.
Take care
Dieter Jurzitza
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.