[gentoo-user] sys-fs/device-mapper

2006-11-13 Thread James Colby

All -

I am trying to emerge sys-fs/device-mapper on an older piece of
hardware (AMD Duron 800, with 512Mb of Ram).  The package has been
compiling for something like 8 hours already.  Is this normal?  It
seems like an awfully long time to me.  As a comparison, I was able to
compile the kernel in about 15 minutes.  If this isn't normal, any
ideas as to what the problem could be.  I didn't see anything on
bugs.gentoo.org.

Thanks,
James


In case it matters my make.conf looks like this:

CFLAGS=-mtune=athlon -O3 -fomit-frame-pointer
CHOST=i686-pc-linux-gnu
CXXFLAGS=${CFLAGS}
USE=-arts -ipv6 apache2 mysql pam ssl xml xml2 -gnome -gtk alsa oss
nvidia -cups mmx -ldap -kde -qt -kde nptl nptlonly
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread Lorenzo Marussi




Hi

I don't think it's normal.
Maybe there is a loop in compiling. 
Please check, if it's still running, if there is some piece of code that repeats
continuously. 

Post your emerge --info output


Lorenzo Marussi


Il giorno lun, 13/11/2006 alle 10.31 -0500, James Colby ha scritto:


All -

I am trying to emerge sys-fs/device-mapper on an older piece of
hardware (AMD Duron 800, with 512Mb of Ram).  The package has been
compiling for something like 8 hours already.  Is this normal?  It
seems like an awfully long time to me.  As a comparison, I was able to
compile the kernel in about 15 minutes.  If this isn't normal, any
ideas as to what the problem could be.  I didn't see anything on
bugs.gentoo.org.

Thanks,
James


In case it matters my make.conf looks like this:

CFLAGS=-mtune=athlon -O3 -fomit-frame-pointer
CHOST=i686-pc-linux-gnu
CXXFLAGS=${CFLAGS}
USE=-arts -ipv6 apache2 mysql pam ssl xml xml2 -gnome -gtk alsa oss
nvidia -cups mmx -ldap -kde -qt -kde nptl nptlonly






Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread Alan McKinnon
On Monday 13 November 2006 17:31, James Colby wrote:
 All -

 I am trying to emerge sys-fs/device-mapper on an older piece of
 hardware (AMD Duron 800, with 512Mb of Ram).  The package has been
 compiling for something like 8 hours already.  Is this normal?  It
 seems like an awfully long time to me.  As a comparison, I was able
 to compile the kernel in about 15 minutes.  If this isn't normal, any
 ideas as to what the problem could be.  I didn't see anything on
 bugs.gentoo.org.

That looks awfully long to me:

[EMAIL PROTECTED] /usr/share/downloads/onyx $ genlop -t device-mapper
 * sys-fs/device-mapper

 Mon Jul 24 00:56:16 2006  sys-fs/device-mapper-1.02.07
   merge time: 10 seconds.

 Sun Sep  3 19:30:30 2006  sys-fs/device-mapper-1.02.07
   merge time: 20 seconds.

 Thu Sep 21 12:54:37 2006  sys-fs/device-mapper-1.02.09
   merge time: 20 seconds.

 Mon Sep 25 18:51:05 2006  sys-fs/device-mapper-1.02.10
   merge time: 42 seconds.

 Wed Nov  8 16:51:18 2006  sys-fs/device-mapper-1.02.12
   merge time: 45 seconds.

 In case it matters my make.conf looks like this:

 CFLAGS=-mtune=athlon -O3 -fomit-frame-pointer

make that -O2
-O3 uses some insane optimizations which in the grand scheme of things 
don't make much difference speed-wise but can be very unstable

 CHOST=i686-pc-linux-gnu
 CXXFLAGS=${CFLAGS}
 USE=-arts -ipv6 apache2 mysql pam ssl xml xml2 -gnome -gtk alsa oss
 nvidia -cups mmx -ldap -kde -qt -kde nptl nptlonly
-- 
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread James Colby

I modified my make.conf file to: CFLAGS=-mtune=athlon -O2 -fomit-frame-pointer

and the emerge has been running for about 1/2 hour and is still going
(..and going, and going)

Any other ideas???

