Cannot install/compile KDE.

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Does anyone know what this means and how to fix it?

brain · Posted: Thu Jun 19, 2003 12:20 pm Post subject:

Is there any reason you need MySQL to install KDE? you could always add

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Thanks man that worked like a dream...

Thanks very much!

Q

paranode · l33t Joined: 06 Mar 2003 Posts: 679 Location: Texas

Or take off the static USE flag if you have it set. I'm guessing this might be the issue with that and other packages.
_________________
Meh.

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Where would I do that? I looked at the that file again, maybe i'm blind or something (no suprise maybe after going at this so long) but I didn't spot it. This could be an issue with other things I try to build, so I'd like to avoid it.

Q

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Ok I'm going to have to try to exclude MySQL support for now. I opted to include it without SSL support and here's what happend.

brain · Posted: Thu Jun 19, 2003 1:18 pm Post subject:

Weird...

Can you post your make.conf file?
_________________
--brain

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Ok, but don't laugh at me for enabling so much, this is only my second attempt and about 3 months or so into using Linux. This is intened to be a general purpose machine mainly focused on the web and home entertainment. I thought if I enabled most stuff now I would be less likely to run into problems in the future.

# Host Setting
# ============
#
# If you are using a Pentium Pro or greater processor, leave this line as-is;
# otherwise, change to i586, i486 or i386 as appropriate. All modern systems
# (even Athlons) should use "i686-pc-linux-gnu"
#
#CHOST="i686-pc-linux-gnu"

# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without
# breaking compatibility with other CPUs.
#
# -march=<cpu-type> means to take full advantage of the ABI and instructions
# for the particular CPU; this will break compatibility with older CPUs (for
# example, -march=athlon-xp code will not run on a regular Athlon, and
# -march=i686 code will not run on a Pentium Classic.
#
# CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron), pentium3.
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
# ATHLON-4 will generate invalid SSE instructions; use 'athlon' instead.
# PENTIUM4 will generate invalid instructions; use 'pentium3' instead.
#
# CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
# (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
#
# Decent examples:
USE="3dnow aalib acl -ssl -mysql acpi alsa arts avi berkdb bonobo canna cdr cups
curl dga directfb dvb dvd emacs encode esd ethereal evo fbcon firebird flash freetds freewnn gb gd gdbm gif gnome gphoto2 gpm gtk gtk2 gtkhtml guile icc icc-pgo imap imlib innodb informix ipv6 jack java jikes jpeg kde kerberos krb4 ladcca lcms ldap leim libg++ libgda libwww lirc maildir matrox mbox mcal mikmod memlimit mmx motif mozilla mpeg mpi mule mysql nas ncurses nhc98 nls oav oci8 odbc oggvorbis opengl oss pam pda pdflib perl plotutils png pnp postgres prebuilt python qt quicktime readline ruby samba sasl scanner sdl slang slp snmp socks5 spell static svga tcltk tcpd tetex tiff truetype trusted usb voodoo3 wavelan wmf X Xaw3d xface xinerama xml xml2 xmms xv zeo zlib"

CFLAGS="-march=athlon-xp -m3dnow -msse -mfpmath=sse -mmmx -O3 -pipe -fforce-addr -fomit-frame-pointer -funroll-loops -frerun-cse-after-loop -frerun-loop-opt -falign-functions=4 -maccumulate-outgoing-args -ffast-math -fprefetch-loop-arrays"

CHOST="i686-pc-linux-gnu"

# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc', '~sparc64' are the unstable KEYWORDS for their respective
# platforms. DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
ACCEPT_KEYWORDS="~x86"

