Thanks Emerson for clarifying that.

I find Gentoo hard to find basic level info on, although their forum is great (I don't like their forum package though - hard to find your own threads, etc).

Your patience was greatly appreciated!!
How do I go about getting the qt/kde4 system instead of kde-3.5.8? Will using the desktop profile accomplish that, or do I have to specifically select the kde4 ebuild somehow?

Shingoshi

I'm back again with an unresolved sandbox issue. It seems this thing is adaptive to creating new problems. Maybe there's more intelligence in the bugs in sandbox, than the developers releasing it. Anyway, here's what I get now:

checking whether the C compiler works... configure: error: cannot run C compiled programs.
If you meant to cross compile, use `--host'.
See `config.log' for more details.

!!! Please attach the following file when filing a report to bugs.gentoo.org:
!!! /var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/work/build-x86-x86_64-pc-linux-gnu/config.log
*
* ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
* ebuild.sh, line 638: Called die
* The specific snippet of code:
* die "econf failed"
* The die message:
* econf failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.
*

* Messages for package sys-apps/sandbox-1.2.18.1-r2:

*
* ERROR: sys-apps/sandbox-1.2.18.1-r2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* sandbox-1.2.18.1-r2.ebuild, line 87: Called econf '--libdir=/usr/lib32' '--enable-multilib'
* ebuild.sh, line 638: Called die
* The specific snippet of code:
* die "econf failed"
* The die message:
* econf failed
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-apps/sandbox-1.2.18.1-r2/temp/build.log'.
*
* If configure fails with a 'cannot run C compiled programs' error, try this:
* FEATURES=-sandbox emerge sandbox
==================================================


And this was after entering the code as I was previously instructed. So I don't know what to say about this, except that it's a MESS!!

Considering how many programs seem to be dependent on the sandbox, it is questionable why it isn't given a level of priority that Gentoo's survival rests upon. Since if you can't emerge packages, what's the point in Gentoo?

Shingoshi

Notice the two critical programs dependent on sandbox:

starbase64 / # emerge glibc --pretend

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild N ] sys-apps/sandbox-1.2.18.1-r2
[ebuild U ] app-misc/ca-certificates-20070303-r1 [20061027.2]
[ebuild NS ] sys-devel/gcc-4.1.2 USE="bootstrap fortran gtk mudflap nls (-altivec) -build -d -doc -gcj (-hardened) -ip28 -ip32r10k (-multilib) -multislot (-n32) (-n64) -nocxx -objc -objc++ -objc-gc -test -vanilla"
[ebuild U ] sys-libs/glibc-2.6.1 [2.3.6-r5] USE="-debug% -gd% (-hardened*) -vanilla%"

http://www.gentoo.org/proj/en/desktop/kde/kde4.xml

I hear it is not ready for production use yet.

Unfortunately I do not have a 64 bit system myself, no experience with multilib.

You may try and disable LDFLAGS if you have set them, also remove anything exotic from CFLAGS. Please post your emerge --info, too.