The output of emerge --info is below:
gentoo portage # emerge --info
Portage 2.1-r2 (default-linux/x86/2006.1, gcc-4.1.1, glibc-2.4-r3,
2.6.17-gentoo-r5 i686)
=
System uname: 2.6.17-gentoo-r5 i686 AMD Duron(tm) Processor
Gentoo Base System version 1.12.1
app-admin/eselect-compiler: [Not Present]
dev-java/java-config: [Not Present]
dev-lang/python: 2.4.3-r1
dev-python/pycrypto: 2.0.1-r5
dev-util/ccache: [Not Present]
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-r2
ACCEPT_KEYWORDS=x86
AUTOCLEAN=yes
CBUILD=i686-pc-linux-gnu
CFLAGS=-mtune=athlon -O2 -fomit-frame-pointer
CHOST=i686-pc-linux-gnu
CONFIG_PROTECT=/etc
CONFIG_PROTECT_MASK=/etc/env.d /etc/gconf /etc/terminfo
CXXFLAGS=-mtune=athlon -O2 -fomit-frame-pointer
DISTDIR=/usr/portage/distfiles
FEATURES=autoconfig distlocks metadata-transfer sandbox sfperms strict
GENTOO_MIRRORS=http://mirrors.tds.net/gentoo;
PKGDIR=/usr/portage/packages
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_TMPDIR=/var/tmp
PORTDIR=/usr/portage
SYNC=rsync://rsync.gentoo.org/gentoo-portage
USE=x86 alsa apache2 berkdb bitmap-fonts cli cracklib crypt dlloader
dri fortran gdbm gpm iconv isdnlog libg++ mmx mysql ncurses nls nptl
nptlonly nvidia oss pam pcre perl ppds pppd python readline reflection
session spl ssl tcpd truetype-fonts type1-fonts udev unicode xml xml2
xorg zlib elibc_glibc input_devices_keyboard input_devices_mouse
kernel_linux userland_GNU video_cards_nvidia
Unset:  CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LANG, LC_ALL,
LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

On 11/13/06, Alan McKinnon [EMAIL PROTECTED] wrote:

On Monday 13 November 2006 17:31, James Colby wrote:
 All -

 I am trying to emerge sys-fs/device-mapper on an older piece of
 hardware (AMD Duron 800, with 512Mb of Ram).  The package has been
 compiling for something like 8 hours already.  Is this normal?  It
 seems like an awfully long time to me.  As a comparison, I was able
 to compile the kernel in about 15 minutes.  If this isn't normal, any
 ideas as to what the problem could be.  I didn't see anything on
 bugs.gentoo.org.

That looks awfully long to me:

[EMAIL PROTECTED] /usr/share/downloads/onyx $ genlop -t device-mapper
 * sys-fs/device-mapper

 Mon Jul 24 00:56:16 2006  sys-fs/device-mapper-1.02.07
   merge time: 10 seconds.

 Sun Sep  3 19:30:30 2006  sys-fs/device-mapper-1.02.07
   merge time: 20 seconds.

 Thu Sep 21 12:54:37 2006  sys-fs/device-mapper-1.02.09
   merge time: 20 seconds.

 Mon Sep 25 18:51:05 2006  sys-fs/device-mapper-1.02.10
   merge time: 42 seconds.

 Wed Nov  8 16:51:18 2006  sys-fs/device-mapper-1.02.12
   merge time: 45 seconds.

 In case it matters my make.conf looks like this:

 CFLAGS=-mtune=athlon -O3 -fomit-frame-pointer

make that -O2
-O3 uses some insane optimizations which in the grand scheme of things
don't make much difference speed-wise but can be very unstable

 CHOST=i686-pc-linux-gnu
 CXXFLAGS=${CFLAGS}
 USE=-arts -ipv6 apache2 mysql pam ssl xml xml2 -gnome -gtk alsa oss
 nvidia -cups mmx -ldap -kde -qt -kde nptl nptlonly
--
gentoo-user@gentoo.org mailing list



--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread Richard Fish

On 11/13/06, James Colby [EMAIL PROTECTED] wrote:

I modified my make.conf file to: CFLAGS=-mtune=athlon -O2 -fomit-frame-pointer

and the emerge has been running for about 1/2 hour and is still going
(..and going, and going)

Any other ideas???


Interrupt it and post the last 100 lines or so of the output.

-Richard

PS: please don't top-post.  This goes for Lorenzo too.
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread James Colby


Interrupt it and post the last 100 lines or so of the output.

-Richard



My apologies, for the top posting.  I interrupted the compile and
below is some of the output from the emerge:

