public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-amd64]  Re: failing to emerge update
  2009-10-13  3:58 [gentoo-amd64] failing to emerge update Mansour Al Akeel
@ 2009-10-13  3:10 ` Nikos Chantziaras
  2009-10-13  4:09   ` Mansour Al Akeel
  2009-10-13  3:16 ` [gentoo-amd64] " Frank Peters
  2009-10-13  6:31 ` Alex Alexander
  2 siblings, 1 reply; 14+ messages in thread
From: Nikos Chantziaras @ 2009-10-13  3:10 UTC (permalink / raw
  To: gentoo-amd64

On 10/13/2009 06:58 AM, Mansour Al Akeel wrote:
> Hello All:
>
> "emerge --update --deep world " is failing. I can not install libXaw. I
> am getting the following error:
>
>
> make[1]: Leaving directory
> `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'
> make: *** [all] Error 2

That's too late.  We need to see further up where the real error message 
is.  What you posted only tells "there was an error".  The actual error 
is further up.




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64] failing to emerge update
  2009-10-13  3:58 [gentoo-amd64] failing to emerge update Mansour Al Akeel
  2009-10-13  3:10 ` [gentoo-amd64] " Nikos Chantziaras
@ 2009-10-13  3:16 ` Frank Peters
  2009-10-13  3:17   ` Crístian Viana
  2009-10-13  6:31 ` Alex Alexander
  2 siblings, 1 reply; 14+ messages in thread
From: Frank Peters @ 2009-10-13  3:16 UTC (permalink / raw
  To: gentoo-amd64

On Tue, 13 Oct 2009 00:58:43 -0300
Mansour Al Akeel <mansour.alakeel@gmail.com> wrote:

> * The complete build log is located at
> * '/var/tmp/portage/x11-libs/libXaw-1.0.6/temp/build.log'.

You need to examine the last lines of this build log.
It will reveal the exact point of the error.

You may want to post this build log, or at least the
tail portion of it, to the list.

Frank Peters




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64] failing to emerge update
  2009-10-13  3:16 ` [gentoo-amd64] " Frank Peters
@ 2009-10-13  3:17   ` Crístian Viana
  0 siblings, 0 replies; 14+ messages in thread
From: Crístian Viana @ 2009-10-13  3:17 UTC (permalink / raw
  To: gentoo-amd64

[-- Attachment #1: Type: text/plain, Size: 828 bytes --]

take a look at this upgrade guide:
http://www.gentoo.org/proj/en/desktop/x/x11/libxcb-1.4-upgrade-guide.xml

 <http://www.gentoo.org/proj/en/desktop/x/x11/libxcb-1.4-upgrade-guide.xml>it
may help you :)

On Tue, Oct 13, 2009 at 12:16 AM, Frank Peters <frank.peters@comcast.net>wrote:

> On Tue, 13 Oct 2009 00:58:43 -0300
> Mansour Al Akeel <mansour.alakeel@gmail.com> wrote:
>
> > * The complete build log is located at
> > * '/var/tmp/portage/x11-libs/libXaw-1.0.6/temp/build.log'.
>
> You need to examine the last lines of this build log.
> It will reveal the exact point of the error.
>
> You may want to post this build log, or at least the
> tail portion of it, to the list.
>
> Frank Peters
>
>
>


-- 
Crístian Deives dos Santos Viana [aka CD1]
Sent from Natal, Rio Grande do Norte, Brazil

[-- Attachment #2: Type: text/html, Size: 1384 bytes --]

^ permalink raw reply	[flat|nested] 14+ messages in thread

* [gentoo-amd64] failing to emerge update
@ 2009-10-13  3:58 Mansour Al Akeel
  2009-10-13  3:10 ` [gentoo-amd64] " Nikos Chantziaras
                   ` (2 more replies)
  0 siblings, 3 replies; 14+ messages in thread
From: Mansour Al Akeel @ 2009-10-13  3:58 UTC (permalink / raw
  To: gentoo64-help

Hello All:

"emerge --update --deep world " is failing. I can not install libXaw. I
am getting the following error:


make[1]: Leaving directory
`/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'
make: *** [all] Error 2
* ERROR: x11-libs/libXaw-1.0.6 failed:
*   emake failed
* 
* Call stack:
*     ebuild.sh, line   49:  Called src_compile
*   environment, line 3258:  Called x-modular_src_compile
*   environment, line 4043:  Called x-modular_src_make
*   environment, line 4082:  Called die
* The specific snippet of code:
*       emake || die "emake failed"
* 
* If you need support, post the output of 'emerge --info
* =x11-libs/libXaw-1.0.6',
* the complete build log and the output of 'emerge -pqv
* =x11-libs/libXaw-1.0.6'.
* The complete build log is located at
* '/var/tmp/portage/x11-libs/libXaw-1.0.6/temp/build.log'.
* The ebuild environment file is located at
* '/var/tmp/portage/x11-libs/libXaw-1.0.6/temp/environment'.
* S:
* '/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'

>>> Failed to emerge x11-libs/libXaw-1.0.6, Log file:

>>>  '/var/tmp/portage/x11-libs/libXaw-1.0.6/temp/build.log'

* Messages for package x11-libs/libXaw-1.0.6:

* ERROR: x11-libs/libXaw-1.0.6 failed:
*   emake failed
* 
* Call stack:
*     ebuild.sh, line   49:  Called src_compile
*   environment, line 3258:  Called
*   x-modular_src_compile
*   environment, line 4043:  Called
*   x-modular_src_make
*   environment, line 4082:  Called die
* The specific snippet of code:
*       emake || die "emake failed"
* 
* If you need support, post the output of
* 'emerge --info =x11-libs/libXaw-1.0.6',
* the complete build log and the output of
* 'emerge -pqv =x11-libs/libXaw-1.0.6'.
* The complete build log is located at
* '/var/tmp/portage/x11-libs/libXaw-1.0.6/temp/build.log'.
* The ebuild environment file is located
* at
* '/var/tmp/portage/x11-libs/libXaw-1.0.6/temp/environment'.
* S:
* '/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'


I don't understand what I need to here. And I can not open the browser
to google it !






^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64]  Re: failing to emerge update
  2009-10-13  3:10 ` [gentoo-amd64] " Nikos Chantziaras
@ 2009-10-13  4:09   ` Mansour Al Akeel
  2009-10-13  6:10     ` Volker Armin Hemmann
  0 siblings, 1 reply; 14+ messages in thread
From: Mansour Al Akeel @ 2009-10-13  4:09 UTC (permalink / raw
  To: gentoo-amd64; +Cc: mansour.alakeel

Nikos, I hope this (the log file) help:



>>> Unpacking source...
>>> Unpacking libXaw-1.0.6.tar.bz2 to /var/tmp/portage/x11-libs/libXaw-1.0.6/work
 ^[[32;01m*^[[0m Running elibtoolize in: libXaw-1.0.6
 ^[[32;01m*^[[0m   Applying portage-2.2.patch ...
 ^[[32;01m*^[[0m   Applying sed-1.5.6.patch ...
 ^[[32;01m*^[[0m   Applying as-needed-2.2.6.patch ...
>>> Source unpacked in /var/tmp/portage/x11-libs/libXaw-1.0.6/work
>>> Compiling source in /var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6 ...
 * econf: updating libXaw-1.0.6/config.guess with /usr/share/gnuconfig/config.guess
 * econf: updating libXaw-1.0.6/config.sub with /usr/share/gnuconfig/config.sub
./configure --prefix=/usr --build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --prefix=/usr --datadir=/usr/share
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking if xorg-macros used to generate configure is at least 1.2... yes, 1.2.1
checking for x86_64-pc-linux-gnu-gcc... x86_64-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether x86_64-pc-linux-gnu-gcc accepts -g... yes
checking for x86_64-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of x86_64-pc-linux-gnu-gcc... gcc3
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by x86_64-pc-linux-gnu-gcc... /usr/x86_64-pc-linux-gnu/bin/ld
checking if the linker (/usr/x86_64-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/x86_64-pc-linux-gnu/bin/ld option to reload object files... -r
checking for x86_64-pc-linux-gnu-objdump... x86_64-pc-linux-gnu-objdump
checking how to recognize dependent libraries... pass_all
checking for x86_64-pc-linux-gnu-ar... x86_64-pc-linux-gnu-ar
checking for x86_64-pc-linux-gnu-strip... x86_64-pc-linux-gnu-strip
checking for x86_64-pc-linux-gnu-ranlib... x86_64-pc-linux-gnu-ranlib
checking command to parse /usr/bin/nm -B output from x86_64-pc-linux-gnu-gcc object... ok
checking how to run the C preprocessor... x86_64-pc-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if x86_64-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for x86_64-pc-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
checking if x86_64-pc-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
checking if x86_64-pc-linux-gnu-gcc static flag -static works... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... yes
checking if x86_64-pc-linux-gnu-gcc supports -c -o file.o... (cached) yes
checking whether the x86_64-pc-linux-gnu-gcc linker (/usr/x86_64-pc-linux-gnu/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for x86_64-pc-linux-gnu-pkg-config... no
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for a sed that does not truncate output... (cached) /bin/sed
checking for XAW6... yes
checking for XAW7... yes
checking for ANSI C header files... (cached) yes
checking wctype.h usability... yes
checking wctype.h presence... yes
checking for wctype.h... yes
checking wchar.h usability... yes
checking wchar.h presence... yes
checking for wchar.h... yes
checking widec.h usability... no
checking widec.h presence... no
checking for widec.h... no
checking for iswalnum... yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating include/Makefile
config.status: creating man/Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing libtool_hack commands
configure: creating ./config.status
config.status: creating Makefile
config.status: creating include/Makefile
config.status: creating man/Makefile
config.status: creating src/Makefile
config.status: creating xaw6.pc
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing libtool_hack commands
configure: creating ./config.status
config.status: creating Makefile
config.status: creating include/Makefile
config.status: creating man/Makefile
config.status: creating src/Makefile
config.status: creating xaw6.pc
config.status: creating xaw7.pc
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands
config.status: executing libtool_hack commands
make 
make  all-recursive
make[1]: Entering directory `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'
Making all in include
make[2]: Entering directory `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6/include'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6/include'
Making all in src
make[2]: Entering directory `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6/src'
/bin/sh ../libtool --tag=CC   --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..    -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement   -march=athlon64 -Os -pipe -MT libXaw6_la-Actions.lo -MD -MP -MF .deps/libXaw6_la-Actions.Tpo -c -o libXaw6_la-Actions.lo `test -f 'Actions.c' || echo './'`Actions.c
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-Actions.lo -MD -MP -MF .deps/libXaw6_la-Actions.Tpo -c Actions.c  -fPIC -DPIC -o .libs/libXaw6_la-Actions.o
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-Actions.lo -MD -MP -MF .deps/libXaw6_la-Actions.Tpo -c Actions.c -o libXaw6_la-Actions.o >/dev/null 2>&1
mv -f .deps/libXaw6_la-Actions.Tpo .deps/libXaw6_la-Actions.Plo
/bin/sh ../libtool --tag=CC   --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..    -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement   -march=athlon64 -Os -pipe -MT libXaw6_la-AllWidgets.lo -MD -MP -MF .deps/libXaw6_la-AllWidgets.Tpo -c -o libXaw6_la-AllWidgets.lo `test -f 'AllWidgets.c' || echo './'`AllWidgets.c
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-AllWidgets.lo -MD -MP -MF .deps/libXaw6_la-AllWidgets.Tpo -c AllWidgets.c  -fPIC -DPIC -o .libs/libXaw6_la-AllWidgets.o
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-AllWidgets.lo -MD -MP -MF .deps/libXaw6_la-AllWidgets.Tpo -c AllWidgets.c -o libXaw6_la-AllWidgets.o >/dev/null 2>&1
mv -f .deps/libXaw6_la-AllWidgets.Tpo .deps/libXaw6_la-AllWidgets.Plo
/bin/sh ../libtool --tag=CC   --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..    -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement   -march=athlon64 -Os -pipe -MT libXaw6_la-AsciiSink.lo -MD -MP -MF .deps/libXaw6_la-AsciiSink.Tpo -c -o libXaw6_la-AsciiSink.lo `test -f 'AsciiSink.c' || echo './'`AsciiSink.c
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-AsciiSink.lo -MD -MP -MF .deps/libXaw6_la-AsciiSink.Tpo -c AsciiSink.c  -fPIC -DPIC -o .libs/libXaw6_la-AsciiSink.o
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-AsciiSink.lo -MD -MP -MF .deps/libXaw6_la-AsciiSink.Tpo -c AsciiSink.c -o libXaw6_la-AsciiSink.o >/dev/null 2>&1
mv -f .deps/libXaw6_la-AsciiSink.Tpo .deps/libXaw6_la-AsciiSink.Plo
/bin/sh ../libtool --tag=CC   --mode=compile x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I..    -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement   -march=athlon64 -Os -pipe -MT libXaw6_la-AsciiSrc.lo -MD -MP -MF .deps/libXaw6_la-AsciiSrc.Tpo -c -o libXaw6_la-AsciiSrc.lo `test -f 'AsciiSrc.c' || echo './'`AsciiSrc.c
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-AsciiSrc.lo -MD -MP -MF .deps/libXaw6_la-AsciiSrc.Tpo -c AsciiSrc.c  -fPIC -DPIC -o .libs/libXaw6_la-AsciiSrc.o
libtool: compile:  x86_64-pc-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include/X11/Xaw -DPROJECT_ROOT=\"/usr\" -DOLDXAW -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing -Wbad-function-cast -Wold-style-definition -Wdeclaration-after-statement -march=athlon64 -Os -pipe -MT libXaw6_la-AsciiSrc.lo -MD -MP -MF .deps/libXaw6_la-AsciiSrc.Tpo -c AsciiSrc.c -o libXaw6_la-AsciiSrc.o >/dev/null 2>&1





