Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
Not eligible to see or edit group visibility for this bug.
View Bug Activity | Format For Printing | XML | Clone This Bug
Hi! I am submitting an ebuild for xindy - A Flexible Indexing System. It is very nice & robust package (binary) especially suited for international users. The proposed category is dev-tex/xindy. It's tested on amd64. Sincerely, Gour Reproducible: Always Steps to Reproduce: 1. 2. 3. Portage 2.0.51-r3 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r1 x86_64) ================================================================= System uname: 2.6.9-gentoo-r1 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.6.4 ccache version 2.3 [enabled] Autoconf: sys-devel/autoconf-2.59-r5 Automake: sys-devel/automake-1.8.5-r1 Binutils: sys-devel/binutils-2.15.92.0.2-r1 Headers: sys-kernel/linux26-headers-2.6.8.1-r1 Libtools: sys-devel/libtool-1.5.2-r5 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer -funroll-loops" CHOST="x86_64-pc-linux-gnu" COMPILER="" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/alias /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=k8 -O2 -pipe -fomit-frame-pointer -funroll-loops" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig buildpkg ccache distlocks sandbox" GENTOO_MIRRORS="ftp://gentoo.inode.at/source/ ftp://gd.tuwien.ac.at/opsys/linux/gentoo/ http://gentoo.inode.at/ http://gentoo.osuosl.org http://www.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/portage/local" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="X aalib acpi alsa amd64 arts audiofile avi berkdb bitmap-fonts cddb cdparanoia cdr crypt cups directfb doc dvd dvdr encode esd f77 fam fbcon flac foomaticdb fortran gdbm gif gimpprint gphoto2 gpm gtk gtk2 gtkhtml imagemagick imlib immqt innodb ipv6 java jp2 jpeg jpeg2k junit kde lcms libwww lzw lzw-tiff mad mmap motif mozilla mpeg multilib mysql ncurses nls nptl oggvorbis opengl oss pam pda perl pic png ppds python qt readline ruby scanner slang speex sqlite ssl svg tcltk tcpd tetex tiff truetype unicode usb userlocales vim-with-x xface xine xinerama xml xml2 xmms xpm xprint xrandr xv zlib"
Created an attachment (id=44158) [details] ebuild for xindy-2.2-rc1 pacakge Pls. put ebuild into your local overlay under dev-tex category. Tested on amd64, so pls. add your arch. Sincerely, Gour
Hi! There is a problem with submitted ebuild since xindy is linked with ncurses4 library (libncurses.so.4). I've tried to symlink with ncurses5, but it does not work. Pls. excuse me :-( I am trying to resolve the issue and will followup here. Sincerely, Gour
I would rather build xindy from source :) Could you provide an ebuild for xindy source?
> I would rather build xindy from source :) Me too :-) > Could you provide an ebuild for xindy source? It's not easy. Building xindy involves building patched version of clisp with some specific xindy plugins which are then built as a run-time engine. Moreover, those plugins are old (build with the clisp from March 2000 and cannot be compiled with modern clisp. Otoh, I'm on amd64 and already have enough troubles with building clisp alone (masked on amd64 :-) However there are some progress in an attempt to build those xindy-specific plugins with modern clisp (2.33), but I still consider more easy to just bundle xindy-runtime compiled for specific arch with the rest of the xindy distribution and it would already be success that we can have xindy in official Linux distribution. Now, although a very useful tool, at least for non-English users, it is still not widely adopted. If you have some skills, especially Lisp-oriented, please step in ;) Sincerely, Gour
New release (rc2) of xindy will be out any day. The prerelease has been unofficially made available on their website (see bug 1072469 in their bug tracker on sourceforge, it is closed now but contains link to a prerelease). This prerelease solves two problems: * xindy should no longer crash on newer kernels and newer glibc (more precisely the old clisp runtime used to crash on some setups), * xindy now compiles with modern day clisp versions Obviously the second point is why I am mentioning it here. It may make it easier to get a real source ebuild for xindy.
Hi! Thank you for the helpful info. These days I'm too busy to play with it, but as soon as find some free time-slot, I'll try to build xindy from the source. Sincerely, Gour
Hi! Thanks to the latest development, now we can build xindy from the source :-) I put together a xindy source distribution and latest version is alpha5 available at: http://dev.atmarama.org/xindy-2.3-alpha5.tar.gz and there is also abuild available: http://dev.atmarama.org/xindy-2.3_alpha5.ebuild. When working on the package, I thought the new release will increase version number, but the main maintainer told me that the new version will be 2.2. I did not want to change version numbers during the alpha releases, but the final release will be probably xindy-2.2-src.tar.gz. Until then, pls. test the package and we hope that soon there will be beta & final release available for including in the portage tree. The package is tested on amd64 platform. Sincerely, Gour
(From update of attachment 44158 [details]) Pls. dont' use this ebuild. Use the new one which build xindy from the source. Sincerely, Gour
Created an attachment (id=62531) [details] xindy-2.2_beta1.ebuild (build from the source) Hi! Here is the new ebuild for xindy (source distribution). The tarball is available (until final release) at: http://dev.atmarama.org/xindy-2.2-beta1.tar.gz Pls. report back if you encounter any problem or have success (I tested the package on x86_64.) Sincerely, Gour
(From update of attachment 62531 [details]) Hi! There is a new ebuild available which adds a new USE flag 'make-rules'. Sincerely, Gour
Created an attachment (id=62909) [details] xindy-2.2_beta2.ebuild We are getting closer to the final release and here is the new xindy-2.2_beta2.ebuild available. Sincerely, Gour
Hi Gour, I have problems with this release: it cannot parse the raw index file generated by latex for me. This used to work with the same unofficial relase a couple of month ago, just installed manually not by the ebuild. The problem may be caused by the fact that I running a unicode machine now (though the raw file is still plain ASCII as it used to be). Are you willing to try running your xindy on my raw file, to help in locating where the problem lies?
(In reply to comment #12) > Hi Gour, I have problems with this release: it cannot parse the raw index file > generated by latex for me. With 2.2_beta? > The problem may be caused by the fact that I running a unicode machine now >(though the raw file is still plain ASCII as it used to be). I'm also on Unicode machine (utf-8). > Are you willing to try running your xindy on my raw file, to help in locating > where the problem lies? Sure. Maybe you can also post your file on xindy list so that more users can try it out. Sincerely, Gour
The latest ebuild fails on my x86 machine, if the doc use flag is positive. Might be that it is caused by my tex configuration, but I have no clue by what precisely... ... (/usr/share/texmf/tex/latex/base/cp1252.def) ! Package inputenc Error: Keyboard character used is undefined (inputenc) in inputencoding `cp1252'. See the inputenc package documentation for explanation. Type H <return> for immediate help. ... l.27 ^^9e \,^^8e\\ ? klimt ~ # emerge info Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-r0, 2.6.11-gentoo-r9 i686) ================================================================= System uname: 2.6.11-gentoo-r9 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.13 ccache version 2.3 [enabled] dev-lang/python: 2.2.3-r5, 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -mcpu=pentium3 -march=pentium3 -msse" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-Os -mcpu=pentium3 -march=pentium3 -msse" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks fixpackages sandbox sfperms strict userpriv" GENTOO_MIRRORS="http://mirror.uni-c.dk/gentoo/ http://ftp.du.se/pub/os/gentoo ftp://mirror.nutsmaas.nl/gentoo/ http://mirror.gentoo.no/ http://ftp.linux.ee/pub/gentoo/distfiles/" LANG="pl_PL.utf8" LC_ALL="pl_PL.utf8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="x86 X alsa apm avi bash-completion berkdb bitmap-fonts bonobo cdr crypt cscope cups curl directfb dvd eds emboss encode esd fam fbcon flac foomaticdb fortran gd gdbm gif gnome gphoto2 gpm gstreamer gtk gtk2 gtkhtml guile imagemagick imlib java jpeg junit libg++ libwww mad mikmod motif mp3 mpeg ncurses nls nptl odbc ogg oggvorbis oss pam pdflib perl png python quicktime readline rtc ruby samba sdl slang speex spell ssl svga tcltk tcpd tetex tiff truetype truetype-fonts type1-fonts unicode vorbis wmf xine xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LDFLAGS, LINGUAS
Hi Andrzej! (In reply to comment #14) > The latest ebuild fails on my x86 machine, if the doc use flag is positive. > Might be that it is caused by my tex configuration, but I have no clue by what > precisely... > > ... > (/usr/share/texmf/tex/latex/base/cp1252.def) > > ! Package inputenc Error: Keyboard character used is undefined > (inputenc) in inputencoding `cp1252'. > > See the inputenc package documentation for explanation. > Type H <return> for immediate help. > ... > > l.27 ^^9e > \,^^8e\\ > ? Can you please join the xind list 'cause your problem is more connected with the xindy than with the building process. I'll post your problem to the xindy mailing list. otoh, I'm a little bit puzzled 'cause 'doc' flag has effect only on building of docs not on the working of xindy. So, do you have problem with xindy itself or with the building of the package with 'doc' flag enabled. Do you use latest ebuild? Can you try to remove all the old traces of xindy and start from a scratch? Sincerely, Gour
(In reply to comment #15) > Can you please join the xind list 'cause your problem is more connected with > the xindy than with the building process. > > I'll post your problem to the xindy mailing list. > > otoh, I'm a little bit puzzled 'cause 'doc' flag has effect only on building of > docs not on the working of xindy. > > So, do you have problem with xindy itself or with the building of the package > with 'doc' flag enabled. Sorry for the confusion. I have two problems: comment #12, which I am trying to report to xindy-discuss and comment #14, which is clearly a problem in the build process, so the first thing to try is to discuss it here. I should have included the header of the emerge not only the suffix, to make this clear that the TeX invocation comes form the ebuild. Apologize again for that. Another thing is that the e-build not only fails, but also does it in the usual TeX way to fail, entering interactive mode, which AFAIK is completely unacceptable for ebuilds. Perhaps we should consider forcing TeX in batchmode or something like that. > Do you use latest ebuild? yes, the latest one posted in this bug. > Can you try to remove all the old traces of xindy and start from a scratch? I believe I have tried that, with no success, though.
(In reply to comment #16) > Sorry for the confusion. I have two problems: comment #12, which I am trying to > report to xindy-discuss and comment #14, which is clearly a problem in the > build process, so the first thing to try is to discuss it here. OK. >I should have > included the header of the emerge not only the suffix, to make this clear that > the TeX invocation comes form the ebuild. Apologize again for that. No problem. > Another thing is that the e-build not only fails, but also does it in the usual > TeX way to fail, entering interactive mode, which AFAIK is completely > unacceptable for ebuilds. Perhaps we should consider forcing TeX in batchmode > or something like that. How to do that? I did not do anything special. Which tetex you have installed? > I believe I have tried that, with no success, though. OK. Take xindy tarball, run configure in a local ($HOME) directory and then try to execute 'make' in top-level/make-rules folder and see what happens and you can also email me log file of that 'make'. I simply cannot reproduce this 'doc' error here so need more info. xindy-related problem will probably be taken over by some xindy-expert on the list. Sincerely, Gour
Created an attachment (id=64974) [details] xindy-2.2_beta2-r1.ebuild Hi! Here is a new ebuild for xindy which does not use 'make-rules' use flag, i.e. we force dependence on tetex 'cause xindy without 'make-rules' package build is not complete. Sincerely, Gour
(From update of attachment 62909 [details]) Please use newer xindy-2.2_beta2-r1.ebuild Sincerely, Gour
I had two problems with the latest ebuild: 1) I suppose you forgot the "http:" in the source line. 2) It seems to my that a document is compiled using LaTeX. This needs some fonts using METAFONT sources which have to be compiled. This, however writes into /var/cache/fonts/tfm which is not allowed: Running mktextfm larm1000 ACCESS DENIED mkdir: /var/cache/fonts/tfm/lh Running mktextfm larm0900 ACCESS DENIED mkdir: /var/cache/fonts/tfm/lh -------------------------- ACCESS VIOLATION SUMMARY --------------------------- LOG FILE = "/var/log/sandbox/sandbox-dev-tex_-_xindy-2.2_beta2-r1-11770.log" mkdir: /var/cache/fonts/tfm/lh mkdir: /var/cache/fonts/tfm/lh -------------------------------------------------------------------------------- Calling mktextfm as a user before emerging solves that problem. Btw. it compiles on a x86 so you can add the corresponding keyword.
The ebuild fails, probably because of gcc 4. ... gcc -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -O -DUNICODE -DDYNAMIC_FFI -DNO_SIGSEGV -I. -Wl,-O1 -Wl,--sort-common -Wl,--as-needed -x none spvw.o spvwtabf.o spvwtabs.o spvwtabo.o eval.o control.o encoding.o pathname.o stream.o socket.o io.o array.o hashtabl.o list.o package.o record.o sequence.o charstrg.o debug.o error.o misc.o time.o predtype.o symbol.o lisparit.o i18n.o foreign.o unixaux.o ari80386.o modules.o libcharset.a libavcall.a libcallback.a -lreadline -lncurses -ldl -o lisp.run sync ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -norc -m 750KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit))" WARNING: *FOREIGN-ENCODING*: reset to ASCII C_CODE_ALIGNMENT is wrong. &PROG1 = 0x80652bb. Add -falign-functions=4 to CFLAGS in the Makefile. make[2]: *** [interpreted.mem] Aborted make[2]: Leaving directory `/var/tmp/portage/xindy-2.2_beta2-r1/work/xindy-2.2-beta2/rte/clisp-2.33.2/src' make[1]: *** [xindy.run] Error 2 make[1]: Leaving directory `/var/tmp/portage/xindy-2.2_beta2-r1/work/xindy-2.2-beta2/rte' make: *** [all-recursive] Error 1 !!! ERROR: dev-tex/xindy-2.2_beta2-r1 failed. Call stack: ebuild.sh, line 1546: Called dyn_compile ebuild.sh, line 937: Called src_compile xindy-2.2_beta2-r1.ebuild, line 25: Called die !!! Make failed !!! If you need support, post the topmost build error, and the call stack if relevant. !!! This ebuild is from an overlay: '/usr/local/portage' Satux ~ # emerge --info Portage 2.1.1 (default-linux/x86/2006.1, gcc-4.1.1, glibc-2.4-r3, 2.6.17-suspend2-r6 i686) ================================================================= System uname: 2.6.17-suspend2-r6 i686 Intel(R) Pentium(R) M processor 1.60GHz Gentoo Base System version 1.12.4 Last Sync: Wed, 13 Sep 2006 12:30:07 +0000 ccache version 2.3 [enabled] app-admin/eselect-compiler: [Not Present] dev-lang/python: 2.4.3-r1 dev-python/pycrypto: 2.0.1-r5 dev-util/ccache: 2.3 dev-util/confcache: [Not Present] sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2 sys-devel/binutils: 2.16.1-r3 sys-devel/gcc-config: 1.3.13-r3 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r5 ACCEPT_KEYWORDS="x86" ACCEPT_LICENSE="" ALSA_CARDS="intel8x0" ANT_HOME="/usr/share/ant-core" ARCH="x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CCACHE_DIR="/var/tmp/ccache" CCACHE_SIZE="1024M" CFLAGS="-march=pentium-m -O2 -fomit-frame-pointer -fno-ident -pipe" CHOST="i686-pc-linux-gnu" CLASSPATH="." CLEAN_DELAY="5" CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config" CONFIG_PROTECT_MASK="/etc/env.d /etc/gconf /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/texmf/web2c" CROSSCOMPILE_OPTS="" CVS_RSH="ssh" CXXFLAGS="-march=pentium-m -O2 -fomit-frame-pointer -fno-ident -pipe" DISPLAY=":0.0" DISTDIR="/usr/portage/distfiles" DVB_CARDS="" EDITOR="/usr/bin/emacs" ELIBC="glibc" EMERGE_DEFAULT_OPTS="-av" EMERGE_WARNING_DELAY="10" FCDSL_CARDS="" FEATURES="autoconfig ccache distlocks metadata-transfer sandbox sfperms strict" FETCHCOMMAND="/usr/bin/wget -t 5 -T 60 --passive-ftp -P ${DISTDIR} ${URI}" FOO2ZJS_DEVICES="" FRITZCAPI_CARDS="" GCC_SPECS="" GDK_USE_XFT="1" GDM_LANG="de_DE.utf8" GENTOO_MIRRORS="http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/" GUILE_LOAD_PATH="/usr/share/guile/1.6" G_BROKEN_FILENAMES="1" G_FILENAME_ENCODING="UTF-8" HOME="/root" INFOPATH="/usr/share/info:/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/info::/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/info:/usr/share/info/emacs-22.0.50" INPUT_DEVICES="keyboard mouse synaptics" JAVAC="/opt/sun-jdk-1.4.2.10/bin/javac" JAVA_HOME="/opt/sun-jdk-1.4.2.10" JDK_HOME="/opt/sun-jdk-1.4.2.10" KDEDIRS="/usr" KDE_IS_PRELINKED="1" KERNEL="linux" LANG="de_DE.utf8" LC_ALL="de_DE.utf8" LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--as-needed" LESS="-R -M --shift 5" LESSOPEN="|lesspipe.sh %s" LINGUAS="de" LIRC_DEVICES="" LOGNAME="root" MAKEOPTS="-j2" MANPATH="/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/i686-pc-linux-gnu/2.16.1/man::/usr/share/gcc-data/i686-pc-linux-gnu/4.1.1/man::/opt/sun-jdk-1.4.2.10/man:/usr/qt/3/doc/man" MISDN_CARDS="" OPENGL_PROFILE="xorg-x11" PAGER="/usr/bin/less" PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/opt/sun-jdk-1.4.2.10/bin:/opt/sun-jdk-1.4.2.10/jre/bin:/opt/sun-jdk-1.4.2.10/jre/javaws:/usr/kde/3.5/sbin:/usr/kde/3.5/bin:/usr/qt/3/bin" PKGDIR="/usr/portage/packages" PKG_CONFIG_PATH="/usr/qt/3/lib/pkgconfig" PORTAGE_ARCHLIST="ppc s390 amd64 ppc64 x86-fbsd m68k arm sparc sh mips ia64 alpha ppc-macos hppa x86" PORTAGE_BINHOST_CHUNKSIZE="3000" PORTAGE_BIN_PATH="/usr/lib/portage/bin" PORTAGE_CALLER="emerge" PORTAGE_CONFIGROOT="/" PORTAGE_DEBUG="0" PORTAGE_DEPCACHEDIR="/var/cache/edb/dep" PORTAGE_ELOG_CLASSES="log warn error" PORTAGE_ELOG_MAILFROM="portage" PORTAGE_ELOG_MAILSUBJECT="[portage] ebuild log for ${PACKAGE} on ${HOST}" PORTAGE_ELOG_MAILURI="root" PORTAGE_GID="250" PORTAGE_INST_GID="0" PORTAGE_INST_UID="0" PORTAGE_PYM_PATH="/usr/lib/portage/pym" PORTAGE_RSYNC_OPTS="--recursive --links --safe-links --perms --times --compress --force --whole-file --delete --delete-after --stats --timeout=180 --exclude='/distfiles' --exclude='/local' --exclude='/packages'" PORTAGE_RSYNC_RETRIES="3" PORTAGE_TMPDIR="/var/tmp" PORTAGE_WORKDIR_MODE="0700" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage /usr/portage/local/layman/sunrise /usr/portage/local/layman/science" PRELINK_PATH="" PRELINK_PATH_MASK="/lib/modules:/usr/lib/locale:/usr/lib/wine:/usr/lib/valgrind:*.la:*.png:*.py:*.pl:*.pm:*.sh:*.xml:*.xslt:*.a:*.js:/usr/lib/klibc" PWD="/root" PYTHONDOCS="/usr/share/doc/python-docs-2.4.3/html" PYTHONPATH="/usr/lib/portage/pym" QMAKESPEC="linux-g++" QTDIR="/usr/qt/3" RESUMECOMMAND="/usr/bin/wget -c -t 5 -T 60 --passive-ftp -P ${DISTDIR} ${URI}" ROOT="/" ROOTPATH="/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/usr/i686-pc-linux-gnu/gcc-bin/4.1.1:/opt/sun-jdk-1.4.2.10/bin:/opt/sun-jdk-1.4.2.10/jre/bin:/opt/sun-jdk-1.4.2.10/jre/javaws:/usr/kde/3.5/sbin:/usr/kde/3.5/bin:/usr/qt/3/bin" RPMDIR="/usr/portage/rpm" SHELL="/bin/bash" SHLVL="1" STAGE1_USE="nptl nptlonly unicode" SYNC="rsync://rsync.gentoo.org/gentoo-portage" TERM="xterm" USE="x86 X Xaw3d acpi alsa auctex avi bash-completion berkdb bitmap-fonts bzip2 cdparanoia cdr cjk cli crypt cups dbus dga dlloader doc dri dvd dvdr dvdread elibc_glibc emacs encode ffmpeg firefox flac fortran gd gdbm gif gpm gtk gtk2 hal ieee1394 imagemagick input_devices_keyboard input_devices_mouse input_devices_synaptics ipv6 isdnlog java javascript jpeg kde kdeenablefinal kdehiddenvisibility kernel_linux libg++ linguas_de mmx mp3 mpeg mplayer ncurses nls nocd nptl nptlonly nsplugin ogg openal opengl oss pam pcmcia pcre pdf pdflib perl plotutils png ppds pppd python qt3 quicktime readline reflection samba sdl session spell spl sse sse2 ssl svg svga tcpd tetex threads tiff truetype truetype-fonts type1-fonts udev unicode usb userland_GNU v4l v4l2 vcd video_cards_i810 vorbis win32codecs xcomposite xine xml xorg xvid zlib" USER="root" USERLAND="GNU" USE_EXPAND="CROSSCOMPILE_OPTS DVB_CARDS ELIBC FCDSL_CARDS FOO2ZJS_DEVICES FRITZCAPI_CARDS INPUT_DEVICES KERNEL LINGUAS LIRC_DEVICES MISDN_CARDS USERLAND VIDEO_CARDS" USE_EXPAND_HIDDEN="CROSSCOMPILE_OPTS ELIBC KERNEL USERLAND" USE_ORDER="env:pkg:conf:defaults" VIDEO_CARDS="i810" XARGS="xargs -r" XAUTHORITY="/root/.xauthfPdJKN" _="/usr/bin/emerge"
(In reply to comment #20) Pls. excuse me for late reply. I spent several months in India and was out of touch with xindy :-) > I had two problems with the latest ebuild: > > 1) I suppose you forgot the "http:" in the source line. True. I fixed this one in xindy-2.2_beta2-r2.ebuild which I include. > 2) It seems to my that a document is compiled using LaTeX. This needs some > fonts using METAFONT sources which have to be compiled. This, however writes > into /var/cache/fonts/tfm which is not allowed: > > Running mktextfm larm1000 > ACCESS DENIED mkdir: /var/cache/fonts/tfm/lh > Running mktextfm larm0900 > ACCESS DENIED mkdir: /var/cache/fonts/tfm/lh > > -------------------------- ACCESS VIOLATION SUMMARY --------------------------- > LOG FILE = "/var/log/sandbox/sandbox-dev-tex_-_xindy-2.2_beta2-r1-11770.log" > > mkdir: /var/cache/fonts/tfm/lh > mkdir: /var/cache/fonts/tfm/lh > -------------------------------------------------------------------------------- > > Calling mktextfm as a user before emerging solves that problem. > Well, atm, I cannot go deeper into this issue... > Btw. it compiles on a x86 so you can add the corresponding keyword. Added in r2 ebuild. Sincerely, Gour
Created an attachment (id=97914) [details] xindy-2.2_beta2-r2.ebuild Hi! Here is the new ebuild which adds ~x86 keyword and fixes the wrong SRC_URI line. Sincerely, Gour
(In reply to comment #21) > The ebuild fails, probably because of gcc 4. > Now I don't have time to take a closer look, but I just uploaded new tarball & new xindy-2.2_beta2-r2.ebuild which builds fine here with gcc-4.1.1. Pls. test & report back! Thank you for testing ebuild. I hope xindy will get released one day and become part of portage ;) Sincerely, Gour
The new ebuild still fails with the same message than previously reported. If I add -falign-functions=4 as instructed by the error message, it compiles fine. I suspect it has to do with some clisp dark magic. Do you know if it is possible to compile xindy with alternative lisp compilers like sbcl or cmucl? It would be better to have them as dependencies rather than rebuild (and install) clisp each time.
The problem is still here too. Maybe something with unicode (just a guess because of the error message)? Where did you add the cflag? I added it to my compiling cflags and it seems to be added to /var/tmp/portage/xindy-2.2_beta2-r2/work/xindy-2.2-beta2/Makefile but it did not work.
I don't think it's directly related to unicode, rather to the clisp implementation. Anyway, the CFLAG needs to be added to the xindy-2.2-beta2/rte/clisp-2.33.2/Makefile If you want to set it cleanly in the ebuild, you can inherit flag-o-matic.
(In reply to comment #25) > The new ebuild still fails with the same message than previously reported. If I > add -falign-functions=4 as instructed by the error message, it compiles fine. I > suspect it has to do with some clisp dark magic. Probably, but I never went much into clisp :-) > Do you know if it is possible to compile xindy with alternative lisp compilers > like sbcl or cmucl? It would be better to have them as dependencies rather >than rebuild (and install) clisp each time. I agree. However, taking into consideration previous situation, this is, imho, great achievement and the tarball is not so big. otoh, I do not have any knowledge abour clisp, so to fix this issue requires someone with some clisp knowledge. xindy uses some clisp stuff and if it can be provided by some other implementation, why not. My intention was (is) just to provide easy build, for the rest better go to xindy mailing list and/or contact Joachim - he is the expert. Sincerely, Gour >
(In reply to comment #26) > The problem is still here too. Maybe something with unicode (just a guess > because of the error message)? > > Where did you add the cflag? I added it to my compiling cflags and it seems to > be added to > /var/tmp/portage/xindy-2.2_beta2-r2/work/xindy-2.2-beta2/Makefile > but it did not work. > I cannot help with it - here it builds nicely on amd64 and I do not have access to any x86 machine :-( Maybe it is better to discuss it on xindy's mailing list? Sincerely, Gour
(In reply to comment #27) > I don't think it's directly related to unicode, rather to the clisp > implementation. Anyway, the CFLAG needs to be added to the > xindy-2.2-beta2/rte/clisp-2.33.2/Makefile > If you want to set it cleanly in the ebuild, you can inherit flag-o-matic. > Mmmh. I tried to use the functions but it is not included. It seems it ignores my use flags completly. Any idea? @Gour: Could you please put a now version of source code together? Joachim Schrod wrote that a new version fixed a bug concerning "| to break ligatures. I would need that... Thx!
(In reply to comment #30) > @Gour: Could you please put a now version of source code together? Joachim > Schrod wrote that a new version fixed a bug concerning "| to break ligatures. > I would need that... Thx! I just posted message to the xindy list to see what is current status of xindy and what is preventing official release. However, few days ago I moved to Arch Linux so won't maintain ebuild any longer, but if Arhc package can be prepared, it means that writing ebuild will be easy ;) Sincerely, Gour
Created an attachment (id=140263) [details] dev-tex/xindy/xindy-2.2_beta2.ebuild For me, clisp from this package don't compile. I use other version of clisp.
(In reply to comment #32) Hi! > Created an attachment (id=140263) [edit] [details] > dev-tex/xindy/xindy-2.2_beta2.ebuild > > For me, clisp from this package don't compile. > I use other version of clisp. Let me inform you that finally there is official xindy-2.3 release :-) Since summer I'm not using Gentoo and won't provide ebuild for it, but someone can just ump this ebuild. Sincerely, Gour
Gud news!
Created an attachment (id=140805) [details] xindy-2.3.ebuild This is an updated ebuild for xindy-2.3.ebuild based on Gours ebuild. I already included a use flag "clisp" to use an external clisp. This does not work for me, I get some compilation errors, but if anyone wants to try it and knows more about the real stuff he/she could try (already wrote to the xindy mailing list). To work, clisp-link must be executable which is not (at least for me), so I filed a bug report. With the clisp useflag, one needs the second version of my patch in #205387. Without clisp useflag everything runs like a charm.
Created an attachment (id=140824) [details] dev-tex/xindy/xindy-2.3.ebuild 1. Non-executable clisp-link --- this is bug of clisp.ebuild. 2. For me external clisp don't work too.
after all the external clisp problem was due to stripped files... added to the tree, thanks a lot !
