[gentoo-amd64] unable to emerge anything

[gentoo-amd64] unable to emerge anything

[Paul Stear]

Hello,
I have been having problems for weeks and have had to reinstall. My 
motherboard SATA controller died so I have had to get a new motherboard 
and at the same time upgraded from a single to a x2 amd 64 processor.

I initially installed from an amd 64 minimal install 2006 disc as I 
couldn't get the 2007 ones to work.
I then restored my system from an external disk using rsync, rebooted and 
my system came to life and I could login to kde.  However the elation 
didn't last long.
I synced portage and tried to update world but no matter what program I 
try to install or update I get errors and each one fails.
The errors appear to be because of a multilib environment.
This is the error for sandbox

 * Building failed for ABI=x86!.  This usually means a broken
 * multilib setup.  Please fix that before filling a bugreport
 * against sandbox.

This is one of the errors for portage

checking size of long long... configure: error: cannot compute sizeof 
(long long)

Why is the sandbox install looking at ABI=x86 ? It should be amd64. but I 
can't find where this is set or how to move forward.

I even adjusted the /etc/make.profile to be no-multilib but that didn't 
solve the problems.

Thanks for your time and help  ---   please----
Paul
Below in my emerge --info

Portage 2.1.3.19 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, 
glibc-2.6.1-r0,glibc-2.5-r0, 2.6.23-gentoo-r6 x86_64)
=================================================================
System uname: 2.6.23-gentoo-r6 x86_64 AMD Athlon(tm) 64 X2 Dual Core 
Processor 4600+
Timestamp of tree: Tue, 05 Feb 2008 01:16:01 +0000
app-shells/bash:     3.2_p17-r1
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python:     2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.10-r5
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 
1.10
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.24
virtual/os-headers:  2.6.23-r2, 2.6.23-r3
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/fonts/fonts.conf /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-march=athlon64 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks fixpackages metadata-transfer parallel-fetch 
sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://distfiles.gentoo.org 
http://www.ibiblio.org/pub/Linux/distributions/gentoo 
http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ 
ftp://mirror.qubenet.net/mirror/gentoo/ 
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo 
http://pandemonium.tiscali.de/pub/gentoo/"
LANG="en_GB.UTF-8"
LINGUAS="en_GB"
MAKEOPTS="-j3"
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 --filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow 3dnowext X a52 acl acpi alsa amd64 avi bash-completion 
bitmap-fonts bzip2 cairo cdparanoia cdr clamav cli cracklib crypt cups 
dbus divx4linux dri dv dvd dvdr dvdread eds emboss encode esd evo fam 
ffmpeg firefox gdbm gif gphoto2 gpm gstreamer hal iconv imagemagick ipv6 
jack java javascript jpeg kde kerberos ldap lzomaildir mad midi mikmod 
mjpeg mmx mmxext mp3 mpeg mplayer mudflap ncurses nls nptl nptlonly 
nsplugin nvidia ogg opengl openmp oss pam pascal pcre pdf perl png pppd 
python qt qt3 qt3support qt4 quicktime readline reflection ruby samba 
scanner sdl session spell spl sqlite sse sse2 sse3 ssl svg tcpd theora 
tiff truetype truetype-fonts type1-fonts unicode usb v4l vorbis x264 xine 
xml xml2 xorg xv xvid zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm 
alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug 
ladspa lfloat linear meter mulaw multi null plug rate route share shm 
softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon 
authn_dbm authn_default authn_file authz_dbm authz_default 
authz_groupfile authz_host authz_owner authz_user autoindex cache dav 
dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache 
filter headers include info log_config logio mem_cache mime mime_magic 
negotiation rewrite setenvif speling status unique_id userdir usertrack 
vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" 
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb 
ncurses text" LINGUAS="en_GB" USERLAND="GNU" VIDEO_CARDS="nvidia vesa"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, 
LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, 
PORTAGE_RSYNC_EXTRA_OPTS

-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] unable to emerge anything

[Mark Haney]

Paul Stear wrote:
> Hello,
> I have been having problems for weeks and have had to reinstall. My 
> motherboard SATA controller died so I have had to get a new motherboard 
> and at the same time upgraded from a single to a x2 amd 64 processor.
> 
> I initially installed from an amd 64 minimal install 2006 disc as I 
> couldn't get the 2007 ones to work.
> I then restored my system from an external disk using rsync, rebooted and 
> my system came to life and I could login to kde.  However the elation 
> didn't last long.
> I synced portage and tried to update world but no matter what program I 
> try to install or update I get errors and each one fails.
> The errors appear to be because of a multilib environment.
> This is the error for sandbox
> 
>  * Building failed for ABI=x86!.  This usually means a broken
>  * multilib setup.  Please fix that before filling a bugreport
>  * against sandbox.
> 
> This is one of the errors for portage
> 
>

Just a word of advice, please don't post the exact same message under 
two different subject lines.  It's annoying.

However, have you tried beso's solution of pulling and rebuild glibc, 
etc?  Sounds to me like that would at least fix part of it if not all.

-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] unable to emerge anything

[Beso]

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

2008/2/5, Mark Haney <mhaney@ercbroadband.org>:
>
> Paul Stear wrote:
> > Hello,
> > I have been having problems for weeks and have had to reinstall. My
> > motherboard SATA controller died so I have had to get a new motherboard
> > and at the same time upgraded from a single to a x2 amd 64 processor.
> >
> > I initially installed from an amd 64 minimal install 2006 disc as I
> > couldn't get the 2007 ones to work.
> > I then restored my system from an external disk using rsync, rebooted
> and
> > my system came to life and I could login to kde.  However the elation
> > didn't last long.
> > I synced portage and tried to update world but no matter what program I
> > try to install or update I get errors and each one fails.
> > The errors appear to be because of a multilib environment.
> > This is the error for sandbox
> >
> >  * Building failed for ABI=x86!.  This usually means a broken
> >  * multilib setup.  Please fix that before filling a bugreport
> >  * against sandbox.
> >
> > This is one of the errors for portage
> >
> >
>
> Just a word of advice, please don't post the exact same message under
> two different subject lines.  It's annoying.
>
> However, have you tried beso's solution of pulling and rebuild glibc,
> etc?  Sounds to me like that would at least fix part of it if not all.
>
> --
> Libenter homines id quod volunt credunt -- Caius Julius Caesar


i suspect that the system does some kind of damaging stuff because of the 2
versions of glibc. having 2 glibc version should never happen and i really
think that that is the main problem. remove the older one and reemerge the
new one and then emerge again the system.
if this doesn't work, copy the /etc to somewhere safe then go here:
http://www.funtoo.org/linux/amd64/funtoo-amd64-2008.02.02/
get the stage3 and untar it from a livedvd or similar to the gentoo root
partition. after that put again the /etc backuped to its place and then log
into gentoo terminal, not kde, and try to update the world. if this still
doesn't work, then ask again.