On Tue Oct 13,2009 06:10 am, Nikos Chantziaras wrote:
> On 10/13/2009 06:58 AM, Mansour Al Akeel wrote:
>> Hello All:
>>
>> "emerge --update --deep world " is failing. I can not install libXaw. I
>> am getting the following error:
>>
>>
>> make[1]: Leaving directory
>> `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'
>> make: *** [all] Error 2
>
> That's too late.  We need to see further up where the real error message 
> is.  What you posted only tells "there was an error".  The actual error is 
> further up.
>
>



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64]  Re: failing to emerge update
  2009-10-13  4:09   ` Mansour Al Akeel
@ 2009-10-13  6:10     ` Volker Armin Hemmann
  0 siblings, 0 replies; 14+ messages in thread
From: Volker Armin Hemmann @ 2009-10-13  6:10 UTC (permalink / raw
  To: gentoo-amd64

you are still not posting everything




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64] failing to emerge update
  2009-10-13  3:58 [gentoo-amd64] failing to emerge update Mansour Al Akeel
  2009-10-13  3:10 ` [gentoo-amd64] " Nikos Chantziaras
  2009-10-13  3:16 ` [gentoo-amd64] " Frank Peters
@ 2009-10-13  6:31 ` Alex Alexander
  2009-10-13 13:25   ` Mansour Al Akeel
  2 siblings, 1 reply; 14+ messages in thread
From: Alex Alexander @ 2009-10-13  6:31 UTC (permalink / raw
  To: gentoo-amd64

On Tue, Oct 13, 2009 at 06:58, Mansour Al Akeel
<mansour.alakeel@gmail.com> wrote:
> Hello All:
>
> "emerge --update --deep world " is failing. I can not install libXaw. I
> am getting the following error:
>
>
> make[1]: Leaving directory
> `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'
> make: *** [all] Error 2

