| View previous topic :: View next topic |
| Author |
Message |
uglyman
Apprentice
Joined: 21 Apr 2002
Posts: 216
Location: Seattle, WA USA
|
 Posted: Tue Sep 10, 2002 7:12 pm Post subject: cant emerge libmng or devfsd |
 |
|
In the last few days I added a bunch of USE settings. I have been using this gentoo install for months and I love it... but I didn't really understand a lot of it when I started. I am about ready to start a new install but I don't have time to mess with it right now. I didn't really understand what all my options were for the USE settings when I installed. SO I added the ones that I wanted and then tried an
of course I updated my portage tree before I started because I figured if I was going to be compiling all those packages I might as well get the newest ones
when it got to libmng I had some problems, Here is the output from emerge libmng:
| Code: |
Calculating dependencies \>>> Unpacking source...
>>> Unpacking libmng-1.0.3.tar.gz
>>> Source unpacked.
creating cache ./config.cache
checking for a BSD compatible install... /bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... yes
checking for working aclocal... found
checking for working autoconf... found
checking for working automake... found
checking for working autoheader... found
checking for working makeinfo... found
checking for gcc... gcc
checking whether the C compiler (gcc -march=i686 -O3 -pipe ) works... yes
checking whether the C compiler (gcc -march=i686 -O3 -pipe ) is a cross-compiler... no
checking whether we are using GNU C... yes
checking whether gcc accepts -g... yes
checking for POSIXized ISC... no
checking for gcc option to accept ANSI C... none needed
checking how to run the C preprocessor... gcc -E
checking for function prototypes... yes
checking host system type... i686-pc-linux-gnu
checking build system type... i686-pc-linux-gnu
checking for ranlib... ranlib
checking for ld used by GCC... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
updating cache ./config.cache
checking for object suffix... o
checking for executable suffix... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.lo... yes
checking if gcc supports -fno-rtti -fno-exceptions ... yes
checking if gcc static flag -static works... -static
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking whether the linker (/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking command to parse /usr/bin/nm -B output... ok
checking how to hardcode library paths into programs... immediate
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking dynamic linker characteristics... Linux ld.so
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for objdir... .libs
creating libtool
loading cache ./config.cache
checking for a BSD compatible install... /bin/install -c
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for _LARGEFILE_SOURCE value needed for large files... 1
checking for _LARGE_FILES value needed for large files... no
checking for _XOPEN_SOURCE value needed for large files... no
checking for ANSI C header files... yes
checking for working const... yes
checking for pow... no
checking for pow in -lm... yes
checking for zlib.h... yes
checking for gzread in -lz... yes
checking for jpeglib.h... yes
checking for jpeg_read_header in -ljpeg... yes
checking for lcms/lcms.h... yes
checking for cmsCreateRGBProfile in -llcms... yes
updating cache ./config.cache
creating ./config.status
creating Makefile
/bin/sh ./libtool --mode=compile gcc -DPACKAGE=\"libmng\" -DVERSION=\"1.0.3\" -DPROTOTYPES=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 -DSTDC_HEADERS=1 -DMNG_SUPPORT_FULL=1 -DMNG_SUPPORT_READ=1 -DMNG_SUPPORT_WRITE=1 -DMNG_SUPPORT_DISPLAY=1 -DMNG_ACCESS_CHUNKS=1 -DMNG_ERROR_TELLTALE=1 -DHAVE_LIBZ=1 -DHAVE_LIBJPEG=1 -DHAVE_LIBLCMS=1 -DMNG_FULL_CMS=1 -I. -I. -march=i686 -O3 -pipe -c libmng_callback_xs.c
mkdir .libs
gcc -DPACKAGE=\"libmng\" -DVERSION=\"1.0.3\" -DPROTOTYPES=1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE=1 -DSTDC_HEADERS=1 -DMNG_SUPPORT_FULL=1 -DMNG_SUPPORT_READ=1 -DMNG_SUPPORT_WRITE=1 -DMNG_SUPPORT_DISPLAY=1 -DMNG_ACCESS_CHUNKS=1 -DMNG_ERROR_TELLTALE=1 -DHAVE_LIBZ=1 -DHAVE_LIBJPEG=1 -DHAVE_LIBLCMS=1 -DMNG_FULL_CMS=1 -I. -I. -march=i686 -O3 -pipe -c libmng_callback_xs.c -fPIC -DPIC -o .libs/libmng_callback_xs.lo
...done!
>>> emerge media-libs/libmng-1.0.3 to /
>>> md5 ;-) libmng-1.0.3.tar.gz
!!! emerge aborting on /usr/portage/media-libs/libmng/libmng-1.0.3.ebuild .
In file included from libmng.h:306,
from libmng_callback_xs.c:48:
libmng_types.h:366: parse error before `mng_cmsprof'
libmng_types.h:366: warning: data definition has no type or storage class
libmng_types.h:367: parse error before `mng_cmstrans'
libmng_types.h:367: warning: data definition has no type or storage class
libmng_types.h:368: parse error before `mng_CIExyY'
libmng_types.h:368: warning: data definition has no type or storage class
libmng_types.h:369: parse error before `mng_CIExyYTRIPLE'
libmng_types.h:369: warning: data definition has no type or storage class
libmng_types.h:370: parse error before `mng_gammatabp'
libmng_types.h:370: warning: data definition has no type or storage class
In file included from libmng_callback_xs.c:49:
libmng_data.h:246: parse error before `mng_cmsprof'
libmng_data.h:246: warning: no semicolon at end of struct or union
libmng_data.h:247: warning: data definition has no type or storage class
libmng_data.h:248: parse error before `hProf3'
libmng_data.h:248: warning: data definition has no type or storage class
libmng_data.h:249: parse error before `hTrans'
libmng_data.h:249: warning: data definition has no type or storage class
libmng_data.h:691: parse error before `}'
libmng_data.h:691: warning: data definition has no type or storage class
libmng_data.h:693: parse error before `*'
libmng_data.h:693: warning: data definition has no type or storage class
libmng_data.h:701: parse error before `pData'
libmng_data.h:702: parse error before `pData'
libmng_data.h:703: parse error before `pData'
libmng_data.h:704: parse error before `pData'
libmng_data.h:705: parse error before `pData'
libmng_data.h:706: parse error before `pData'
libmng_data.h:707: parse error before `pData'
libmng_data.h:708: parse error before `pData'
libmng_data.h:709: parse error before `pData'
libmng_data.h:710: parse error before `pData'
libmng_data.h:712: parse error before `pData'
libmng_data.h:719: parse error before `pData'
In file included from libmng_callback_xs.c:50:
libmng_error.h:59: parse error before `pData'
libmng_error.h:64: parse error before `pData'
libmng_callback_xs.c: In function `mng_setcb_memalloc':
libmng_callback_xs.c:74: parse error before `hHandle'
libmng_callback_xs.c:75: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_memfree':
libmng_callback_xs.c:95: parse error before `hHandle'
libmng_callback_xs.c:96: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_openstream':
libmng_callback_xs.c:116: parse error before `hHandle'
libmng_callback_xs.c:117: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_closestream':
libmng_callback_xs.c:137: parse error before `hHandle'
libmng_callback_xs.c:138: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_readdata':
libmng_callback_xs.c:158: parse error before `hHandle'
libmng_callback_xs.c:159: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_writedata':
libmng_callback_xs.c:179: parse error before `hHandle'
libmng_callback_xs.c:180: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_errorproc':
libmng_callback_xs.c:199: parse error before `hHandle'
libmng_callback_xs.c:200: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processheader':
libmng_callback_xs.c:240: parse error before `hHandle'
libmng_callback_xs.c:241: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processtext':
libmng_callback_xs.c:261: parse error before `hHandle'
libmng_callback_xs.c:262: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processsave':
libmng_callback_xs.c:282: parse error before `hHandle'
libmng_callback_xs.c:283: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processseek':
libmng_callback_xs.c:303: parse error before `hHandle'
libmng_callback_xs.c:304: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processneed':
libmng_callback_xs.c:324: parse error before `hHandle'
libmng_callback_xs.c:325: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processmend':
libmng_callback_xs.c:345: parse error before `hHandle'
libmng_callback_xs.c:346: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processunknown':
libmng_callback_xs.c:366: parse error before `hHandle'
libmng_callback_xs.c:367: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_processterm':
libmng_callback_xs.c:387: parse error before `hHandle'
libmng_callback_xs.c:388: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_getcanvasline':
libmng_callback_xs.c:408: parse error before `hHandle'
libmng_callback_xs.c:409: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_getbkgdline':
libmng_callback_xs.c:429: parse error before `hHandle'
libmng_callback_xs.c:430: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_getalphaline':
libmng_callback_xs.c:450: parse error before `hHandle'
libmng_callback_xs.c:451: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_refresh':
libmng_callback_xs.c:471: parse error before `hHandle'
libmng_callback_xs.c:472: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_gettickcount':
libmng_callback_xs.c:492: parse error before `hHandle'
libmng_callback_xs.c:493: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_setcb_settimer':
libmng_callback_xs.c:513: parse error before `hHandle'
libmng_callback_xs.c:514: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_memalloc':
libmng_callback_xs.c:642: parse error before `hHandle'
libmng_callback_xs.c:648: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_memfree':
libmng_callback_xs.c:661: parse error before `hHandle'
libmng_callback_xs.c:667: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_readdata':
libmng_callback_xs.c:680: parse error before `hHandle'
libmng_callback_xs.c:686: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_openstream':
libmng_callback_xs.c:699: parse error before `hHandle'
libmng_callback_xs.c:705: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_closestream':
libmng_callback_xs.c:718: parse error before `hHandle'
libmng_callback_xs.c:724: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_writedata':
libmng_callback_xs.c:737: parse error before `hHandle'
libmng_callback_xs.c:743: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_errorproc':
libmng_callback_xs.c:755: parse error before `hHandle'
libmng_callback_xs.c:761: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processheader':
libmng_callback_xs.c:792: parse error before `hHandle'
libmng_callback_xs.c:798: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processtext':
libmng_callback_xs.c:811: parse error before `hHandle'
libmng_callback_xs.c:817: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processsave':
libmng_callback_xs.c:830: parse error before `hHandle'
libmng_callback_xs.c:836: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processseek':
libmng_callback_xs.c:849: parse error before `hHandle'
libmng_callback_xs.c:855: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processneed':
libmng_callback_xs.c:868: parse error before `hHandle'
libmng_callback_xs.c:874: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processmend':
libmng_callback_xs.c:887: parse error before `hHandle'
libmng_callback_xs.c:893: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processunknown':
libmng_callback_xs.c:906: parse error before `hHandle'
libmng_callback_xs.c:912: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_processterm':
libmng_callback_xs.c:925: parse error before `hHandle'
libmng_callback_xs.c:931: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_getcanvasline':
libmng_callback_xs.c:944: parse error before `hHandle'
libmng_callback_xs.c:950: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_getbkgdline':
libmng_callback_xs.c:963: parse error before `hHandle'
libmng_callback_xs.c:969: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_getalphaline':
libmng_callback_xs.c:982: parse error before `hHandle'
libmng_callback_xs.c:988: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_refresh':
libmng_callback_xs.c:1001: parse error before `hHandle'
libmng_callback_xs.c:1007: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_gettickcount':
libmng_callback_xs.c:1020: parse error before `hHandle'
libmng_callback_xs.c:1026: parse error before `hHandle'
libmng_callback_xs.c: In function `mng_getcb_settimer':
libmng_callback_xs.c:1039: parse error before `hHandle'
libmng_callback_xs.c:1045: parse error before `hHandle'
make: *** [libmng_callback_xs.lo] Error 1
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_compile, Line -207, Exitcode 2
!!! (no error message)
|
I don't really even know what libmng is so I thought maybe I could keep using whatever old version I have.... but I wanted to continue to continue my emerge -u world. There might (probably) be a better way to do this, but I don't know what it is (maybe with inject?). What I did was figure out what package dep was making libmng get installed (using qpkg) and then I emerged that package with --nodeps (libmng wasn't in my /var/cache/edb/world).
this let me continue my emerge -u world and I figured I would fix libmng later.
then I got to devfsd and this happened:
| Code: |
Calculating dependencies \>>> Unpacking source...
>>> Unpacking devfsd-v1.3.25.tar.gz
>>> Source unpacked.
cc -march=i686 -O3 -pipe -I. -I/usr/src/linux/include -Wall -DLIBNSL="\"/lib/libnsl.so.1\"" -c -o devfsd.o devfsd.c
cc -march=i686 -O3 -pipe -I. -I/usr/src/linux/include -Wall -DLIBNSL="\"/lib/libnsl.so.1\"" -c -o expression.o expression.c
cc -march=i686 -O3 -pipe -I. -I/usr/src/linux/include -Wall -DLIBNSL="\"/lib/libnsl.so.1\"" -c -o compat_name.o compat_name.c
cc -march=i686 -O3 -pipe -o devfsd devfsd.o expression.o compat_name.o -export-dynamic -ldl
>>> Install devfsd-1.3.25 into /var/tmp/portage/devfsd-1.3.25/image/ category sys-apps
if [ ! -e /var/tmp/portage/devfsd-1.3.25/image//sbin ]; then mkdir -p /var/tmp/portage/devfsd-1.3.25/image//sbin; fi
rm -f /var/tmp/portage/devfsd-1.3.25/image//sbin/devfsd
install -s devfsd /var/tmp/portage/devfsd-1.3.25/image//sbin/devfsd
if [ ! -e /var/tmp/portage/devfsd-1.3.25/image//usr/share/man/man5 ]; then mkdir -p /var/tmp/portage/devfsd-1.3.25/image//usr/share/man/man5; fi
if [ ! -e /var/tmp/portage/devfsd-1.3.25/image//usr/share/man/man8 ]; then mkdir -p /var/tmp/portage/devfsd-1.3.25/image//usr/share/man/man8; fi
rm -f /var/tmp/portage/devfsd-1.3.25/image//usr/share/man/*/devfsd.*
cp -p devfsd.8 /var/tmp/portage/devfsd-1.3.25/image//usr/share/man/man8
...done!
>>> emerge sys-apps/devfsd-1.3.25 to /
>>> md5 ;-) devfsd-v1.3.25.tar.gz
!!! emerge aborting on /usr/portage/sys-apps/devfsd/devfsd-1.3.25.ebuild .
install: setting permissions for `/var/tmp/portage/devfsd-1.3.25/image//sbin/devfsd': Unknown error 524
cp: `devfsd.8': Unknown error 524
make: *** [install] Error 1
!!! ERROR: The ebuild did not complete successfully.
!!! Function src_install, Line 2, Exitcode 2
!!! (no error message)
|
near as I can tell with my limited knowledge of qpkg these two packages do not depend on each other. I have tried everything I can think of to get them to install. I am out of ideas short of cracking the src open and taking a look, which probably wouldn't mean anything to a guy like me anyway.
any suggestions?
thanks a lot, sorry for the long post... trying to give all the needed info.
later
uglyman |
|
| Back to top |
|
 |
uglyman
Apprentice
Joined: 21 Apr 2002
Posts: 216
Location: Seattle, WA USA
|
| Posted: Wed Sep 11, 2002 3:26 am Post subject: found devfsd prob in make file? |
|
|
OK!!!
had to tell this story because I am so proud of myself... I tried to call up the only guy I know who would understand what I was talking about and he wasn't there.....
I fixed my problem with the devfsd ebuild! 
this one really had me going but I was super focused like a zombie in front of my computer all day... I looked kind of like this guy 
anyway I think either we have a problem with this ebuild... or there is something wrong with the permissions in my man dir somehow. This is very possible because I can't get the man pages to open on portage or emerge which I could swear used to work. Please understand that I really don't know much about this stuff, this morning I hardly understood ebuild files at all. Now I am starting to get it. Also I have never had to mess with a make file before. SO this solution is a little ugly but I think it is a good tip for a quick test of what the problem is.......
the newest ebuild (at least as of this morning) for devfsd looks like this:
| Code: | # Copyright 1999-2002 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License, v2 or later
# $Header: /home/cvsroot/gentoo-x86/sys-apps/devfsd/devfsd-1.3.25.ebuild,v 1.6 2002/08/14 03:19:50 murphy Exp $
S=${WORKDIR}/${PN}
DESCRIPTION="Daemon for the Linux Device Filesystem"
SRC_URI="ftp://ftp.atnf.csiro.au/pub/people/rgooch/linux/daemons/devfsd/devfsd-v${PV}.tar.gz"
HOMEPAGE="http://www.atnf.csiro.au/~rgooch/linux/"
KEYWORDS="x86 ppc sparc sparc64"
SLOT="0"
LICENSE="GPL-2"
DEPEND="virtual/glibc"
src_unpack() {
unpack ${A}
cd ${S}
cp GNUmakefile GNUmakefile.orig
sed -e "s:-O2:${CFLAGS}:g" \
-e 's:/usr/man:/usr/share/man:' \
-e '29,31d;11,16d' -e '6c\' \
-e 'DEFINES := -DLIBNSL="\\"/lib/libnsl.so.1\\""' \
GNUmakefile.orig > GNUmakefile
}
src_compile() {
make || die
}
src_install() {
dodir /sbin /usr/share/man /etc
make PREFIX=${D} install || die
#config file is handled in baselayout
rm -f ${D}/etc/devfsd.conf
dodoc devfsd.conf COPYING* INSTALL
}
|
I started poking around in the directory where the source is unpacked and it was all left since the thing would error out in mid merge. I started looking at the GNUmakefile which seems to be created by the sed statement in the src_unpack section of the ebuild.
I figured out that running a plain old make caused no errors. it was make install that caused the problems and I finally figured out that it was happening when the make file tried to cp -p the man pages into the right dir for my system.
the file GNUmakefile that is created by the ebuild looks like this:
| Code: | PREFIX =
SBINDIR = $(PREFIX)/sbin
MANDIR = $(PREFIX)/usr/share/man
CONFDIR = $(PREFIX)/etc
CONFIG_FILE = $(CONFDIR)/devfsd.conf
DEFINES := -DLIBNSL="\"/lib/libnsl.so.1\""
ifndef KERNEL_DIR
KERNEL_DIR = /usr/src/linux
endif
all: devfsd rpm.spec
OBJECTS = devfsd.o expression.o compat_name.o
CFLAGS = -march=i686 -O3 -pipe -I. -I$(KERNEL_DIR)/include -Wall $(CEXTRAS) $(DEFINES)
devfsd: $(OBJECTS)
$(CC) -march=i686 -O3 -pipe -o devfsd $(OBJECTS) $(LDFLAGS) -export-dynamic -ldl
install: devfsd
if [ ! -e $(SBINDIR) ]; then mkdir -p $(SBINDIR); fi
rm -f $(SBINDIR)/devfsd
install -s devfsd $(SBINDIR)/devfsd
if [ ! -e $(MANDIR)/man5 ]; then mkdir -p $(MANDIR)/man5; fi
if [ ! -e $(MANDIR)/man8 ]; then mkdir -p $(MANDIR)/man8; fi
-rm -f $(MANDIR)/*/devfsd.*
cp -p devfsd.8 $(MANDIR)/man8
cp -p devfsd.conf.5 $(MANDIR)/man5
if [ ! -e $(CONFDIR) ]; then mkdir -p $(CONFDIR); fi
if [ ! -e $(CONFIG_FILE) ]; then cp -p devfsd.conf $(CONFIG_FILE); fi
@echo "Installing /etc/modules.devfs"
@sed "s/DEVFSD-VERSION/`grep '#define DEVFSD_VERSION' version.h | cut -d'"' -f 2`/" modules.devfs > $(CONFDIR)/modules.devfs
rpm.spec: version.h
echo "%define version `grep '#define DEVFSD_VERSION' version.h | cut -d'"' -f 2`" > rpm.new
tail +2 rpm.spec >> rpm.new
mv rpm.new rpm.spec
clean:
-rm -f *~ *.o *.orig *.rej
distclean: clean
-rm -f devfsd
# Dependencies: made by hand
devfsd.o: devfsd.h version.h
|
where we go wrong is the lines that cp -p the man pages.... typing that line in to a bash prompt causes the same unknown error 524 I found that commenting these lines out made install process run smoothly except of course for the man pages. This would be problem solved except I wanted the emerge to finish so that I could continue my emerge -u world. I found that if I omit the -p from the cp -p there was no error produced... and the man pages seemed to work fine my regular user account can access them normally and everything. so what I really wanted to do is edit the ebuild to make it edit the GNUmakefile even further and strip the -p's off of the cp -p's. I don't know how to do this though... so then I had what I think is a stroke of genius... I edited the ebuild so that the section with the sed statement that changes the makefile looks like this:
| Code: |
src_unpack() {
unpack ${A}
cd ${S}
cp GNUmakefile GNUmakefile.orig
sed -e "s:-O2:${CFLAGS}:g" \
-e 's:/usr/man:/usr/share/man:' \
-e '29,31d;11,16d' -e '6c\' \
-e 'DEFINES := -DLIBNSL="\\"/lib/libnsl.so.1\\""' \
GNUmakefile.orig > GNUmakefile
nano -w GNUmakefile
}
|
adding the line
| Code: | | nano -w GNUmakefile |
let me edit the newly eddited makefile on the fly. as soon as I saved my changes the ebuild would complete. The first time through I found I had to remove the -p from the line about the devfsd.conf file as well. then the emerge finished and emerge -u world moved on to the next ebuild.
my question to you guys is this:
does the ebuild need to be changed to automatically do this? I mean I know this isn't normal emerge procedure to have to go through all of this, but are the -p's there for a reason?
all I know is that solving a problem like this makes a guy feel pretty kewl 
later,
uglyman
p.s. the libmng thing seems to be a problem in the code or something... looks over my head. but it won't emerge still. I am not too worried about that one because I suspect it is far less vital to my system then devfsd  |
|
| Back to top |
|
|
rac
Bodhisattva
Joined: 30 May 2002
Posts: 6553
Location: Japanifornia
|
| Posted: Wed Sep 11, 2002 3:44 am Post subject: |
|
|
Kudos on all your work. Would you happen to be using XFS with ACLs? I seem to remember some other people that had problems with cp -p in that situation. See https://bugs.gentoo.org/show_bug.cgi?id=3582.
_________________
For every higher wall, there is a taller ladder |
|
| Back to top |
|
|
uglyman
Apprentice
Joined: 21 Apr 2002
Posts: 216
Location: Seattle, WA USA
|
| Posted: Wed Sep 11, 2002 5:19 am Post subject: |
|
|
Thanks for that link rac ....
I need to get to bed ASAP if I am gonna make it to work in the morning, but that link seems to be related. Yes I do use XFS. I don't really know anything about it but it sounded good in the install docs and I have had NO problems until now. To be honest I don't even know off the top of my head what ACLs is but I will read up tomorrow.
The bug in the report you linked too really fits because I just updated my kernel for the first time since it switched to the new style where we have to choose a kernel. I hadn't bothered messing with it for a long time. Now they make us choose the "XFS-sources" instead of the Gentoo sources and this recent upgrade must be what made the bug show up. Come to think of it this is the first major emerge attempt I have made since I switched kernels.
As for ACL I will worry about what that is tomorrow and post back to the list if I find anything more that might be useful to someone in my situation.
later,
uglyman |
|
| Back to top |
|
|
uglyman
Apprentice
Joined: 21 Apr 2002
Posts: 216
Location: Seattle, WA USA
|
| Posted: Thu Sep 12, 2002 3:47 am Post subject: OK! |
|
|
Well, I have learned a lot here. in case anyone finds this thread in a search and needs some good info look at this link as well as the one rac mentioned:
http://www-106.ibm.com/developerworks/library/l-fs.html
This is the beginning of a series of tutorials on File systems by our buddy Daniel Robbins Parts 9 and 10 cleared it all up for me. I actually found it in a google search. These explain ACLs a litte (Access Control Lists).
It appears that they have a patch to fix the issue on the bugzilla page that rac linked to. I haven't applied it yet, but I am no longer too concerned with it all. The problem showed up for me because I just updated my kernel for the first time from the SGI XFS sources instead of the gentoo sources (like I said, it had been a while). One of the new use flags I had set was acl which was because it sounded interesting in the USE HOWTO. I was wanting to check out the xfs utils that I have heard mentioned before like xfsdump. The HOWTO said I should set the flag on so I did. So rac nailed it.... amazing recall on that one (thanks rac). I was using XFS and ACLs (although I didn't know what ACLs did)... apparently for the time being those don't work nicely together when doing a cp -p get rid of the -p for a quick fix or try the patch.
Thanks to all who read my long post!
Thanks one more time to rac on the link!
later
uglyman
hmmm now that I am such an expert maybe it is time for the gcc upgrade.... just shoot me  |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Portage & Programming