make[1]: Leaving directory
`/var/tmp/portage/device-mapper-1.02.12/work/device-mapper.1.02.12/lib'
make[1]: Entering directory
`/var/tmp/portage/device-mapper-1.02.12/work/device-mapper.1.02.12/lib'
make[1]: Warning: File `ioctl/libdm-iface.c' has modification time
1.7e+08 s in the future
set -e; \
FILE=`echo ioctl/libdm-iface.d | sed 's/\\//\\//g;s/\\.d//g'`; \
DEPS=`echo ../make.tmpl ../VERSION Makefile
../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
-DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
-fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
-Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
-DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
-Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
-Wmissing-declarations -Wnested-externs -Winline -O2
ioctl/libdm-iface.c | \
sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g 
ioctl/libdm-iface.d; \
[ -s ioctl/libdm-iface.d ] || rm -f ioctl/libdm-iface.d
set -e; \
FILE=`echo mm/pool.d | sed 's/\\//\\//g;s/\\.d//g'`; \
DEPS=`echo ../make.tmpl ../VERSION Makefile
../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
-DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
-fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
-Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
-DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
-Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
-Wmissing-declarations -Wnested-externs -Winline -O2 mm/pool.c | \
sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g  mm/pool.d; \
[ -s mm/pool.d ] || rm -f mm/pool.d
set -e; \
FILE=`echo mm/dbg_malloc.d | sed 's/\\//\\//g;s/\\.d//g'`; \
DEPS=`echo ../make.tmpl ../VERSION Makefile
../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
-DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
-fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
-Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
-DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
-Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
-Wmissing-declarations -Wnested-externs -Winline -O2 mm/dbg_malloc.c |
\
sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g  mm/dbg_malloc.d; \
[ -s mm/dbg_malloc.d ] || rm -f mm/dbg_malloc.d
set -e; \
FILE=`echo libdm-string.d | sed 's/\\//\\//g;s/\\.d//g'`; \
DEPS=`echo ../make.tmpl ../VERSION Makefile
../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
-DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
-fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
-Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
-DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
-Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
-Wmissing-declarations -Wnested-externs -Winline -O2 libdm-string.c |
\
sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g  libdm-string.d; \
[ -s libdm-string.d ] || rm -f libdm-string.d
set -e; \
FILE=`echo libdm-deptree.d | sed 's/\\//\\//g;s/\\.d//g'`; \
DEPS=`echo ../make.tmpl ../VERSION Makefile
../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
-DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
-fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
-Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
-Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
-DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
-Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
-Wmissing-declarations -Wnested-externs -Winline -O2 libdm-deptree.c |
\
sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g  libdm-deptree.d; \
[ -s libdm-deptree.d ] || rm -f libdm-deptree.d
set -e; \
FILE=`echo libdm-file.d | sed 's/\\//\\//g;s/\\.d//g'`; \
DEPS=`echo ../make.tmpl ../VERSION Makefile
../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
-DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
-fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow 

Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread James Colby


Also, try unpacking the source somewhere and doing a manual compile.
Then at least you'll know if it's portage making the difference or not.

alan
--


Alan, thanks for the suggestion.  I tried this and the compile failed
with an error related to the system time.  I checked the system date
and it was *WAY* off...after fixing the date / time the emerge of
device-mapper took about 1.5 minutes.  Thanks for all the help
everyone.

James (off to install ntp)
--
gentoo-user@gentoo.org mailing list



Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread Neil Bothwick
On Mon, 13 Nov 2006 19:26:44 +0200, Alan McKinnon wrote:

 What's the compile doing? I see you don't have PORTAGE_ELOG* set so you 
 won't have full compile session logs in /var/log/portage but you should 
 be able to see on the screen what's happening and make an intelligent 
 summary.

It's PORT_LOGDIR that sets the destination for full compile logs. The
PORTAGE_ELOG variables control the saving or mailing of the info and
warn messages from the ebuild. 


-- 
Neil Bothwick

In possession of a mind not merely twisted, but actually sprained.


signature.asc
Description: PGP signature


Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread Alan McKinnon
On Monday 13 November 2006 19:35, James Colby wrote:
  Interrupt it and post the last 100 lines or so of the output.
 
  -Richard

 My apologies, for the top posting.  I interrupted the compile and
 below is some of the output from the emerge:

This is becoming a big post, but so be it. I compared your output to the 
same package being compiled on my machine, and I found a difference. 
The beginning is the same:

 make[1]: Leaving directory
 `/var/tmp/portage/device-mapper-1.02.12/work/device-mapper.1.02.12/li