We need your full build.log! Neither of your two emails contains the
"Error 1" part where it actually failed and we have to read that to
help :)

Try wgetpaste[0]'ing the build.log file.

[0] app-text/wgetpaste - Command-line interface to various pastebins

-- 
Alex || wired
Gentoo Dev
www.linuxized.com



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64] failing to emerge update
  2009-10-13  6:31 ` Alex Alexander
@ 2009-10-13 13:25   ` Mansour Al Akeel
  2009-10-13 14:39     ` [gentoo-amd64] " Duncan
  0 siblings, 1 reply; 14+ messages in thread
From: Mansour Al Akeel @ 2009-10-13 13:25 UTC (permalink / raw
  To: gentoo-amd64

I lost the output from the previos build, and unable to regenerate the
issue after fooliwnf libxcb update guilde. But now I am stuck with
another error, when bulllding gcc.


/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include  -O2 -march=athlon64 -pipe -O2    -o minimal  minimal.o  -lpthread -lm true "AR_FLAGS=rc" "CC_FOR_BUILD=gcc" "CC_FOR_TARGET=/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/xgcc -B/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/ -B/usr/x86_64-pc-linux-gnu/bin/ -B/usr/x86_64-pc-linux-gnu/lib/ -isystem /usr/x86_64-pc-linux-gnu/include -isystem /usr/x86_64-pc-linux-gnu/sys-include" "CFLAGS=-O2 -march=athlon64 -pipe -O2 " "CXXFLAGS=-march=athlon64 -pipe -O2  -D_GNU_SOURCE" "CFLAGS_FOR_BUILD=-march=athlon64 -pipe -O2" "CFLAGS_FOR_TARGET=-O2 -march=athlon64 -pipe -O2 " "INSTALL=/usr/bin/install -c" "INSTALL_DATA=/usr/bin/install -c -m 644" "INSTALL_PROGRAM=/usr/bin/install -c" "INSTALL_SCRIPT=/usr/bin/install -c" "LDFLAGS=" "LIBCFLAGS=-O2 -march=athlon64 -pipe -O2 " "LIBCFLAGS_FOR_TARGET=-O2 -march=athlon64 -pipe -O2 " "MAKE=make" "MAKEINFO=makeinfo --split-size=5000000 --split-size=5000000 --split-size=5000000  " "PICFLAG=" "PICFLAG_FOR_TARGET=" "SHELL=/bin/sh" "RUNTESTFLAGS=" "exec_prefix=/usr" "infodir=/usr/share/gcc-data/x86_64-pc-linux-gnu/4.1.2/info" "libdir=/usr/lib" "includedir=/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/include" "prefix=/usr" "tooldir=/usr/x86_64-pc-linux-gnu" "gdc_include_dir=/usr/include/d/4.1.2" "AR=x86_64-pc-linux-gnu-ar" "AS=/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/as" "LD=/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/collect-ld" "RANLIB=x86_64-pc-linux-gnu-ranlib" "NM=/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/./gcc/nm" "NM_FOR_BUILD=" "NM_FOR_TARGET=x86_64-pc-linux-gnu-nm" "DESTDIR=" "WERROR=" DO=all multi-do # make
make[4]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/x86_64-pc-linux-gnu/libphobos'
make[3]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build/x86_64-pc-linux-gnu/libphobos'
make[2]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build'
make[1]: Leaving directory `/var/tmp/portage/sys-devel/gcc-4.1.2/work/build'
/var/tmp/portage/sys-devel/gcc-4.1.2/work/build /var/tmp/portage/sys-devel/gcc-4.1.2/work/gcc-4.1.2
>>> Source compiled.
--------------------------- ACCESS VIOLATION SUMMARY ---------------------------
LOG FILE "/var/log/sandbox/sandbox-11274.log"