ps. don't ask the same question on the same mailing list with 2 different
subjects as you'll finish in the banlist for 99% of the readers and you
won't get any help.

Mark Haney
> Sr. Systems Administrator
> ERC Broadband
> (828) 350-2415
>
> Call (866) ERC-7110 for after hours support
> --
> gentoo-amd64@lists.gentoo.org mailing list
>
>


-- 
dott. ing. beso

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

Re: [gentoo-amd64] unable to emerge anything

[Paul Stear]

>
> ps. don't ask the same question on the same mailing list with 2
> different subjects as you'll finish in the banlist for 99% of the
> readers and you won't get any help.
>
> Mark Haney
Thanks for your advise, I'll try it now.

The reason for 2 posts is that I didn't think the first one was sent. I 
had so much stuff on the desktop, the computer crashed so I sent a second 
one after a reboot.
Sorry for any problems caused.
Paul



-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] unable to emerge anything

[Mark Haney]

Paul Stear wrote:
> 
>> ps. don't ask the same question on the same mailing list with 2
>> different subjects as you'll finish in the banlist for 99% of the
>> readers and you won't get any help.
>>
>> Mark Haney
> Thanks for your advise, I'll try it now.
> 
> The reason for 2 posts is that I didn't think the first one was sent. I 
> had so much stuff on the desktop, the computer crashed so I sent a second 
> one after a reboot.
> Sorry for any problems caused.
> Paul
> 
> 
> 

It's all good.  Personally, I would prefer 2 identical posts (with same 
subject line) rather than 2 identical with different subject lines. 
Makes grouping by thread harder.


-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] unable to emerge anything

[Mark Haney]

Paul Stear wrote:

> Well thank you Mark and Beso,
> The above worked well and I think I now have my beloved gentoo back to 
> normal.
> It's great to know that comprehensive help is available to solve even the 
> most complex problems.
> kind regards
> Paul
> 
> 
> 

Honestly, the credit goes all to Beso.  I simply re-iterated what he 
said since it wasn't apparent that you had tried anything between the 2 
posts.  (Little did I know it was due to a possible email failure.  He's 
been (and is) a great resource to have on this list.


-- 
Libenter homines id quod volunt credunt -- Caius Julius Caesar


Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415

Call (866) ERC-7110 for after hours support
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] unable to emerge anything

[Paul Stear]

> i suspect that the system does some kind of damaging stuff because of
> the 2 versions of glibc. having 2 glibc version should never happen and
> i really think that that is the main problem. remove the older one and
> reemerge the new one and then emerge again the system.
> if this doesn't work, copy the /etc to somewhere safe then go here:
> http://www.funtoo.org/linux/amd64/funtoo-amd64-2008.02.02/
> get the stage3 and untar it from a livedvd or similar to the gentoo
> root partition. after that put again the /etc backuped to its place and
> then log into gentoo terminal, not kde, and try to update the world. if
> this still doesn't work, then ask again.

Well thank you Mark and Beso,
The above worked well and I think I now have my beloved gentoo back to 
normal.
It's great to know that comprehensive help is available to solve even the 
most complex problems.
kind regards
Paul



-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] unable to emerge anything

[Paul Stear]

On Tuesday 05 February 2008, Mark Haney wrote:
> Paul Stear wrote:
> > Well thank you Mark and Beso,
> > The above worked well and I think I now have my beloved gentoo back
> > to normal.
> > It's great to know that comprehensive help is available to solve even
> > the most complex problems.
> > kind regards
> > Paul
Well I think my elation was a bit premature last night..  I ran 
revdep-update and the 4 or 5 items that should be re emerged failed. So I 
went to be dreaming about what could be the matter, after all the emerge 
world I did after the recovery worked perfectly.
These are the items that were updated:-
groff-1.19.2-r1
com_err-1.40.4
mit-krb5-1.5.3-r1
nano-2.0.6
psmisc-22.5-r2
gcc-4.1.2
openssl-0.9.8g
openldap-2.3.39-r2
db-4.5.20_p2
pycrypto-2.0.1-r6
busybox-1.8.2
openssh-4.7_p1-r1
Quite a few of these show conflicting files in their logs because I do not 
have collision protect on -- should I have?

These are the items that revdep-rebuild suggested needed to be rebuilt:
ffmpeg-0.4.9_p20070616
libquicktime-1.0.1
mplayer-1.0_rc2_p24929-r1
xine-lib-1.1.8
All of the above required libx264.so.54

Today I have synced portage and have 1 update....It failed