# Portage Directories
# ===================
#
# Each of these settings controls an aspect of portage's storage and file
# system usage. If you change any of these, be sure it is available when
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
# temporary storage of data. This can get VERY large depending upon
# the application being installed.
#PORTAGE_TMPDIR=/var/tmp
#
# PORTDIR is the location of the portage tree. This is the repository
# for all profile information as well as all ebuilds. This directory
# itself can reach 200M. WE DO NOT RECOMMEND that you change this.
#PORTDIR=/usr/portage
#
# DISTDIR is where all of the source code tarballs will be placed for
# emerges. The source code is maintained here unless you delete
# it. The entire repository of tarballs for gentoo is 9G. This is
# considerably more than any user will ever download. 2-3G is
# a large DISTDIR.
#DISTDIR=${PORTDIR}/distfiles
#
# PKGDIR is the location of binary packages that you can have created
# with '--buildpkg' or '-b' while emerging a package. This can get
# upto several hundred megs, or even a few gigs.
#PKGDIR=${PORTDIR}/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as YYMMDD-$PF.log
# in the directory specified. This is disabled until you enable it by
# providing a directory. Permissions will be modified as needed IF the
# directory exists, otherwise logging will be disabled.
#PORT_LOGDIR=/var/log/portage
#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
# concern that they will be deleted by rsync updates. Default is not
# defined.
#PORTDIR_OVERLAY=/usr/local/portage

# Fetching files
# ==============
#
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
# all users on your system should use them.
#
# Portage uses wget by default. Here are some settings for some alternate
# downloaders -- note that you need to merge these programs first before they
# will be available.
#
# Default fetch command (5 tries, passive ftp for firewall compatibility)
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#
# Using wget, ratelimiting downloads
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
#
# Prozilla (turbo downloader)
#FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space seperated list which is read left to right. If you use
# another mirror we highly recommend leaving the default mirror at the end of
# the list so that portage will fall back to it if the files cannot be found
# on your specified mirror. We _HIGHLY_ recommend that you change this setting
# to a nearby mirror by merging and using the 'mirrorselect' tool.
#GENTOO_MIRRORS="<your_mirror_here> http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo"

# Advanced Features
# =================
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
# program is compiled. Presently the only use is for specifying
# the number of parallel makes (-j) to perform. The suggested number
# for parallel makes is CPUs+1.
#MAKEOPTS="-j2"
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
# packages from the system after every successful merge. This is the
# same as running 'emerge -c' after every merge. Set with: "yes" or "no".
# This does not affect the unpacked source. See 'noclean' below.
AUTOCLEAN="yes"
#
# FEATURES are settings that affect the functionality of portage. Most of
# these settings are for developer use, but some are available to non-
# developers as well. 'buildpkg' is an always-on setting for the emerge
# flag of the same name. It causes binary packages to be created of all
# packages that are merged. 'distcc' enables distcc support for via CC.
# 'userpriv' allows portage to drop root privleges while it is compiling
# as a security measure, and as a side effect this can remove sandbox
# access violations for users. 'usersandbox' enables sandboxing while
# portage is running under userpriv. 'notitles' disables xterm titlebar
# updates (which contain status info). 'noclean' prevents portage from
# removing the source and temporary files after a merge -- for debugging
# purposes only. 'noauto' is a feature which causes ebuild to perform
# the action requested and not any other required actions like clean or
# unpack -- for debugging purposes only. 'cvs' is a feature for developers
# that causes portage to enable full settings and USE flags in SRC_URI and
# has wide effects -- don't set this unless you're ready for it. 'keeptemp'
# prevents the clean phase from deleting the temp files ($T) from a merge.
# 'keepwork' prevents the clean phase from deleting the $WORKDIR.
#FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork"
#
# CCACHE_SIZE sets the space use limitations for ccache. The default size is
# 2G, and will be set if not defined otherwise and ccache is in features.
# Portage will set the default ccache dir if it is not present in the
# user's environment: ${PORTAGE_TMPDIR}/ccache (/var/tmp/ccache).
# Sizes are specified with 'G' 'M' or 'K'.
# '4G' for 4 gigabytes, '4096M' for 4 gigabytes, etc... Default is 2G
#CCACHE_SIZE="2G"
#
# RSYNC_RETRIES sets the number of times portage will attempt to retrieve
# a current portage tree before it exits with an error. This allows
# for a more successful retrieval without user intervention most times.
RSYNC_RETRIES="5"
#
# RSYNC_TIMEOUT sets the length of time rsync will wait before it times out
# on a connection. Most users will benefit from this setting as it will
# reduce the amount of 'dead air' they experience when they run across
# the occasional, unreachable mirror. Dialup users might want to set this
# value up around the 300 second mark.
RSYNC_TIMEOUT=180
#
# RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
# the portage tree. Specific chucks of the tree may be excluded from
# consideration. This may cause dependency failures if you are not careful.
# The file format is one pattern per line, blanks and ';' or '#' lines are
# comments. See 'man rsync' for more details on the exclude-from format.
#RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes

So is there anything weirrd here or not? Again your opinion is welcome. I notice in the error its saying it it looking in the Xfree directory 9or something to that effect) I don't have X installed yet. Do you think this is significant?

Q

paranode · l33t Joined: 06 Mar 2003 Posts: 679 Location: Texas

brain · Posted: Thu Jun 19, 2003 2:06 pm Post subject:

Holy cow...

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Yeah man thanks. Maybe I did go a bit far, I don't know. But there is no advisory on how many flags you can use on the page that discusses them. I thought they were all optional, and after reading about them, most of them sounded pretty useful.

So ok as far as the USE flags are concerned, if I wanted a multi media, fast gaming /music dvd video entertainment centre, what would be your recommended choices? Also I couldn't find much official information about what were considered usable CFlags, so what I added came from a purely unofficial source. What you printed seems like a very conservative approach - but at the same time I'm concerned if I have gone too far and optimised things to death. In both cases I need advice on how to achive a good ballance between optimisation and good stability.

Also if I have come this far, to the final stages of installing KDE - and I find things aren't running too well, can I rebuild everything with new safer flags, or will I have to start from the bootstrapping process again?

Q

brain · Posted: Thu Jun 19, 2003 3:43 pm Post subject:

paranode · l33t Joined: 06 Mar 2003 Posts: 679 Location: Texas

brain · Posted: Thu Jun 19, 2003 3:44 pm Post subject:

brain · Posted: Thu Jun 19, 2003 3:44 pm Post subject:

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Can you print the link again? It seems to have messed up?

Ok,

Thanks you fixed it.

brain · Posted: Thu Jun 19, 2003 3:59 pm Post subject:

Yea, just saw that... looks like phpBB puked for a moment, it posted my message twice! The second one has the right link.
_________________
--brain

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Well everything seems to be going fairly well by simly ommiting -ssl and -mysql, so rather than make any radical changes as this late stage I'll just go with what I have. So far the only problem I have had is with MySQL (which I also had problems with in Red Hat) so i guess ommiting it now will allow me to investigate further in the future, should the need arrise.

In any case your advice will certainly be useful for future reference!

Q

raid517 · l33t Joined: 06 Mar 2003 Posts: 946

Ahh rats... it seems like you were 100% right. It looks like I'm going to have to eat my words. The problem is now half way through building KDE (yep that's right I'm still only half way - the speed on the portage defualt Berkly db server sucks) I have now changed the flags to something much more conservative. Isn't that liable to cause problems? I mean swtiching comipler flags half way through can't be good, right? Does this mean I will have to unmerge KDE and start again from the begiinging? (Boy that would suck). How do I check that a program that's beein installed contains no errors? I'd like to be able to predict potential trouble spots before they happen.

And finally, those CFLags still look very conservative to me. I have a nice fast system, Athlon 2600+ CPU 512 MB Ram, 360 Gig HDD space. What flags can I use fairly safely, while getting good optimisation and good stability. What do you guys think would be a good ballance?

Q