Portage 2.1.3.19 (default-linux/amd64/2007.0/desktop, gcc-3.4.6, glibc-2.3.6-r5, 2.6.23.1-smp x86_64)
=================================================================
System uname: 2.6.23.1-smp x86_64 Dual-Core AMD Opteron(tm) Processor 2210
Timestamp of tree: Tue, 12 Feb 2008 08:00:01 +0000
app-shells/bash: 3.2_p17-r1
dev-lang/python: 2.4.3-r4, 2.5.1-r5
dev-python/pycrypto: 2.0.1-r6
sys-apps/baselayout: 1.12.9
sys-devel/autoconf: 2.13, 2.61-r1
sys-devel/automake: 1.5, 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="-O2 -pipe -fforce-addr"
CHOST="x86_64-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/share/X11/xkb"
CONFIG_PROTECT_MASK="/etc/env.d /etc/fonts/fonts.conf /etc/gconf /etc/revdep-rebuild /etc/terminfo /etc/udev/rules.d"
CXXFLAGS="-O2 -pipe -fforce-addr"
DISTDIR="/usr/portage/distfiles"
EMERGE_DEFAULT_OPTS="--with-bdeps=y --buildpkg --deep"
FEATURES="distlocks metadata-transfer sfperms strict unmerge-orphans userfetch"
GENTOO_MIRRORS="http://gentoo.llarian.net/"
LANG="en_US"
PKGDIR="/usr/portage/packages"
PORTAGE_COMPRESS="lzma"
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"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X acl acpi alsa amd64 arts berkdb bitmap-fonts bootstrap cairo cdr cli cracklib crypt cups dbus dri dvd dvdr dvdread eds emboss encode esd evo fam firefox fortran gdbm gif gnome gpm gstreamer gtk hal iconv ipv6 isdnlog jpeg kde kerberos ldap libgcj libssp mad midi mikmod mmx mp3 mpeg mudflap ncurses nls nptl nptlonly ogg opengl openmp oss pam pcre pdf perl png pppd python qt3 qt3support qt4 quicktime readline reflection sdl session slang spell spl sse sse2 ssl svg tcpd tiff truetype truetype-fonts type1-fonts unicode vorbis xml xorg xv zlib" ALSA_CARDS="ali5451 als4000 atiixp atiixp-modem bt87x ca0106 cmipci emu10k1x ens1370 ens1371 es1938 es1968 fm801 hda-intel intel8x0 intel8x0m maestro3 trident usb-audio via82xx via82xx-modem ymfpci" 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 evdev" KERNEL="linux" LCD_DEVICES="bayrad cfontz cfontz633 glk hd44780 lb216 lcdm001 mtxorb ncurses text" USERLAND="GNU" VIDEO_CARDS="apm ark chips cirrus cyrix dummy fbdev glint i128 i810 mach64 mga neomagic nv r128 radeon rendition s3 s3virge savage siliconmotion sis sisusb tdfx tga trident tseng v4l vesa vga via vmware voodoo"
Unset: CPPFLAGS, CTARGET, INSTALL_MASK, LC_ALL, LDFLAGS, LINGUAS, MAKEOPTS, PORTAGE_COMPRESS_FLAGS, PORTAGE_RSYNC_EXTRA_OPTS, PORTDIR_OVERLAY

I will get the rest.
Shingoshi

http://gentoo-wiki.com/Safe_Cflags#2...eron_.28AMD.29

It seems -fforce-addr is not among safe flags, also you miss -march flag.
I'd say fix it and try again.

Changed settings as advised, no difference!

Shingoshi

I write notes for my systems so I know where things may be wrong and have pretty good ideas how to fix.
Unfortunately I have no clues for your box. All I know you changed profile from hardened to regular. Hardened profile is throughly tested, due to this program versions are older. I suspect your problems come from the fact you have a mixed system right now. I'm not saying it will cure everything, but here's what I'd do: emerge binutils, gcc, glibc, libtool; in this order. After that, emerge -e system. And I'd put that sandbox back to features.

If you go this route I'd recommend to emerge ufed (USE flag editor) and remove everything you do not need beforehand. For instance, are you really using ALSA, aRts, ESD and OSS? Do you really need pppd? Etc.
Also set VIDEO_CARDS variable, then Gentoo won't build all those video drivers, same for ALSA_CARDS.

Here's what I get. It seems for some reason the system is still trying to cross-compile some things. Maybe?


make: *** [profiledbootstrap] Error 2
*
* ERROR: sys-devel/gcc-4.1.2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1383: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1548: Called gcc_do_make
* toolchain.eclass, line 1422: Called die
* The specific snippet of code:
* emake \
* LDFLAGS="${LDFLAGS}" \
* STAGE1_CFLAGS="${STAGE1_CFLAGS}" \
* LIBPATH="${LIBPATH}" \
* BOOT_CFLAGS="${BOOT_CFLAGS}" \
* ${GCC_MAKE_TARGET} \
* || die "emake failed with ${GCC_MAKE_TARGET}"
* The die message:
* emake failed with profiledbootstrap
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'.
*

* Messages for package sys-devel/gcc-4.1.2:

*
* ERROR: sys-devel/gcc-4.1.2 failed.
* Call stack:
* ebuild.sh, line 1701: Called dyn_compile
* ebuild.sh, line 1039: Called qa_call 'src_compile'
* ebuild.sh, line 44: Called src_compile
* ebuild.sh, line 1383: Called toolchain_src_compile
* toolchain.eclass, line 26: Called gcc_src_compile
* toolchain.eclass, line 1548: Called gcc_do_make
* toolchain.eclass, line 1422: Called die
* The specific snippet of code:
* emake \
* LDFLAGS="${LDFLAGS}" \
* STAGE1_CFLAGS="${STAGE1_CFLAGS}" \
* LIBPATH="${LIBPATH}" \
* BOOT_CFLAGS="${BOOT_CFLAGS}" \
* ${GCC_MAKE_TARGET} \
* || die "emake failed with ${GCC_MAKE_TARGET}"
* The die message:
* emake failed with profiledbootstrap
*
* If you need support, post the topmost build error, and the call stack if relevant.
* A complete build log is located at '/var/tmp/portage/sys-devel/gcc-4.1.2/temp/build.log'.
*
* Regenerating GNU info directory index...
* Processed 201 info files.
* IMPORTANT: 18 config files in '/etc' need updating.
* See the CONFIGURATION FILES section of the emerge
* man page to learn how to update config files.
starbase64 / #