This is today's error for man-1.6f
cd src; make
libsandbox:  Can't resolve getcwd: (null)
make: *** [source] Error 1
x86_64-pc-linux-gnu-gcc -march=athlon64 -O2 -pipe   -c -o genlib.o 
genlib.c
make: *** Waiting for unfinished jobs....
x86_64-pc-linux-gnu-gcc  -o gencat gencat.o genlib.o
make[1]: Leaving directory 
`/var/tmp/portage/sys-apps/man-1.6f/work/man-1.6f/gencat'

Just for completeness below is my emerge --info
Portage 2.1.3.19 (default-linux/amd64/2007.0/desktop, gcc-4.1.2, 
glibc-2.6.1-r0, 2.6.23-gentoo-r6 x86_64)
=================================================================
System uname: 2.6.23-gentoo-r6 x86_64 AMD Athlon(tm) 64 X2 Dual Core 
Processor 4600+
Timestamp of tree: Wed, 06 Feb 2008 01:16:01 +0000
app-shells/bash:     3.2_p17-r1
dev-java/java-config: 1.3.7, 2.0.33-r1
dev-lang/python:     2.4.4-r6
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.10-r5
sys-apps/sandbox:    1.2.18.1-r2
sys-devel/autoconf:  2.13, 2.61-r1
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 
1.10
sys-devel/binutils:  2.18-r1
sys-devel/gcc-config: 1.4.0-r4
sys-devel/libtool:   1.5.24
virtual/os-headers:  2.6.23-r3
ACCEPT_KEYWORDS="amd64"
CBUILD="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O2 -pipe"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-march=athlon64 -O2 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="ccache distlocks fixpackages metadata-transfer parallel-fetch 
sandbox sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://distfiles.gentoo.org 
http://www.ibiblio.org/pub/Linux/distributions/gentoo 
http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/ 
ftp://mirror.qubenet.net/mirror/gentoo/ 
ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo 
http://pandemonium.tiscali.de/pub/gentoo/"
LANG="en_GB.UTF-8"
LINGUAS="en_GB"
MAKEOPTS="-j3"
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 --filter=H_**/files/digest-*"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
USE="3dnow 3dnowext X a52 acl acpi alsa amd64 avi bash-completion 
bitmap-fonts bzip2 cairo cdparanoia cdr clamav cli cracklib crypt cups 
dbus divx4linux dri dv dvd dvdr dvdread eds emboss encode esd evo fam 
ffmpeg firefox gdbm gif gphoto2 gpm gstreamer hal iconv imagemagick ipv6 
jack java javascript jpeg kde kerberos ldap lzomaildir mad midi mikmod 
mjpeg mmx mmxext mp3 mpeg mplayer mudflap ncurses nls nptl nptlonly 
nsplugin nvidia ogg opengl openmp oss pam pascal pcre pdf perl png pppd 
python qt qt3 qt3support qt4 quicktime readline reflection ruby samba 
scanner sdl session spell spl sqlite sse sse2 sse3 ssl svg tcpd theora 
tiff truetype truetype-fonts type1-fonts unicode usb v4l vorbis x264 xine 
xml xml2 xorg xv xvid zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm 
alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug 
ladspa lfloat linear meter mulaw multi null plug rate route share shm 
softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon 
authn_dbm authn_default authn_file authz_dbm authz_default 
authz_groupfile authz_host authz_owner authz_user autoindex cache dav 
dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache 
filter headers include info log_config logio mem_cache mime mime_magic 
negotiation rewrite setenvif speling status unique_id userdir usertrack 
vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux" 
LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb 
ncurses text" LINGUAS="en_GB" USERLAND="GNU" VIDEO_CARDS="nvidia vesa"
Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, 
LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS, 
PORTAGE_RSYNC_EXTRA_OPTS

I just don't know what to try next ----- I await your guidance

Paul

This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] unable to emerge anything

[Beso]

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

2008/2/6, Paul Stear <gentoo@appjaws.plus.com>:
>
> On Tuesday 05 February 2008, Mark Haney wrote:
> > Paul Stear wrote:
> > > Well thank you Mark and Beso,
> > > The above worked well and I think I now have my beloved gentoo back
> > > to normal.
> > > It's great to know that comprehensive help is available to solve even
> > > the most complex problems.
> > > kind regards
> > > Paul
> Well I think my elation was a bit premature last night..  I ran
> revdep-update and the 4 or 5 items that should be re emerged failed. So I
> went to be dreaming about what could be the matter, after all the emerge
> world I did after the recovery worked perfectly.
> These are the items that were updated:-
> groff-1.19.2-r1
> com_err-1.40.4
> mit-krb5-1.5.3-r1
> nano-2.0.6
> psmisc-22.5-r2
> gcc-4.1.2
> openssl-0.9.8g
> openldap-2.3.39-r2
> db-4.5.20_p2
> pycrypto-2.0.1-r6
> busybox-1.8.2
> openssh-4.7_p1-r1
> Quite a few of these show conflicting files in their logs because I do not
> have collision protect on -- should I have?
>
These are the items that revdep-rebuild suggested needed to be rebuilt:
> ffmpeg-0.4.9_p20070616
> libquicktime-1.0.1
> mplayer-1.0_rc2_p24929-r1
> xine-lib-1.1.8
> All of the above required libx264.so.54


these are multimedia stuff, that is not manadatory before the system is to
be fixed, so we'll leave them for after. these shouldn't give any problems.

Today I have synced portage and have 1 update....It failed
>
> This is today's error for man-1.6f
> cd src; make
> libsandbox:  Can't resolve getcwd: (null)
> make: *** [source] Error 1
> x86_64-pc-linux-gnu-gcc -march=athlon64 -O2 -pipe   -c -o genlib.o
> genlib.c
> make: *** Waiting for unfinished jobs....
> x86_64-pc-linux-gnu-gcc  -o gencat gencat.o genlib.o
> make[1]: Leaving directory
> `/var/tmp/portage/sys-apps/man-1.6f/work/man-1.6f/gencat'
>
> Just for completeness below is my emerge --info
> Portage 2.1.3.19 (default-linux/amd64/2007.0/desktop, gcc-4.1.2,
> glibc-2.6.1-r0, 2.6.23-gentoo-r6 x86_64)
> =================================================================
> System uname: 2.6.23-gentoo-r6 x86_64 AMD Athlon(tm) 64 X2 Dual Core
> Processor 4600+
> Timestamp of tree: Wed, 06 Feb 2008 01:16:01 +0000
> app-shells/bash:     3.2_p17-r1
> dev-java/java-config: 1.3.7, 2.0.33-r1
> dev-lang/python:     2.4.4-r6
> dev-python/pycrypto: 2.0.1-r6
> sys-apps/baselayout: 1.12.10-r5
> sys-apps/sandbox:    1.2.18.1-r2
> sys-devel/autoconf:  2.13, 2.61-r1
> sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2,
> 1.10
> sys-devel/binutils:  2.18-r1
> sys-devel/gcc-config: 1.4.0-r4
> sys-devel/libtool:   1.5.24
> virtual/os-headers:  2.6.23-r3
> ACCEPT_KEYWORDS="amd64"
> CBUILD="x86_64-pc-linux-gnu"
> CFLAGS="-march=athlon64 -O2 -pipe"


i suggest this flags instead of yours usually they're a little more
processor based and are not experimental ones as usually they say about
them:
CFLAGS="-Os -march=k8 -mno-tls-direct-seg-refs -mmmx -msse3 -pipe
-fomit-frame-pointer"

CHOST="x86_64-pc-linux-gnu"
> CONFIG_PROTECT="/etc /usr/kde/3.5/env /usr/kde/3.5/share/config
> /usr/kde/3.5/shutdown /usr/share/X11/xkb /usr/share/config"
> CONFIG_PROTECT_MASK="/etc/env.d /etc/env.d/java/ /etc/gconf
> /etc/java-config/vms/ /etc/revdep-rebuild /etc/splash /etc/terminfo
> /etc/udev/rules.d"
> CXXFLAGS="-march=athlon64 -O2 -pipe"

this is the same and is faster to write and to have it updated.
CXXFLAGS="${CFLAGS}"
also add:
LDFLAGS="-Wl,--as-needed,-O1 -Wl,--enable-new-dtags -Wl,--sort-common -s"

DISTDIR="/usr/portage/distfiles"
> FEATURES="ccache distlocks fixpackages metadata-transfer parallel-fetch
> sandbox sfperms strict unmerge-orphans userfetch"


if you experience collision problems add collision-protect to the features.
you should have some better protection between packages and should avoid
packages from writing files owned by other packages. this could provoke some
more emerge errors than before because there are quite some packages that
overwrite files

