| View previous topic :: View next topic |
| Author |
Message |
knarf
Guru
Joined: 20 Feb 2003
Posts: 338
Location: Geneva, Switzerland
|
 Posted: Tue Jan 20, 2004 8:30 pm Post subject: [POSTFIX] Emerge fails |
 |
|
Bonsoir,
En emergant, ce soir, postfix j'ai eu un joli _fails_ pendant celui-ci.
Le message d'erreur :
| Code: | gcc -DHAS_PCRE -DHAS_MYSQL -I/usr/include/mysql -DUSE_SSL -DUSE_SASL_AUTH
clude/sasl -DDEF_CONFIG_DIR=\"/etc/postfix\" -DDEF_DAEMON_DIR=\"/usr/lib/p
-DDEF_PROGRAM_DIR=\"/usr/lib/postfix\" -DDEF_MANPAGE_DIR=\"/usr/share/man\
EADME_DIR=\"/usr/share/doc/postfix-2.0.16-r1/readme\" -DDEF_SAMPLE_DIR=\"/
/doc/postfix-2.0.16-r1/sample\" -g -mcpu=i686 -O3 -pipe -I. -DLINUX2 -c fi
c
gcc -DHAS_PCRE -DHAS_MYSQL -I/usr/include/mysql -DUSE_SSL -DUSE_SASL_AUTH
clude/sasl -DDEF_CONFIG_DIR=\"/etc/postfix\" -DDEF_DAEMON_DIR=\"/usr/lib/p
-DDEF_PROGRAM_DIR=\"/usr/lib/postfix\" -DDEF_MANPAGE_DIR=\"/usr/share/man\
EADME_DIR=\"/usr/share/doc/postfix-2.0.16-r1/readme\" -DDEF_SAMPLE_DIR=\"/
/doc/postfix-2.0.16-r1/sample\" -g -mcpu=i686 -O3 -pipe -I. -DLINUX2 -c fi
gcc: Internal error: Segmentation fault (program as)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions.
make: *** [fifo_trigger.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [update] Error 1
!!! ERROR: net-mail/postfix-2.0.16-r1 failed.
!!! Function src_compile, Line 138, Exitcode 2
!!! compile problem
|
Mon /proc/sys :
| Code: | tux root # cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 7
model name : Pentium III (Katmai)
stepping : 3
cpu MHz : 551.319
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse
bogomips : 1089.53
|
Mon make.conf
| Code: | # ========================
#
# The USE variable is used to enable optional build-time functionality. For
# example, quite a few packages have optional X, gtk or GNOME functionality
# that can only be enabled or disabled at compile-time. Gentoo Linux has a
# very extensive set of USE variables described in our USE variable HOWTO at
# http://www.gentoo.org/doc/use-howto.html
#
# The available list of use flags with descriptions is in your portage tree.
# Use 'less' to view them: --> less /usr/portage/profiles/use.desc <--
#
# Example
USE="-X -kde -qt -gnome -gtk mysql imap libwww maildir sasl ssl"
# 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="i486-pc-linux-gnu"
# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU
#
# -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-4,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron), pentium3,
# and pentium4. Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
#
# 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:
#
#CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CFLAGS="-mcpu=i686 -O3 -pipe"
# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings. If you don't set CFLAGS above, then comment this line out.
CXXFLAGS="${CFLAGS}"
# 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="~arch"
# 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"
#
# 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.
#
# 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}'
# 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".
#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.
#FEATURES="sandbox ccache buildpkg"
#
# 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="3"
|
Je vous poste toutes ces infos parce qu'en faite je suis pas sûr de mes cflags.
Je vous remercie |
|
| Back to top |
|
 |
TGL
Bodhisattva
Joined: 02 Jun 2002
Posts: 1978
Location: Rennes, France
|
| Posted: Tue Jan 20, 2004 9:24 pm Post subject: Re: [POSTFIX] Emerge fails |
|
|
| knarf wrote: | | Code: | gcc: Internal error: Segmentation fault (program as)
Please submit a full bug report.
See <URL:http://bugs.gentoo.org/> for instructions.
make: *** [fifo_trigger.o] Error 1
make: *** Waiting for unfinished jobs....
make: *** [update] Error 1 |
|
Est-ce que si tu rééssaies il te refait l'erreur exactement au même endroit ? Parceque si oui, on peut probablement trouver une solution, sinon, c'est plus probablement matériel (mémoire défectueuse ou proc pas assez ventilé, ce genre de chose).
| knarf wrote: | Mon make.conf | Code: | <snip>
CHOST="i486-pc-linux-gnu"
<snip>
CFLAGS="-mcpu=i686 -O3 -pipe" |
|
Ça c'est un peu incohérent. Je ne sais pas si ça peut avoir de mauvais effet, mais vu ton processeur, j'aurais mis CHOST=i686-pc-linux-gnu. Ça me semblerait raisonnable de réémerger le system ("emerge -p -e system") avec ça corrigé. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
French