I thought I was running stage3. So what's the issue above about STAGE1? And the profiledbootstrap, isn't that also related to a cross-compile?

Ok. So here's a silly question. Can I reinstall Stage3 just to make sure I don't have a confused stage issue?

Shingoshi

You can probably do that. I noticed you have:

IMPORTANT: 18 config files in '/etc' need updating. You haven't run dispatch-conf (or etc-update)? This is a good recipe for trouble.

I like being able to SEE what it is that I'm doing. I'm not comfortable with the CL for something like this. If I had the experience to manage these files, I wouldn't need the programs. Besides, guis often provide a help system along with the binary. I'd like to have something to explain to me what I'm doing BEFORE I do it. So, if you know of a curses based tool for doing this, I'd really like to know which one to use. Everything that I've looked at, requires many other packages to be installed first. I don't want to make things worse, by installing more software than I actually need to resolve this.

Shingoshi

Shingoshi

There is no GUI nor curses based tool for this. Actually, dispatch-conf is a great tool, it's screen is easy to read, functions are flexible and it saves backups. Etc-update works well, too.
Despite Gentoo has a (controversial) GUI installer now it is a manual distribution by definition. More precisely, Gentoo is not a distro, it is a framework to build your own Linux.
GUI vs CLI? This argument won't lead anywhere. Do an ls -l /etc. You'll see a bunch of small, less than 10 kB files. CLI user can use a 10 kB big editor to edit all of them, no option is hidden, all error messages are displayed. A GUI user has to load tens of MB software to run a speialized editor to edit just one of those files. He will rely on author of that GUI tool, not every option is displayed, error messages suppressed, if the configuration file it is supposed to handle is updated then it often simply borks it. And what if there is no GUI? Or something is broken and GUI won't start? Help files? What if the help file is needed just once? And next 50 years you won't need it? Doesn't it qualify as cruft? Besides, there are man pages, Google, forums like this one for newcomers. Do you insist the whole POSIX world should be oriented to rookies?
There are hundreds of Linuxes out there, why did you pick a manual one if you don't want a manual one?

I decided to restart with a completely clean Gentoo root. I am documenting my steps as I go along, so as to have a script to automatically repeat this entire process.

So far, I have run in this order:
emerge -sync
emerge portage
emerge binutils
emerge gcc

Now here is where the instructions given here diverge from reality. emerging gcc gives you 37 total packages which must be installed. gcc cannot be built on it's own, separate from anything else. If there is a way to do that, it wasn't explained here. So just be aware, emerging gcc amounts to more than just a single build of one binary. It requires a total of 37 sources to be built as well. I should also add that I set this in /etc/make.conf:
EMERGE_DEFAULT_OPTS="--with-bdeps=y --buildpkg --deep"
So this may have influenced the build process, by adding more packages than would have
otherwise been emerged.

Be aware however, this is with a new installation. The instructions may have been valid if performed on a system that was already in place and running. However, I chose to start with a CLEAN system, and run the instructions given above, to ensure that I have the most up-to-date configuration possible. In any case, I have not encountered any problems yet.

I finally completed the process as stated above, with the exception of "emerge -e system". At that point, I found that I had a conflict between util-linux and setarch. So I decided to upgrade setarch, thinking that having a newer version might eliminate the problem. I was able to update setarch just fine, but that didn't fix the problem. I still have a conflict between setarch and util-linux, where each is blocking the other.

So I would like to hear now how to continue from this point, so that I have a completed upgrade. I will check on the net with Google, to see if there are any solutions given to resolve this conflict.

Ok. The solution was found. setarch in now included in util-linux, and can be safely removed to continue with "emerge -e system", which is running now. 98 packages have to be emerged.
http://www.tummblr.com/linux/gentoo-...erge-ud-world/

Shingoshi