GENTOO_MIRRORS="http://distfiles.gentoo.org
> http://www.ibiblio.org/pub/Linux/distributions/gentoo
> http://ftp.belnet.be/mirror/rsync.gentoo.org/gentoo/
> ftp://mirror.qubenet.net/mirror/gentoo/
> ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo
> http://pandemonium.tiscali.de/pub/gentoo/"
> LANG="en_GB.UTF-8"
> LINGUAS="en_GB"
> MAKEOPTS="-j3"


set MAKEOPTS="-j3" to MAKEOPTS="-j5 -s ".  if you experience compile problem
decrease the j number to 1.

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
> --filter=H_**/files/digest-*"
> PORTAGE_TMPDIR="/var/tmp"
> PORTDIR="/usr/portage"
> PORTDIR_OVERLAY="/usr/local/portage"
> SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage"
> USE="3dnow 3dnowext X a52 acl acpi alsa amd64 avi bash-completion
> bitmap-fonts bzip2 cairo cdparanoia cdr clamav cli cracklib crypt cups
> dbus divx4linux dri dv dvd dvdr dvdread eds emboss encode esd evo fam
> ffmpeg firefox gdbm gif gphoto2 gpm gstreamer hal iconv imagemagick ipv6
> jack java javascript jpeg kde kerberos ldap lzomaildir mad midi mikmod
> mjpeg mmx mmxext mp3 mpeg mplayer mudflap ncurses nls nptl nptlonly
> nsplugin nvidia ogg opengl openmp oss pam pascal pcre pdf perl png pppd
> python qt qt3 qt3support qt4 quicktime readline reflection ruby samba
> scanner sdl session spell spl sqlite sse sse2 sse3 ssl svg tcpd theora
> tiff truetype truetype-fonts type1-fonts unicode usb v4l vorbis x264 xine
> xml xml2 xorg xv xvid zlib" ALSA_CARDS="emu10k1" ALSA_PCM_PLUGINS="adpcm
> alaw asym copy dmix dshare dsnoop empty extplug file hooks iec958 ioplug
> ladspa lfloat linear meter mulaw multi null plug rate route share shm
> softvol" APACHE2_MODULES="actions alias auth_basic authn_alias authn_anon
> authn_dbm authn_default authn_file authz_dbm authz_default
> authz_groupfile authz_host authz_owner authz_user autoindex cache dav
> dav_fs dav_lock deflate dir disk_cache env expires ext_filter file_cache
> filter headers include info log_config logio mem_cache mime mime_magic
> negotiation rewrite setenvif speling status unique_id userdir usertrack
> vhost_alias" ELIBC="glibc" INPUT_DEVICES="keyboard mouse" KERNEL="linux"
> LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb
> ncurses text" LINGUAS="en_GB" USERLAND="GNU" VIDEO_CARDS="nvidia vesa"
> Unset:  CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL,
> LDFLAGS, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS,
> PORTAGE_RSYNC_EXTRA_OPTS
>
> I just don't know what to try next ----- I await your guidance
>
> Paul


now, do a qlist on all the packages that had collision problems. do this
package by package. for example do qlist groff and then remove all the files
in the list generated by groff. then emerge groff with --oneshot and
--nodeps options like this emerge groff --oneshot --nodeps -v. this should
avoid collision and install groff. do this for any package that fails for
collision. the only problems that you might get then are compilation
problems, but that are to be seen problem by problem.
after everything is ok you need to clean the unneeded stuff with emerge
--clean --depclean --deep -vp if you're satisfied with the packges that are
to be clean (look if you don't remove packages that you want to use, and
write them down for a reemerge after the clean) then remove the p at the end
and let portage clean the tree. now do emerge --regen to regenerate the tree
cache and then revdep-rebuild. if you see important packages like kdebase,
kdelibs, expat, gcc (gcj use flag in gcc always triggers a rebuild of gcc
and i need to fix this upon my box too), glibc then let him do the revdep,
but if there aren't such packages then do emerge world -uDNvp and only after
that is finished revdep the packages. now you should have the world
consistent and quite clean.
the only thing that is still there to do is to install the cruf removal
script and the distfiles cleaner one. in the forums and on gentoo-wiki you
should find the way to use them. the first script generates a long list of
"unneeded" files while the second can do a clean on the distfiles and on the
binpackages. the list generated need to be controlled before running the
help script that move the files somewhere else because it puts into all the
files in the /home and /etc that normally are needed by the user. so the
cruft file needs to be carefully examined in search for the files that need
not be deleted/moved for backup. after deleting rerun revdep-rebuild to
eventually fix missing stuff.
now you'll have a clean and working package.

-- 
dott. ing. beso

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

Re: [gentoo-amd64] unable to emerge anything

[Paul Stear]

On Wednesday 06 February 2008, Beso wrote:
> 2008/2/6, Paul Stear <gentoo@appjaws.plus.com>:

> > Well I think my elation was a bit premature last night..  I ran
> > revdep-update and the 4 or 5 items that should be re emerged failed.
> > So I went to be dreaming about what could be the matter, after all
> > the emerge world I did after the recovery worked perfectly.

> now you'll have a clean and working package.

Thank you again Beso, I have change make.conf and will continue with your 
suggestions.
regards
Paul

-- 
This message has been sent using kmail with gentoo linux
-- 
gentoo-amd64@lists.gentoo.org mailing list

[gentoo-amd64] Re: unable to emerge anything

[Duncan]

Beso <givemesugarr@gmail.com> posted
d257c3560802060159q3a5b0334gd40b5d8b25aa348f@mail.gmail.com, excerpted
below, on  Wed, 06 Feb 2008 09:59:29 +0000:

>> CFLAGS="-march=athlon64 -O2 -pipe"
> 
> 
> i suggest this flags instead of yours usually they're a little more
> processor based and are not experimental ones as usually they say about
> them:
> CFLAGS="-Os -march=k8 -mno-tls-direct-seg-refs -mmmx -msse3 -pipe
> -fomit-frame-pointer"

-fomit-frame-pointer is the default for -O and above on amd64/x86_64, as 
it doesn't interfere with debugging here as it does on 32-bit x86, so 
omitting it saves on complexity without changing the compiled result.  Of 
course, it's still useful for 32-bit, but there's only a very few 
programs that portage compiles as 32-bit on amd64 anyway (and even there, 
CFLAGS aren't really used except for sandbox, because gcc does its own 
bootstrapping and glibc is considered critical enough it basically sets 
its own very strict CFLAGS in the ebuild).

-Os I used to use, for reasons explained in detail in a post to the list 
some time ago but briefly, cache size restrictions tend to matter more 
than pure cycle optimization on modern processors, so -Os generally made 
more sense to me than -O2.  However, with gcc-4.2, several optmizations 
that used to be in -Os only, made it into -O2, and -O2 now includes a 
couple of cache optimizers that raw size optimization misses, so it's not 
as critical, now.  Given that -O2 tends to be the recommended for Gentoo 
and more widely tested than -Os, I've therefore switched back to it.