VERSION 1.0    
FORMAT: F - Function called
FORMAT: S - Access Status
FORMAT: P - Path as passed to function
FORMAT: A - Absolute Path (not canonical)
FORMAT: R - Canonical Path
FORMAT: C - Command Line

F: open_wr     
S: deny        
P: /dev/stderr 
A: /dev/stderr 
R: /dev/stderr 
C: /bin/bash /usr/bin/jikes --help
--------------------------------------------------------------------------------

>>> Failed to emerge sys-devel/gcc-4.1.2, Log file:

>>>  '/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'

* IMPORTANT: 2 news items need reading for repository 'gentoo'.
* Use eselect news to read news items.

*             
* revdep-rebuild failed to emerge all packages.
* you have the following choices:
* - If emerge failed during the build, fix the problems and re-run revdep-rebuild.
* - Use /etc/portage/package.keywords to unmask a newer version of the package.
*   (and remove 5_order.rr to be evaluated again)
* - Modify the above emerge command and run it manually.
* - Compile or unmerge unsatisfied packages manually,
*   remove temporary files, and try again.
*   (you can edit package/ebuild list first)
*             
* To remove temporary files, please run:
* rm /var/cache/revdep-rebuild/*.rr
* Found some broken files that weren't associated with known packages
* The broken files are:
*   /usr/lib64/gcc/x86_64-pc-linux-gnu/4.1.2/lib-gnu-java-awt-peer-gtk.so.7.0.0




On Tue Oct 13,2009 09:31 am, Alex Alexander wrote:
> On Tue, Oct 13, 2009 at 06:58, Mansour Al Akeel
> <mansour.alakeel@gmail.com> wrote:
> > Hello All:
> >
> > "emerge --update --deep world " is failing. I can not install libXaw. I
> > am getting the following error:
> >
> >
> > make[1]: Leaving directory
> > `/var/tmp/portage/x11-libs/libXaw-1.0.6/work/libXaw-1.0.6'
> > make: *** [all] Error 2
> 
> We need your full build.log! Neither of your two emails contains the
> "Error 1" part where it actually failed and we have to read that to
> help :)
> 
> Try wgetpaste[0]'ing the build.log file.
> 
> [0] app-text/wgetpaste - Command-line interface to various pastebins
> 
> -- 
> Alex || wired
> Gentoo Dev
> www.linuxized.com
> 



^ permalink raw reply	[flat|nested] 14+ messages in thread

* [gentoo-amd64]  Re: failing to emerge update
  2009-10-13 13:25   ` Mansour Al Akeel
@ 2009-10-13 14:39     ` Duncan
  2009-10-14 17:37       ` Mansour Al Akeel
  2009-10-14 23:49       ` Mansour Al Akeel
  0 siblings, 2 replies; 14+ messages in thread
From: Duncan @ 2009-10-13 14:39 UTC (permalink / raw
  To: gentoo-amd64

Mansour Al Akeel posted on Tue, 13 Oct 2009 10:25:15 -0300 as excerpted:

> I lost the output from the previos build, and unable to regenerate the
> issue after fooliwnf libxcb update guilde. But now I am stuck with
> another error, when bulllding gcc.
> 
> 
> /var/tmp/portage/sys-devel/gcc-4.1.2/

gcc-4.1.2 ?  gcc 4.1 is a bit outdated.  You /may/ be able to simply 
unmerge it.  What versions of gcc do you have installed, anyway?  It's 
likely you have a 4.3 version, as gcc-4.3.2-r3 is the latest keyworded 
stable for amd64.

A caution, however.  Until your whole system is rebuilt with the newer 
gccs, some C++ packages in particular may still link to the old 
versions.  But it should at least be possible to ignore the old gccs for 
the moment (emerge --resume --skipfirst if necessary) and build 
everything else.  If you're using FEATURES=buildpkg, it's easy enough to 
unmerge a package, see if anything breaks (run revdep-rebuild and see if 
there's anything that needs rebuilt, and hope it rebuilds fine), and 
remerge the binpkg if necessary.  That's what I'd do.  

If you're not running FEATURES=buildpkg, I'd suggest you consider it.  
Right before a system-wide rebuild is a great time to turn it on. =:^)  
But if you're not, you can use quickpkg to create a binpkg of a 
particular package before removing it for testing.  That way you still 
get the binpkg, and can remerge it if necessary, if you find you still 
need it.

Anyway... after updating gcc to 4.3.2-r3 if you don't have it, and gcc-
config-ing to it, you could emerge --emptytree @system @world so 
everything is built with it, and then unmerge older gcc versions, 
including the 4.1.2 that's giving you issues ATM.

FWIW, on ~amd64, the only gcc I have currently installed is 4.4.1, as I 
unmerged earlier versions after I had rebuilt the entire system with it.  
I do remember having some issues rebuilding earlier gccs at one point, 
but with the entire system (other than those gccs) building with 4.4.1, I 
was able to unmerge them instead of rebuild them.

Of course, I always do --update --deep --newuse, generally a couple times 
a week, and revdep-rebuild and --depclean afterward, to make sure the 
system stays consistent and keep the cruft to a minimum.  If you've let 
it build up by not regularly using --update --deep and not regularly 
doing --depcleans and revdep-rebuilds, you are likely to have quite some 
problems getting the system back in shape, as there will be quite some 
cruft buildup to clean out, and doing it incrementally as the updates 
show up is MUCH easier than letting it buildup and trying to do it all at 
once.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64] Re: failing to emerge update
  2009-10-13 14:39     ` [gentoo-amd64] " Duncan
@ 2009-10-14 17:37       ` Mansour Al Akeel
  2009-10-14 23:49       ` Mansour Al Akeel
  1 sibling, 0 replies; 14+ messages in thread
From: Mansour Al Akeel @ 2009-10-14 17:37 UTC (permalink / raw
  To: gentoo-amd64

I did revdep-rebuild and things went fine. When I did --depclean, It
removed many necessary packages. And I can not even complete
running "emerge system", it fails on one of the packages due to missing alocal !

I can not even run mutt, as lynx is not there and can not install it as well.

I run this type of things before going to bed, as it takes time. I
should change this habit, and spend time on it when I am not tired. :)
I will look into this tonight, or maybe on the weekend. I may have to
spend many hours to fix this.

Normally I run "emerge --update --deep --newuse world" every two
weeks, but I haven't done this for more than 2 months. I don't this
should be an issue.


On Tue, Oct 13, 2009 at 11:39 AM, Duncan <1i5t5.duncan@cox.net> wrote:
> Mansour Al Akeel posted on Tue, 13 Oct 2009 10:25:15 -0300 as excerpted:
>
>> I lost the output from the previos build, and unable to regenerate the
>> issue after fooliwnf libxcb update guilde. But now I am stuck with
>> another error, when bulllding gcc.
>>
>>
>> /var/tmp/portage/sys-devel/gcc-4.1.2/
>
> gcc-4.1.2 ?  gcc 4.1 is a bit outdated.  You /may/ be able to simply
> unmerge it.  What versions of gcc do you have installed, anyway?  It's
> likely you have a 4.3 version, as gcc-4.3.2-r3 is the latest keyworded
> stable for amd64.
>
> A caution, however.  Until your whole system is rebuilt with the newer
> gccs, some C++ packages in particular may still link to the old
> versions.  But it should at least be possible to ignore the old gccs for
> the moment (emerge --resume --skipfirst if necessary) and build
> everything else.  If you're using FEATURES=buildpkg, it's easy enough to
> unmerge a package, see if anything breaks (run revdep-rebuild and see if
> there's anything that needs rebuilt, and hope it rebuilds fine), and
> remerge the binpkg if necessary.  That's what I'd do.
>
> If you're not running FEATURES=buildpkg, I'd suggest you consider it.
> Right before a system-wide rebuild is a great time to turn it on. =:^)
> But if you're not, you can use quickpkg to create a binpkg of a
> particular package before removing it for testing.  That way you still
> get the binpkg, and can remerge it if necessary, if you find you still
> need it.
>
> Anyway... after updating gcc to 4.3.2-r3 if you don't have it, and gcc-
> config-ing to it, you could emerge --emptytree @system @world so
> everything is built with it, and then unmerge older gcc versions,
> including the 4.1.2 that's giving you issues ATM.
>
> FWIW, on ~amd64, the only gcc I have currently installed is 4.4.1, as I
> unmerged earlier versions after I had rebuilt the entire system with it.
> I do remember having some issues rebuilding earlier gccs at one point,
> but with the entire system (other than those gccs) building with 4.4.1, I
> was able to unmerge them instead of rebuild them.
>
> Of course, I always do --update --deep --newuse, generally a couple times
> a week, and revdep-rebuild and --depclean afterward, to make sure the
> system stays consistent and keep the cruft to a minimum.  If you've let
> it build up by not regularly using --update --deep and not regularly
> doing --depcleans and revdep-rebuilds, you are likely to have quite some
> problems getting the system back in shape, as there will be quite some
> cruft buildup to clean out, and doing it incrementally as the updates
> show up is MUCH easier than letting it buildup and trying to do it all at
> once.
>
> --
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
>
>
>



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64]  Re: failing to emerge update
  2009-10-13 14:39     ` [gentoo-amd64] " Duncan
  2009-10-14 17:37       ` Mansour Al Akeel
@ 2009-10-14 23:49       ` Mansour Al Akeel
  2009-10-15  1:19         ` Duncan
  2009-10-15  1:58         ` David Fellows
  1 sibling, 2 replies; 14+ messages in thread
From: Mansour Al Akeel @ 2009-10-14 23:49 UTC (permalink / raw
  To: gentoo-amd64

Ok, I think I did something rally bad. I am unable to install emacs. 
Here's the output :
============================================================
These are the packages that would be merged, in order:

Calculating dependencies   ... done!
[ebuild  N    ] net-libs/liblockfile-1.06-r2  0 kB
[ebuild  N    ] app-emacs/emacs-common-gentoo-1.2  USE="X -emacs22icons" 0 kB
[ebuild  N    ] app-editors/emacs-23.1  USE="X alsa dbus gif gpm gtk jpeg png svg tiff xpm -Xaw3d -gzip-el -hesiod -kerberos -m17n-lib -motif -sound -source -toolkit-scroll-bars -xft" 30,648 kB
[ebuild  N    ] virtual/emacs-23  0 kB

Total: 4 packages (4 new), Size of downloads: 30,648 kB

Would you like to merge these packages? [Yes/No] 
>>> Verifying ebuild manifests

>>> Starting parallel fetch

>>> Emerging (1 of 4) net-libs/liblockfile-1.06-r2
 * liblockfile_1.06.tar.gz RMD160 SHA1 SHA256 size ;-) ...               [ ok ]
 * checking ebuild checksums ;-) ...                                     [ ok ]
 * checking auxfile checksums ;-) ...                                    [ ok ]
 * checking miscfile checksums ;-) ...                                   [ ok ]
>>> Unpacking source...
>>> Unpacking liblockfile_1.06.tar.gz to /var/tmp/portage/net-libs/liblockfile-1.06-r2/work
 * Applying liblockfile-1.06-glibc24.patch ...
  [ ok ]
 * Applying liblockfile-1.06-respectflags.patch ...
  [ ok ]
 * Applying liblockfile-orphan-file.patch ...
  [ ok ]
 * Running eautoreconf in '/var/tmp/portage/net-libs/liblockfile-1.06-r2/work/liblockfile-1.06' ...
 * Running aclocal ...
  [ !! ]

 * Failed Running aclocal !
 * 
 * Include in your bugreport the contents of:
 * 
 *   /var/tmp/portage/net-libs/liblockfile-1.06-r2/temp/aclocal.out

 * ERROR: net-libs/liblockfile-1.06-r2 failed:
 *   Failed Running aclocal !
 * 
 * Call stack:
 *     ebuild.sh, line   49:  Called src_unpack
 *   environment, line 2802:  Called eautoreconf
 *   environment, line  894:  Called eaclocal
 *   environment, line  833:  Called autotools_run_tool 'aclocal'
 *   environment, line  378:  Called die
 * The specific snippet of code:
 *           die "Failed Running $1 !";
 * 
 * If you need support, post the output of 'emerge --info =net-libs/liblockfile-1.06-r2',
 * the complete build log and the output of 'emerge -pqv =net-libs/liblockfile-1.06-r2'.
 * The complete build log is located at '/var/tmp/portage/net-libs/liblockfile-1.06-r2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/net-libs/liblockfile-1.06-r2/temp/environment'.
 * S: '/var/tmp/portage/net-libs/liblockfile-1.06-r2/work/liblockfile-1.06'

>>> Failed to emerge net-libs/liblockfile-1.06-r2, Log file:

>>>  '/var/tmp/portage/net-libs/liblockfile-1.06-r2/temp/build.log'

 * Messages for package net-libs/liblockfile-1.06-r2:



Any idea ? 




^ permalink raw reply	[flat|nested] 14+ messages in thread

* [gentoo-amd64]  Re: failing to emerge update
  2009-10-14 23:49       ` Mansour Al Akeel
@ 2009-10-15  1:19         ` Duncan
  2009-10-22  0:45           ` Mansour Al Akeel
  2009-10-15  1:58         ` David Fellows
  1 sibling, 1 reply; 14+ messages in thread
From: Duncan @ 2009-10-15  1:19 UTC (permalink / raw
  To: gentoo-amd64

Mansour Al Akeel posted on Wed, 14 Oct 2009 20:49:32 -0300 as excerpted:

> Ok, I think I did something rally bad. I am unable to install emacs.
> Here's the output :
> ============================================================
> These are the packages that would be merged, in order:
> 
> Calculating dependencies   ... done!
> [ebuild  N    ] net-libs/liblockfile-1.06-r2  0 kB
> [ebuild  N    ] app-emacs/emacs-common-gentoo-1.2
>  USE="X -emacs22icons" 0 kB
> [ebuild  N    ] app-editors/emacs-23.1  USE="X alsa dbus gif gpm gtk
>  jpeg png svg tiff xpm -Xaw3d -gzip-el -hesiod -kerberos -m17n-lib
>  -motif -sound -source -toolkit-scroll-bars -xft" 30,648 kB
> [ebuild  N    ] virtual/emacs-23  0 kB
> 
> Total: 4 packages (4 new), Size of downloads: 30,648 kB

>>>> Emerging (1 of 4) net-libs/liblockfile-1.06-r2

>  * Running eautoreconf in
>  '/var/tmp/portage/net-libs/liblockfile-1.06-r2/work/liblockfile-1.06'
>  ...
>  * Running aclocal ...
>   [ !! ]
> 
>  * Failed Running aclocal !
>  *
>  * Include in your bugreport the contents of: *
>  *   /var/tmp/portage/net-libs/liblockfile-1.06-r2/temp/aclocal.out

> Any idea ?

FWIW, it doesn't seem /that/ bad.  It just failed one step.  We don't 
know why, but the answer or at least a good hint should be in that 
aclocal.out file.  What does it say?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman




^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64] Re: failing to emerge update
  2009-10-14 23:49       ` Mansour Al Akeel
  2009-10-15  1:19         ` Duncan
@ 2009-10-15  1:58         ` David Fellows
  1 sibling, 0 replies; 14+ messages in thread
From: David Fellows @ 2009-10-15  1:58 UTC (permalink / raw
  To: gentoo-amd64

On Wed, 14 Oct 2009 20:49:32 -0300 
Mansour Al Akeel wrote -
> Ok, I think I did something rally bad. I am unable to install emacs. 

Have you checked the obvious?
 Do you have gigabytes of free space on the volume housing /var/tmp/portage?
 Portage leaves its temporary workspace on failure. You have had a lot of 
 falures lately.
 Sufficient free space on / and /usr?
 Hardware problems?
   cpu overheating - is the cpu fan running?
   general overheating? all fans running?
   Memory problems? perhaps reseat the memory modules.
   I/O errors?
   Corrupted file system? Try fsck.

   
Dave F



^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [gentoo-amd64]  Re: failing to emerge update
  2009-10-15  1:19         ` Duncan
@ 2009-10-22  0:45           ` Mansour Al Akeel
  0 siblings, 0 replies; 14+ messages in thread
From: Mansour Al Akeel @ 2009-10-22  0:45 UTC (permalink / raw
  To: gentoo-amd64

Thank you all. It was a matter of reinstalling m4. Things are working
fine and everything is updated. 



On Thu Oct 15,2009 01:19 am, Duncan wrote:
> Mansour Al Akeel posted on Wed, 14 Oct 2009 20:49:32 -0300 as excerpted:
> 
> > Ok, I think I did something rally bad. I am unable to install emacs.
> > Here's the output :
> > ============================================================
> > These are the packages that would be merged, in order:
> > 
> > Calculating dependencies   ... done!
> > [ebuild  N    ] net-libs/liblockfile-1.06-r2  0 kB
> > [ebuild  N    ] app-emacs/emacs-common-gentoo-1.2
> >  USE="X -emacs22icons" 0 kB
> > [ebuild  N    ] app-editors/emacs-23.1  USE="X alsa dbus gif gpm gtk
> >  jpeg png svg tiff xpm -Xaw3d -gzip-el -hesiod -kerberos -m17n-lib
> >  -motif -sound -source -toolkit-scroll-bars -xft" 30,648 kB
> > [ebuild  N    ] virtual/emacs-23  0 kB
> > 
> > Total: 4 packages (4 new), Size of downloads: 30,648 kB
> 
> >>>> Emerging (1 of 4) net-libs/liblockfile-1.06-r2
> 
> >  * Running eautoreconf in
> >  '/var/tmp/portage/net-libs/liblockfile-1.06-r2/work/liblockfile-1.06'
> >  ...
> >  * Running aclocal ...
> >   [ !! ]
> > 
> >  * Failed Running aclocal !
> >  *
> >  * Include in your bugreport the contents of: *
> >  *   /var/tmp/portage/net-libs/liblockfile-1.06-r2/temp/aclocal.out
> 
> > Any idea ?
> 
> FWIW, it doesn't seem /that/ bad.  It just failed one step.  We don't 
> know why, but the answer or at least a good hint should be in that 
> aclocal.out file.  What does it say?
> 
> -- 
> Duncan - List replies preferred.   No HTML msgs.
> "Every nonfree program has a lord, a master --
> and if you use the program, he is your master."  Richard Stallman
> 
> 



^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2009-10-22  0:45 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-10-13  3:58 [gentoo-amd64] failing to emerge update Mansour Al Akeel
2009-10-13  3:10 ` [gentoo-amd64] " Nikos Chantziaras
2009-10-13  4:09   ` Mansour Al Akeel
2009-10-13  6:10     ` Volker Armin Hemmann
2009-10-13  3:16 ` [gentoo-amd64] " Frank Peters
2009-10-13  3:17   ` Crístian Viana
2009-10-13  6:31 ` Alex Alexander
2009-10-13 13:25   ` Mansour Al Akeel
2009-10-13 14:39     ` [gentoo-amd64] " Duncan
2009-10-14 17:37       ` Mansour Al Akeel
2009-10-14 23:49       ` Mansour Al Akeel
2009-10-15  1:19         ` Duncan
2009-10-22  0:45           ` Mansour Al Akeel
2009-10-15  1:58         ` David Fellows

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox