Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 31921 - lyx-1.3.3 ebuild fails image install
Summary: lyx-1.3.3 ebuild fails image install
Status: RESOLVED WORKSFORME
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High normal
Assignee: Text-Markup Team (OBSOLETE)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-24 08:11 UTC by David King
Modified: 2004-02-24 12:41 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments
emerge log for lyx-1.3.3 (lyx.log.bz2,26.57 KB, application/x-bzip2)
2003-11-04 04:14 UTC, David King
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David King 2003-10-24 08:11:45 UTC
The ebuild seems to compile OK, but when it comes to installing the results prior to a 
merge into the target system something breaks. Looking at the work directory, the 
../lyx-1.3.3/image/usr/share/lyx/xfonts directory does not appear to have been created 
earlier in the install script. 

Reproducible: Always
Steps to Reproduce:
1.emerge app-office/lyx-1.3.3		 
2. 
3. 
Actual Results:  
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/bind 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/clipart 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/doc 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/examples 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/help 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/images 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/images/math 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/kbd 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/layouts 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/lyx2lyx 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/scripts 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/templates 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/tex 
mkdir /tmp/portage/lyx-1.3.3/image/usr/share/lyx/ui 
files=`cd . ; echo configure configure.cmd scripts/* lyx2lyx/*` ; \ 
for i in ${files} ; do \ 
   /bin/install -c ./$i /tmp//portage/lyx-1.3.3/image//usr/share/lyx/$i ; \ 
done 
test -f xfonts/fonts.dir || exit 0 ; \ 
/bin/sh ../config/mkinstalldirs /tmp//portage/lyx-1.3.3/image//usr/share/lyx/xfonts ; \ 
files=`sed -e 's/^[0-9]*$//' -e 's/^\([^ ]*\) .*$/\1/' xfonts/fonts.dir` ; \ 
for i in ${files} ; do \ 
  ln -f -s `kpsewhich $i` /tmp//portage/lyx-1.3.3/image//usr/share/lyx/xfonts/$i ; \ 
done ; \ 
/bin/install -c -m 644 xfonts/fonts.dir 
/tmp//portage/lyx-1.3.3/image//usr/share/lyx/xfonts/fonts.dir ; \ 
/bin/install -c -m 644 xfonts/fonts.scale 
/tmp//portage/lyx-1.3.3/image//usr/share/lyx/xfonts/fonts.scale 
test -f xfonts/PSres.upr && /bin/install -c -m 644 xfonts/PSres.upr 
/tmp//portage/lyx-1.3.3/image//usr/share/lyx/xfonts/PSres.upr 
make[3]: *** [install-xfonts] Error 1 
make[3]: Leaving directory `/tmp/portage/lyx-1.3.3/work/lyx-1.3.3/lib' 
make[2]: *** [install-am] Error 2 
make[2]: Leaving directory `/tmp/portage/lyx-1.3.3/work/lyx-1.3.3/lib' 
make[1]: *** [install-recursive] Error 1 
make[1]: Leaving directory `/tmp/portage/lyx-1.3.3/work/lyx-1.3.3/lib' 
make: *** [install-recursive] Error 1 
 
!!! ERROR: app-office/lyx-1.3.3 failed. 
!!! Function einstall, Line 361, Exitcode 2 
!!! einstall failed 

Expected Results:  
sucessful compile and merge 

Portage 2.0.49-r15 (default-x86-1.4, gcc-3.3.1, glibc-2.3.2-r6, 2.4.20-gaming-r5) 
================================================================= 
System uname: 2.4.20-gaming-r5 i686 AMD Athlon(tm) XP 2100+ 
Gentoo Base System version 1.4.3.11 
ACCEPT_KEYWORDS="x86 ~x86" 
AUTOCLEAN="yes" 
CFLAGS="-march=athlon-xp -O3 -pipe" 
CHOST="i686-pc-linux-gnu" 
COMPILER="gcc3" 
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config 
/usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config /var/qmail/control 
/var/qmail/alias" 
CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" 
CXXFLAGS="-march=athlon-xp -O3 -pipe" 
DISTDIR="/usr/portage/distfiles" 
FEATURES="ccache autoaddcvs sandbox userpriv" 
GENTOO_MIRRORS="http://www.mirror.ac.uk/sites/www.ibiblio.org/gentoo/ 
http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo" 
MAKEOPTS="-j2" 
PKGDIR="/usr/portage/packages" 
PORTAGE_TMPDIR="/tmp/" 
PORTDIR="/usr/portage" 
PORTDIR_OVERLAY="" 
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" 
USE="x86 oss avi crypt cups encode foomaticdb gif jpeg libg++ mad mikmod mpeg 
ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gdbm berkdb slang 
readline arts nas svga tcltk java ruby mysql X sdl gpm tcpd pam libwww ssl perl python 
imlib oggvorbis gtk qt kde motif opengl acpi acpi4linux alsa ethereal gtk2 imap innodb 
jikes maildir md5sum nptl odbc samba slp sse tetex type1 apm -gnome"
Comment 1 Mike Gardiner (RETIRED) gentoo-dev 2003-10-26 01:22:37 UTC
/bin/sh ../config/mkinstalldirs /tmp//portage/lyx-1.3.3/image//usr/share/lyx/xfonts
; \ should definitely make the install directory and it seems to work fine
for me. following the install-xfonts target i cant see anything wrong. could
you remerge with -j1 and we might be able to see exactly what's causing the
error ? also, what version of automake are you using ?
Comment 2 Mike Gardiner (RETIRED) gentoo-dev 2003-11-03 19:59:55 UTC
reporter ping. can you also merge with MAKEOPTS="-j1" and provide a build
log? thanks
Comment 3 David King 2003-11-04 04:14:26 UTC
Created attachment 20248 [details]
emerge log for lyx-1.3.3
Comment 4 Mamoru KOMACHI (RETIRED) gentoo-dev 2004-02-23 10:34:01 UTC
Do you have the same error with recently committed lynx-1.3.4?
Also, do you mount /tmp or /var/tmp with noexec option? If so,
I guess it may cause an error like this.
Comment 5 David King 2004-02-24 07:31:18 UTC
emerge for lyx-1.3.4 merges OK, and seems to work as well.
Comment 6 Mamoru KOMACHI (RETIRED) gentoo-dev 2004-02-24 12:41:52 UTC
alright, I mark the bug as WORKSFORME because I never have this
problem and now you don't have it with 1.3.4. As I see your log,
the directory should be created and I don't understand why it
failed... (So there isn't much that we can do for it)

Please reopen this bug if you happen to have the same bug in
the future release.