-mmmx is included in the default for -march=k8, so that should be 
superfluous.  However, -msse3 is NOT included, as the original amd chips 
didn't have it.  Newer amd CPUs DO include sse3 (look for pni in the 
flags line(s) of /proc/cpuinfo), so unlike -mmmx it's worth specifying 
-msse3 if your CPU has it.

What about -mno-tls-direct-seg-refs?  Why do you use that?  The gcc 
manpage doesn't have enough info to convince me it's useful, and in fact, 
implies the reverse, since it defaults glibc folks to using it, which 
implies a reason for that default.  I'd therefore love to see a 
discussion of the flag with enough information to justify a better 
informed decision, as yours presumably is given your depth of knowledge 
and activity on this list.

FWIW, here's my CFLAGS.  CXXFLAGS are similar, minus -combine (mentioned 
below) and -freorder-blocks-and-partition (for similar reasons).  
-combine and -ftree-vectorize still cause occasional problems, which I 
avoid on a case by case basis as I encounter them, with an appropriate 
entry in /etc/portage/env/<cat>/<pkg>, but in general, these flags have 
worked well for me for some time.  I can explain why I use each one if 
anyone wants to know.

CFLAGS="-march=k8 -msse3 -O2 -pipe -frename-registers -fweb -ftree-
vectorize -freorder-blocks-and-partition -combine -fgcse-sm -fgcse-las -
fgcse-after-reload -fmerge-all-constants"

>> CXXFLAGS="-march=athlon64 -O2 -pipe"
> 
> this is the same and is faster to write and to have it updated.
> CXXFLAGS="${CFLAGS}"

The exception would be if your CFLAGS include things like -combine, which 
doesn't work so well on C++ so shouldn't be in CXXFLAGS.  (For -combine 
specifically, gcc ignores it in such cases, but spits a warning, which 
various configure scripts interpret as a problem causing them to screwup, 
so it's best to leave it out of CXXFLAGS entirely.)

> also add:
> LDFLAGS="-Wl,--as-needed,-O1 -Wl,--enable-new-dtags -Wl,--sort-common
> -s"

Could you point me to documentation on LDFLAGS in general, or at least 
--enable-new-dtags and --sort-common?  I use --as-needed already 
( documentation at http://www.gentoo.org/proj/en/qa/asneeded.xml ), as 
well as -z,now (security thing as mentioned in portage's QA warnings if 
you have them enabled for setuid/setgid applications, but I find it 
useful in general, and no, it doesn't simply counteract --as-needed), but 
have yet to find a resource even close to as helpful for LDFLAGS in 
general as "man gcc" is for CFLAGS, so I'm left asking about them one at 
a time as I see them, and I've not seen those yet.  Again, a discussion 
with enough info to make an informed decision would be invaluable!  I 
don't even know what the options are at this point, and that's 
frustrating!

>> FEATURES="ccache distlocks fixpackages metadata-transfer parallel-fetch
>> sandbox sfperms strict unmerge-orphans userfetch"
> 
> if you experience collision problems add collision-protect to the
> features. you should have some better protection between packages and
> should avoid packages from writing files owned by other packages. this
> could provoke some more emerge errors than before because there are
> quite some packages that overwrite files

Agreed.  It's worth mentioning COLLISION_IGNORE, which you can set in 
make.conf to avoid specific known collisions, especially if they are 
known to be "safe", that is, something like icons or the like (using an 
example from the recent KDE4-svn overlay work, upstream was changing them 
fast enough to make it not worth filing bugs with Gentoo over), that it 
really doesn't matter if a couple of packages are fighting over.  
Differing config files, OTOH, you probably want to know about!

>> MAKEOPTS="-j3"
> 
> 
> set MAKEOPTS="-j3" to MAKEOPTS="-j5 -s ".  if you experience compile
> problem decrease the j number to 1.

Note that there are occasional parallel make issues with -jX, where X>1 
or not existent (-j by itself indicates unlimited jobs).  These don't 
occur frequently at -j2 as it's so heavily used by Gentooers everywhere 
so those occurring there tend to have been eliminated already.  However, 
as the number of jobs increase, so does the likelihood of running into 
parallel make issues.  make errors indicating file or directory not found 
are the classic example, so any time you see one of those, try 
MAKEOPTS=-j1 emerge <whatever> and you'll likely find it gone.  If so, 
file a bug with [parallel make] as well as the package name in the 
subject line (assuming there's not yet one filed), and help get it fixed! 
=8^)

FWIW, I run MAKEOPTS="-j20 -l12" (up to 20 jobs, but don't start any more 
if the load is above 12) here.  Dual-dual-core Opteron 290s, 8 gig RAM, 
PORTAGE_TMPDIR pointing at a tmpfs so all those temp files don't hit 
disk.  With PORTAGE_NICENESS=19, and with kernel 2.6.24's new per-user 
scheduling turned on (and with Hz=300, voluntary preemption, so it's not 
a special real-time kernel or anything by any stretch), I can still 
listen to streaming audio and even run a moderately sized visualization 
window (amarok with the scrolling voice-print analyzer going in its own 
window) without audio pause or undue jerkiness (there's a bit, but under 
a load of 3 per core and no real-time preemption, one might expect that)
of the visualization.    If I'm feeling adventurous and don't have 
anything else critical going on, I'll occasionally try -j by itself, just 
to see how high I can run the load average. A 400-500 load average is 
doable with kernel compiles, for instance, and nicely entertaining! =8^)  
It still amazes me how well the system copes with even that, and it was 
even more amazing back with dual-single-cores (242s)!

-- 
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

-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] Re: unable to emerge anything

[Beso]

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

2008/2/6, Duncan <1i5t5.duncan@cox.net>:
>
> Beso <givemesugarr@gmail.com> posted
> d257c3560802060159q3a5b0334gd40b5d8b25aa348f@mail.gmail.com, excerpted
> below, on  Wed, 06 Feb 2008 09:59:29 +0000:
>
> >> CFLAGS="-march=athlon64 -O2 -pipe"
> >
> >
> > i suggest this flags instead of yours usually they're a little more
> > processor based and are not experimental ones as usually they say about
> > them:
> > CFLAGS="-Os -march=k8 -mno-tls-direct-seg-refs -mmmx -msse3 -pipe
> > -fomit-frame-pointer"
>
> -fomit-frame-pointer is the default for -O and above on amd64/x86_64, as
> it doesn't interfere with debugging here as it does on 32-bit x86, so
> omitting it saves on complexity without changing the compiled result.  Of
> course, it's still useful for 32-bit, but there's only a very few
> programs that portage compiles as 32-bit on amd64 anyway (and even there,
> CFLAGS aren't really used except for sandbox, because gcc does its own
> bootstrapping and glibc is considered critical enough it basically sets
> its own very strict CFLAGS in the ebuild).


i tend to always add it since i don't want to always look at what the arch
would do later.

-Os I used to use, for reasons explained in detail in a post to the list
> some time ago but briefly, cache size restrictions tend to matter more
> than pure cycle optimization on modern processors, so -Os generally made
> more sense to me than -O2.  However, with gcc-4.2, several optmizations
> that used to be in -Os only, made it into -O2, and -O2 now includes a
> couple of cache optimizers that raw size optimization misses, so it's not
> as critical, now.  Given that -O2 tends to be the recommended for Gentoo
> and more widely tested than -Os, I've therefore switched back to it.


i tend to think that Os should be gentoo's default, since it adds some
options for cache and disk occupation and since i've always been good with
it.

-mmmx is included in the default for -march=k8, so that should be
> superfluous.  However, -msse3 is NOT included, as the original amd chips
> didn't have it.  Newer amd CPUs DO include sse3 (look for pni in the
> flags line(s) of /proc/cpuinfo), so unlike -mmmx it's worth specifying
> -msse3 if your CPU has it.


when i've added it it wasn't included by default.

What about -mno-tls-direct-seg-refs?  Why do you use that?  The gcc
> manpage doesn't have enough info to convince me it's useful, and in fact,
> implies the reverse, since it defaults glibc folks to using it, which
> implies a reason for that default.  I'd therefore love to see a
> discussion of the flag with enough information to justify a better
> informed decision, as yours presumably is given your depth of knowledge
> and activity on this list.


this should help with virtualizazion apps. xen won't work well without it
with large system memory. without xen or other virt apps this shouldn't
influence much on the packages.

FWIW, here's my CFLAGS.  CXXFLAGS are similar, minus -combine (mentioned
> below) and -freorder-blocks-and-partition (for similar reasons).
> -combine and -ftree-vectorize still cause occasional problems, which I
> avoid on a case by case basis as I encounter them, with an appropriate
> entry in /etc/portage/env/<cat>/<pkg>, but in general, these flags have
> worked well for me for some time.  I can explain why I use each one if
> anyone wants to know.
>
> CFLAGS="-march=k8 -msse3 -O2 -pipe -frename-registers -fweb -ftree-
> vectorize -freorder-blocks-and-partition -combine -fgcse-sm -fgcse-las -
> fgcse-after-reload -fmerge-all-constants"
>
> >> CXXFLAGS="-march=athlon64 -O2 -pipe"
> >
> > this is the same and is faster to write and to have it updated.
> > CXXFLAGS="${CFLAGS}"
>
> The exception would be if your CFLAGS include things like -combine, which
> doesn't work so well on C++ so shouldn't be in CXXFLAGS.  (For -combine
> specifically, gcc ignores it in such cases, but spits a warning, which
> various configure scripts interpret as a problem causing them to screwup,
> so it's best to leave it out of CXXFLAGS entirely.)
>
> > also add:
> > LDFLAGS="-Wl,--as-needed,-O1 -Wl,--enable-new-dtags -Wl,--sort-common
> > -s"
>
> Could you point me to documentation on LDFLAGS in general, or at least
> --enable-new-dtags and --sort-common?  I use --as-needed already
> ( documentation at http://www.gentoo.org/proj/en/qa/asneeded.xml ), as
> well as -z,now (security thing as mentioned in portage's QA warnings if
> you have them enabled for setuid/setgid applications, but I find it
> useful in general, and no, it doesn't simply counteract --as-needed), but
> have yet to find a resource even close to as helpful for LDFLAGS in
> general as "man gcc" is for CFLAGS, so I'm left asking about them one at
> a time as I see them, and I've not seen those yet.  Again, a discussion
> with enough info to make an informed decision would be invaluable!  I
> don't even know what the options are at this point, and that's
> frustrating!


--sort-common is to prevent gaps between symbols due to alignment
constraints, presumably increasing efficiency layout.
here's an interesting topic on ldflags:
http://forums.gentoo.org/viewtopic-t-67777.html

--enable-new-dtags should be default for current binutils but it  was there
from my 3 years old make.conf so it is still there. adding it again
shouldn't do harm.

>> FEATURES="ccache distlocks fixpackages metadata-transfer parallel-fetch
> >> sandbox sfperms strict unmerge-orphans userfetch"
> >
> > if you experience collision problems add collision-protect to the
> > features. you should have some better protection between packages and
> > should avoid packages from writing files owned by other packages. this
> > could provoke some more emerge errors than before because there are
> > quite some packages that overwrite files
>
> Agreed.  It's worth mentioning COLLISION_IGNORE, which you can set in
> make.conf to avoid specific known collisions, especially if they are
> known to be "safe", that is, something like icons or the like (using an
> example from the recent KDE4-svn overlay work, upstream was changing them
> fast enough to make it not worth filing bugs with Gentoo over), that it
> really doesn't matter if a couple of packages are fighting over.
> Differing config files, OTOH, you probably want to know about!


that's why i don't have it set. i only have set this:
FEATURES="parallel-fetch ccache -strict -sandbox buildpkg"
i use -strict since i have a quite high live ebuilds use that sometimes
require manual handling, and i've disabled sandbox since it pisses me off
with some xorg ebuilds and ati-drivers. i've now switched to paludis which
is faster or resolving deps for world and is more able to handle external
overlays directly. though, it lacks pkging and for some packages i still use
portage.

>> MAKEOPTS="-j3"
> >
> >
> > set MAKEOPTS="-j3" to MAKEOPTS="-j5 -s ".  if you experience compile
> > problem decrease the j number to 1.
>
> Note that there are occasional parallel make issues with -jX, where X>1
> or not existent (-j by itself indicates unlimited jobs).  These don't
> occur frequently at -j2 as it's so heavily used by Gentooers everywhere
> so those occurring there tend to have been eliminated already.  However,
> as the number of jobs increase, so does the likelihood of running into
> parallel make issues.  make errors indicating file or directory not found
> are the classic example, so any time you see one of those, try
> MAKEOPTS=-j1 emerge <whatever> and you'll likely find it gone.  If so,
> file a bug with [parallel make] as well as the package name in the
> subject line (assuming there's not yet one filed), and help get it fixed!
> =8^)
>
FWIW, I run MAKEOPTS="-j20 -l12" (up to 20 jobs, but don't start any more
> if the load is above 12) here.  Dual-dual-core Opteron 290s, 8 gig RAM,
> PORTAGE_TMPDIR pointing at a tmpfs so all those temp files don't hit
> disk.  With PORTAGE_NICENESS=19, and with kernel 2.6.24's new per-user
> scheduling turned on (and with Hz=300, voluntary preemption, so it's not
> a special real-time kernel or anything by any stretch), I can still
> listen to streaming audio and even run a moderately sized visualization
> window (amarok with the scrolling voice-print analyzer going in its own
> window) without audio pause or undue jerkiness (there's a bit, but under
> a load of 3 per core and no real-time preemption, one might expect that)
> of the visualization.    If I'm feeling adventurous and don't have
> anything else critical going on, I'll occasionally try -j by itself, just
> to see how high I can run the load average. A 400-500 load average is
> doable with kernel compiles, for instance, and nicely entertaining! =8^)
> It still amazes me how well the system copes with even that, and it was
> even more amazing back with dual-single-cores (242s)!


yep, i'll try out  it someday. for the moment i'm planning a disk change,
mine has already 2 years and its overall health is starting to be heard when
writing or reading data from the disk. i've got an external bigger disk that
i'll partition with tmpfs for paludis and portage. the only thing that i
still don't know is:
1. can i put on more than one different tmpfs?!
2. if i put one tmpfs and symlink there what i do want to use on tmpfs is
better?!

-- 
dott. ing. beso

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

[gentoo-amd64] Re: unable to emerge anything

[Duncan]

Beso <givemesugarr@gmail.com> posted
d257c3560802060625o3261f5cfw4eec6d5718e3bad9@mail.gmail.com, excerpted
below, on  Wed, 06 Feb 2008 14:25:24 +0000:

> 2008/2/6, Duncan <1i5t5.duncan@cox.net>:
>>
>> -fomit-frame-pointer is the default for -O and above on amd64/x86_64 
> 
> i tend to always add it since i don't want to always look at what the
> arch would do later.

OK, makes sense.  I used to as well, but I've enough other stuff there 
now that if I can avoid duping defaults, I do! =8^)

> i tend to think that Os should be gentoo's default, since it adds some
> options for cache and disk occupation and since i've always been good
> with it.

Like I said, I used to use it, and agreed with you. I still do in 
principle, but with gcc-4.2, -O2 is enough improved it does what I want, 
now, without doing what I don't want, for the most part.  There's still a 
couple bits I change, but from 4.2, there'd be about as many I'd change 
for -Os as for -O2, and -O2 is certainly better tested, so that's what I 
decided to run for at least this version.  I'll have to see if that 
changes again when 4.3 comes out.

> -mmmx is included in the default for -march=k8
> 
> when i've added it it wasn't included by default.

Are you sure?  For amd64/x86_64, AFAIK, -mmmx has always been there as 
it's part of the architecture definitions.  (BTW I wonder if Via's new 64-
bit Isaiah changes things in this regard; IIRC they omitted part of the 
pentium spec for some 32-bit CPU some years ago now altho it wasn't Via 
at the time but someone they later purchased, but anyway, it threw 
compilers for a loop for awhile, but hopefully they learned from that.)