b' make[1]: Entering directory
 `/var/tmp/portage/device-mapper-1.02.12/work/device-mapper.1.02.12/li
b' make[1]: Warning: File `ioctl/libdm-iface.c' has modification time
 1.7e+08 s in the future
 set -e; \
 FILE=`echo ioctl/libdm-iface.d | sed 's/\\//\\//g;s/\\.d//g'`; \
 DEPS=`echo ../make.tmpl ../VERSION Makefile
 ../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
 i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
 -DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
 -fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
 -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
 -Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
 -DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
 -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
 -Wmissing-declarations -Wnested-externs -Winline -O2
 ioctl/libdm-iface.c | \
 sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g 
 ioctl/libdm-iface.d; \
 [ -s ioctl/libdm-iface.d ] || rm -f ioctl/libdm-iface.d
 set -e; \
 FILE=`echo mm/pool.d | sed 's/\\//\\//g;s/\\.d//g'`; \
 DEPS=`echo ../make.tmpl ../VERSION Makefile
 ../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
 i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
 -DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
 -fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
 -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
 -Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
 -DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
 -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
 -Wmissing-declarations -Wnested-externs -Winline -O2 mm/pool.c | \
 sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g 
 mm/pool.d; \ [ -s mm/pool.d ] || rm -f mm/pool.d
 set -e; \
 FILE=`echo mm/dbg_malloc.d | sed 's/\\//\\//g;s/\\.d//g'`; \
 DEPS=`echo ../make.tmpl ../VERSION Makefile
 ../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
 i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
 -DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
 -fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
 -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
 -Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
 -DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
 -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
 -Wmissing-declarations -Wnested-externs -Winline -O2 mm/dbg_malloc.c
 | \
 sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g 
 mm/dbg_malloc.d; \ [ -s mm/dbg_malloc.d ] || rm -f mm/dbg_malloc.d
 set -e; \
 FILE=`echo libdm-string.d | sed 's/\\//\\//g;s/\\.d//g'`; \
 DEPS=`echo ../make.tmpl ../VERSION Makefile
 ../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
 i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
 -DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
 -fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
 -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
 -Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
 -DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
 -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
 -Wmissing-declarations -Wnested-externs -Winline -O2 libdm-string.c |
 \
 sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g 
 libdm-string.d; \ [ -s libdm-string.d ] || rm -f libdm-string.d
 set -e; \
 FILE=`echo libdm-deptree.d | sed 's/\\//\\//g;s/\\.d//g'`; \
 DEPS=`echo ../make.tmpl ../VERSION Makefile
 ../include/.symlinks_created | sed -e 's/\\//\\//g'`; \
 i686-pc-linux-gnu-gcc -MM -Iioctl -I. -I../include -DHAVE_CONFIG_H
 -DDM_IOCTLS -mtune=athlon -O2 -fomit-frame-pointer -mtune=athlon -O2
 -fomit-frame-pointer -fPIC -Wall -Wundef -Wshadow -Wcast-align
 -Wwrite-strings -Wmissing-prototypes -Wmissing-declarations
 -Wnested-externs -Winline -O2 -DDEVICE_UID=0 -DDEVICE_GID=0
 -DDEVICE_MODE=0600 -mtune=athlon -O2 -fomit-frame-pointer -fPIC -Wall
 -Wundef -Wshadow -Wcast-align -Wwrite-strings -Wmissing-prototypes
 -Wmissing-declarations -Wnested-externs -Winline -O2 libdm-deptree.c
 | \
 sed s/\(.*\)\.o[ :]*/$FILE.o $FILE.d $FILE.pot: $DEPS /g 
 libdm-deptree.d; \ [ -s libdm-deptree.d ] || rm -f libdm-deptree.d
 set -e; \
 FILE=`echo libdm-file.d | sed 

Re: [gentoo-user] sys-fs/device-mapper

2006-11-13 Thread Alan McKinnon
On Monday 13 November 2006 20:07, Neil Bothwick wrote:
 On Mon, 13 Nov 2006 19:26:44 +0200, Alan McKinnon wrote:
  What's the compile doing? I see you don't have PORTAGE_ELOG* set so
  you won't have full compile session logs in /var/log/portage but
  you should be able to see on the screen what's happening and make
  an intelligent summary.

 It's PORT_LOGDIR that sets the destination for full compile logs. The
 PORTAGE_ELOG variables control the saving or mailing of the info and
 warn messages from the ebuild.

Yes you are correct of course. Thanks for the clarification.

alan
-- 
gentoo-user@gentoo.org mailing list