>> What about -mno-tls-direct-seg-refs?  Why do you use that?
> 
> this should help with virtualizazion apps. xen won't work well without
> it with large system memory. without xen or other virt apps this
> shouldn't influence much on the packages.

OK, that answers /that/ question.  My CPUs, being Opteron 290s, aren't of 
the virtualization instruction generation yet, and I've kind of avoided 
it for that reason.  Thus, the flag above isn't something I need to worry 
about.  Thanks!

>> > also add:
>> > LDFLAGS="-Wl,--as-needed,-O1 -Wl,--enable-new-dtags -Wl,--sort-common
>> > -s"
>>
>> Could you point me to documentation on LDFLAGS in general, or at least
>> --enable-new-dtags and --sort-common?  I use --as-needed already (
>> documentation at http://www.gentoo.org/proj/en/qa/asneeded.xml )

> --sort-common is to prevent gaps between symbols due to alignment
> constraints, presumably increasing efficiency layout. here's an
> interesting topic on ldflags:
> http://forums.gentoo.org/viewtopic-t-67777.html

Thanks!  Bookmarking for later reference (I'm about to go to sleep now 
and am too sleepy to make sense of much new stuff ATM).

> --enable-new-dtags should be default for current binutils but it  was
> there from my 3 years old make.conf so it is still there. adding it
> again shouldn't do harm.

Again, thanks.  Now that you mention it, I think I did see something to 
that effect elsewhere, but didn't worry about it since it was now the 
default.

> yep, i'll try out [-j, unlimited jobs] someday.
> for the moment i'm planning a disk
> change, mine has already 2 years and its overall health is starting to
> be heard when writing or reading data from the disk.

Ouch!  Unfortunately, my last couple disks didn't really get to that 
point.  The last one in particular got too hot after the A/C died on a 
summer day when I was out, here in Phoenix.  The room air temp could have 
gotten to well over 50 C, so who knows how hot the disk got!  Fortunately 
I had the disk partitioned decently and unmounted backup partitions of 
most stuff, which was generally retrievable.  I was even able to run the 
thing in operation for awhile after it cooled back down -- NOT using the 
partitions that the head had crashed on due to the heat, of course, but I 
replaced it as soon as I could scrap the money together.

That's when I decided I needed RAID.  Two disks in a row going out after 
almost exactly a year each.  FWIW, I also ended up replacing the A/C, and 
I've not had a problem since, 2.5 years ago now.

> i've got an
> external bigger disk that i'll partition with tmpfs for paludis and
> portage. the only thing that i still don't know is:

> 1. can i put on more than one different tmpfs?!

Yes.  I'm actually running several, /dev (udev), max size 2 MB, /dev/shm 
(FHS but used only by portage for PORTAGE_TMPFS, not to be confused with 
PORTAGE_TMPDIR and PKG_TMPDIR), max 50 MB, /lib64/rcscripts/init.d (old 
entry, now inactive, old baselayout-1.x), max 512 KB, and my big one, /
tmp, 6 GB.  /var/tmp is actually a symlink to the 6 gig /tmp, and both 
PORTAGE_TMPDIR and PKG_TMPDIR point to /tmp.  (Note that ccache's dir is 
inside PORTAGE_TMPDIR by default according to make.conf.example.  You'll 
want to put it elsewhere, OUTSIDE the tmpfs, so it doesn't die at reboot, 
rather defeating the purpose.)

2. if i put one tmpfs and symlink there what i do want to use on tmpfs is 
better?!

I can't quite get that question to parse.  However... remember that while 
you can have multiple tmpfs mounted, if you might be using both at once, 
you need to consider the total effect on memory.  Thus, it's probably 
better to only have one big (multi-gig) one, and point other things at it 
if necessary.  I've used symlinks (as with /var/tmp above), but mount --
bind /should/ work as well, AFAIK.

While we're talking symlinks, this is for cache not tmp, but it may be 
worth mentioning that I have one filesystem containing all my system 
cache stuff on RAID-0, that is, CCACHE_DIR, PORTDIR (including layman's 
subdirs and DISTDIR but not PKGDIR), and /usr/src.  Those are 
traditionally in various separate locations, but here, I have them all as 
subdirs on the same RAID-0 backed filesystem for speed and because they 
don't need redundancy.  CCACHE_DIR and PORTDIR can of course be reset to 
point to the desired subdirs directly, but /usr/src is a symlink to the 
appropriate subdir on my RAID-0, which I have mounted as /str (for 
striped).  So /usr/src -> /str/usrsrc as a symlink.  I also symlink most 
of my frequently used dirs directly from root, too.  So /h -> /home 
(actually, the reverse, I mount my home filesystem on /h, and /home -> /
h), /usr/local -> /l, /var/log -> /log, /usr/portage -> /p -> /str/
portage, etc.  Saves a lot of typing that way, as I can refer to /l/bin/
script or /log/messages or /p/profiles/package.mask, for instance.

Symlinks are SO useful; I'm STILL trying to figure out how I survived a 
decade on MS without them!  (Actually, by W98 time, I was using a third 
party Explorer extension that allowed one to create custom system 
folders, much like My Computer is as shipped, but of course that was 
only /sort/ of like symlinks, I had yet to discover the power of the real 
thing! =8^)  Of course, since the advent of --bind and friends as options 
to mount, basically the same thing could be accomplished with it by mount 
--binding the subdirs as necessary, but I don't think MS does that 
either, and symlinks work, so that's what I've used.

-- 
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

-- 
gentoo-amd64@lists.gentoo.org mailing list

Re: [gentoo-amd64] Re: unable to emerge anything

[Beso]

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

2008/2/6, Duncan <1i5t5.duncan@cox.net>:
>
> Beso <givemesugarr@gmail.com> posted
> d257c3560802060625o3261f5cfw4eec6d5718e3bad9@mail.gmail.com, excerpted
> below, on  Wed, 06 Feb 2008 14:25:24 +0000:
> >> What about -mno-tls-direct-seg-refs?  Why do you use that?
> >
> > this should help with virtualizazion apps. xen won't work well without
> > it with large system memory. without xen or other virt apps this
> > shouldn't influence much on the packages.
>
> OK, that answers /that/ question.  My CPUs, being Opteron 290s, aren't of
> the virtualization instruction generation yet, and I've kind of avoided
> it for that reason.  Thus, the flag above isn't something I need to worry
> about.  Thanks!


on processors with virt instruction it should be mandatory and on system
without them this option would speed-up the virtualization to about 50%. in
fact the xen ebuild also says this.

> yep, i'll try out [-j, unlimited jobs] someday.
> > for the moment i'm planning a disk
> > change, mine has already 2 years and its overall health is starting to
> > be heard when writing or reading data from the disk.
>
> Ouch!  Unfortunately, my last couple disks didn't really get to that
> point.  The last one in particular got too hot after the A/C died on a
> summer day when I was out, here in Phoenix.  The room air temp could have
> gotten to well over 50 C, so who knows how hot the disk got!  Fortunately
> I had the disk partitioned decently and unmounted backup partitions of
> most stuff, which was generally retrievable.  I was even able to run the
> thing in operation for awhile after it cooled back down -- NOT using the
> partitions that the head had crashed on due to the heat, of course, but I
> replaced it as soon as I could scrap the money together.


i won't use raid, since i'm on notebook. so raid doesn't has a reason to be
since it won't work. lvm2 instead would be installed. also it seems that my
notebook is able to boot external disks and for that reason i might put a
root copy on the external disk.

> i've got an
> > external bigger disk that i'll partition with tmpfs for paludis and
> > portage. the only thing that i still don't know is:
>
> > 1. can i put on more than one different tmpfs?!
>
> Yes.  I'm actually running several, /dev (udev), max size 2 MB, /dev/shm
> (FHS but used only by portage for PORTAGE_TMPFS, not to be confused with
> PORTAGE_TMPDIR and PKG_TMPDIR), max 50 MB, /lib64/rcscripts/init.d (old
> entry, now inactive, old baselayout-1.x), max 512 KB, and my big one, /
> tmp, 6 GB.  /var/tmp is actually a symlink to the 6 gig /tmp, and both
> PORTAGE_TMPDIR and PKG_TMPDIR point to /tmp.  (Note that ccache's dir is
> inside PORTAGE_TMPDIR by default according to make.conf.example.  You'll
> want to put it elsewhere, OUTSIDE the tmpfs, so it doesn't die at reboot,
> rather defeating the purpose.)


this is interesting.

2. if i put one tmpfs and symlink there what i do want to use on tmpfs is
> better?!
>
> I can't quite get that question to parse.  However... remember that while
> you can have multiple tmpfs mounted, if you might be using both at once,
> you need to consider the total effect on memory.  Thus, it's probably
> better to only have one big (multi-gig) one, and point other things at it
> if necessary.  I've used symlinks (as with /var/tmp above), but mount --
> bind /should/ work as well, AFAIK.
>
> While we're talking symlinks, this is for cache not tmp, but it may be
> worth mentioning that I have one filesystem containing all my system
> cache stuff on RAID-0, that is, CCACHE_DIR, PORTDIR (including layman's
> subdirs and DISTDIR but not PKGDIR), and /usr/src.  Those are
> traditionally in various separate locations, but here, I have them all as
> subdirs on the same RAID-0 backed filesystem for speed and because they
> don't need redundancy.  CCACHE_DIR and PORTDIR can of course be reset to
> point to the desired subdirs directly, but /usr/src is a symlink to the
> appropriate subdir on my RAID-0, which I have mounted as /str (for
> striped).  So /usr/src -> /str/usrsrc as a symlink.  I also symlink most
> of my frequently used dirs directly from root, too.  So /h -> /home
> (actually, the reverse, I mount my home filesystem on /h, and /home -> /
> h), /usr/local -> /l, /var/log -> /log, /usr/portage -> /p -> /str/
> portage, etc.  Saves a lot of typing that way, as I can refer to /l/bin/
> script or /log/messages or /p/profiles/package.mask, for instance.
>
> Symlinks are SO useful; I'm STILL trying to figure out how I survived a
> decade on MS without them!  (Actually, by W98 time, I was using a third
> party Explorer extension that allowed one to create custom system
> folders, much like My Computer is as shipped, but of course that was
> only /sort/ of like symlinks, I had yet to discover the power of the real
> thing! =8^)  Of course, since the advent of --bind and friends as options
> to mount, basically the same thing could be accomplished with it by mount
> --binding the subdirs as necessary, but I don't think MS does that
> either, and symlinks work, so that's what I've used.


yep you're quite right on synlinks. it seems that vista has something
similar.


-- 
dott. ing. beso

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