Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Fiordland Stage 1 install Guide Ver. 3.0 (Deprecated)
View unanswered posts
View posts from last 24 hours

Goto page Previous  1, 2, 3  
Reply to topic    Gentoo Forums Forum Index Unsupported Software
View previous topic :: View next topic  
Author Message
cellularmitosis
Tux's lil' helper
Tux's lil' helper


Joined: 27 Dec 2003
Posts: 87

PostPosted: Thu Jun 26, 2008 8:27 pm    Post subject: Reply with quote

or perhaps i'll try the 2008 beta stages.
Back to top
View user's profile Send private message
warrens
Apprentice
Apprentice


Joined: 04 Jan 2005
Posts: 210
Location: Don't Tread On Me!

PostPosted: Thu Jun 26, 2008 10:53 pm    Post subject: Reply with quote

Now I know what the problem is. You missed this step:
Quote:
6 Set the correct make.profile link on X86.

The stage 1 tarbel comes with the make.profile link set to /usr/portage/profiles/default-linix/x86/no-nptl, so for those of us that have x86 machines that are x486 or greater need to change our make.profile link.

Code:
rm -f /etc/make.profile
ln -s /usr/portage/profiles/default-linux/x86/2007.0 /etc/make.profile
If your not using an x86 profile select the one that best fits your arch. With 32-bit systems the script works as writen, but for 64-bit systems you have to build glic before starting the script.
_________________
The BIGGER the GOVERNMENT, the smaller the citizen.

DON'T TREAD ON ME!!!

My Bias #1
The best government is the government that governs least.
Back to top
View user's profile Send private message
cellularmitosis
Tux's lil' helper
Tux's lil' helper


Joined: 27 Dec 2003
Posts: 87

PostPosted: Fri Jun 27, 2008 2:20 pm    Post subject: Reply with quote

yeah, after fiordland.sh failed the first time, I started over and was manually running all of the commands in the script one at a time, and sure enough, somehow I simply skipped that step.

I've set my make.profile to 2008.0 and things are progressing again. this is on an olpc, so its a pretty slow process! (~12 hours to build gcc...)
Back to top
View user's profile Send private message
cellularmitosis
Tux's lil' helper
Tux's lil' helper


Joined: 27 Dec 2003
Posts: 87

PostPosted: Fri Jun 27, 2008 2:20 pm    Post subject: Reply with quote

btw, thanks for writing fiordland :)
Back to top
View user's profile Send private message
g2g591
Tux's lil' helper
Tux's lil' helper


Joined: 17 Sep 2007
Posts: 103

PostPosted: Sun Jun 29, 2008 1:11 am    Post subject: Reply with quote

Somehow the script messed up changing my make.conf the first time and didn't stop at the EOF for some reason. after cut and pasting the remaining commands of the script into a new file, it ran fine. Nice guide overall.
Back to top
View user's profile Send private message
cellularmitosis
Tux's lil' helper
Tux's lil' helper


Joined: 27 Dec 2003
Posts: 87

PostPosted: Sun Jun 29, 2008 9:13 pm    Post subject: Reply with quote

ran into this one in the last emerge command:

Code:

/bin/sh ../libtool --tag=CC   --mode=link i586-pc-linux-gnu-gcc  -Os -march=geode -fomit-frame-pointer -pipe -D_GNU_SOURCE   -o file file.o libmagic.la -lz
i586-pc-linux-gnu-gcc -Os -march=geode -fomit-frame-pointer -pipe -D_GNU_SOURCE -o .libs/file file.o  ./.libs/libmagic.so -lz
creating file
make[2]: Leaving directory `/var/tmp/portage/sys-apps/file-4.24/work/file-4.24/src'
Making all in magic
make[2]: Entering directory `/var/tmp/portage/sys-apps/file-4.24/work/file-4.24/magic'
../src/file -C -m ../magic/Magdir
lt-file: No current entry for continuation
make[2]: *** [magic.mgc] Error 255
make[2]: Leaving directory `/var/tmp/portage/sys-apps/file-4.24/work/file-4.24/magic'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/var/tmp/portage/sys-apps/file-4.24/work/file-4.24'
make: *** [all] Error 2
 *
 * ERROR: sys-apps/file-4.24 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2913:  Called die
 * The specific snippet of code:
 *       emake || die "emake failed";
 *  The die message:
 *   emake 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/file-4.24/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/file-4.24/temp/environment'.
 *


again, I'm using gcc 4.3.1.
Back to top
View user's profile Send private message
cellularmitosis
Tux's lil' helper
Tux's lil' helper


Joined: 27 Dec 2003
Posts: 87

PostPosted: Sun Jun 29, 2008 9:16 pm    Post subject: Reply with quote

looks like there has been a bug filed against it:

https://bugs.gentoo.org/show_bug.cgi?id=215499
Back to top
View user's profile Send private message
warrens
Apprentice
Apprentice


Joined: 04 Jan 2005
Posts: 210
Location: Don't Tread On Me!

PostPosted: Tue Jul 08, 2008 7:03 am    Post subject: Reply with quote

Fiordland has been updated for use with release 2008.0.
_________________
The BIGGER the GOVERNMENT, the smaller the citizen.

DON'T TREAD ON ME!!!

My Bias #1
The best government is the government that governs least.
Back to top
View user's profile Send private message
cellularmitosis
Tux's lil' helper
Tux's lil' helper


Joined: 27 Dec 2003
Posts: 87

PostPosted: Sun Jul 20, 2008 7:36 pm    Post subject: Reply with quote

thanks again for fiordland :)

I found a possible bug/improvement.

executive summary: add '--nodeps' to the 'emerge --prune gcc' line.

details:

I am running into a bizarre problem where there are still references to gcc-4.1.2 in /etc/profile.env, even after running gcc-config, env-update, and sourcing /etc/profile. what's stranger is that both gcc's are in there, but the old one is first, so it gets used:

Code:

localhost / # env | grep gcc
MANPATH=/usr/local/share/man:/usr/share/man:/usr/share/binutils-data/i586-pc-linux-gnu/2.18/man:/usr/share/gcc-data/i486-pc-linux-gnu/4.1.2/man:/usr/share/gcc-data/i586-pc-linux-gnu/4.3.1/man
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i486-pc-linux-gnu/gcc-bin/4.1.2:/usr/i586-pc-linux-gnu/gcc-bin/4.3.1
INFOPATH=/usr/share/info:/usr/share/binutils-data/i586-pc-linux-gnu/2.18/info:/usr/share/gcc-data/i486-pc-linux-gnu/4.1.2/info:/usr/share/gcc-data/i586-pc-linux-gnu/4.3.1/info


I don't know how to fix that problem, but pruning the old gcc out of the way is at least a work-around. however, pruning gcc was failing (with a 0 exit code! ARGH!), because of a python dependency:

Code:

localhost / # gcc-config -l
 [1] i486-pc-linux-gnu-4.1.2
 [2] i586-pc-linux-gnu-4.3.1 *
localhost / # emerge --prune gcc

Calculating dependencies... done!

Dependencies could not be completely resolved due to
the following required packages not being installed:

>=dev-lang/python-2.5 required by sys-apps/portage-2.1.4.4

Have you forgotten to run `emerge --update --newuse --deep world` prior to
prune?  It may be necessary to manually uninstall packages that no longer
exist in the portage tree since it may not be possible to satisfy their
dependencies.  Also, be aware of the --with-bdeps option that is documented
in `man emerge`.

If you would like to ignore dependencies then use --nodeps.
 * GNU info directory index is up-to-date.
 * IMPORTANT: 1 config files in '/etc' need updating.
 * See the CONFIGURATION FILES section of the emerge
 * man page to learn how to update config files.
localhost / # echo $?
0


adding --nodeps works around that issue.
Back to top
View user's profile Send private message
heurist
n00b
n00b


Joined: 21 Jul 2008
Posts: 8

PostPosted: Mon Jul 21, 2008 1:34 pm    Post subject: suggestion for script robustness Reply with quote

Nice, informative guide and nice script; I use something very similar and have a suggestion from my script.

This takes the make.conf settings from the real make.conf so you do not need to edit the CHOST and such and it uses the preferred mirrors (HTTP and RSYNC) and log settings from the real file:
Code:
# Backup /etc/make.conf
OF="/etc/make.conf.build"
NF="/etc/make.conf"

# If /etc/make.conf.build exists do not overwrite it again.
if [ -e $OF ] ; then
   echo "ERROR: $OF already exists."
   echo "      previous install was probably interrupted."
   echo "      restore $NF and start again."
   exit 1
else
   cp -f $NF $OF
fi


if [ -e $OF ] ; then
   # Source(verb) settings from original make.conf
   . $OF
fi

# Create new /etc/make.conf with bootstrap specific settings:
# This will get most settings from your original make.conf
echo "##This is a copy of $NF for the bootstrap process" > $NF
echo "##Remember to restore you real $NF from $OF" >> $NF
# Use CHOST, CFLAGS, CXXFLAGS, MAKEOPTS and ACCEPT_KEYWORDS from original file.
echo "CHOST=\"$CHOST\"" >> $NF
echo "CFLAGS=\"$CFLAGS\"" >> $NF
echo "CXXFLAGS=\"$CXXFLAGS\"" >> $NF
echo "MAKEOPTS=\"$MAKEOPTS\"" >> $NF
echo "ACCEPT_KEYWORDS=\"$ACCEPT_KEYWORDS\"" >> $NF
# If FEATURES exists in orig use it else use these settings
if [ -n "$FEATURES" ] ; then
   echo "FEATURES=\"$FEATURES\"" >> $NF
else
   echo "FEATURES=\"distlocks sandbox userpriv usersandbox parallel-fetch userfetch\"" >> $NF
fi
# The Below lines are copied only if they exist in the original.
if [ -n "$PORTAGE_NICENESS" ] ; then
   echo "PORTAGE_NICENESS=\"$PORTAGE_NICENESS\"" >> $NF
fi
if [ -n "$PORT_LOGDIR" ] ; then
   echo "PORT_LOGDIR=\"$PORT_LOGDIR\"" >> $NF
fi
if [ -n" $PORTAGE_ELOG_CLASSES" ] ; then
   echo "PORTAGE_ELOG_CLASSES=\"$PORTAGE_ELOG_CLASSES\"" >> $NF
fi
if [ -n "$PORTAGE_ELOG_SYSTEM" ] ; then
   echo "PORTAGE_ELOG_SYSTEM=\"$PORTAGE_ELOG_SYSTEM\"" >> $NF
fi
if [ -n "$PKGDIR" ] ; then
   echo "PKGDIR=\"$PKGDIR\"" >> $NF
fi
if [ -n "$DISTDIR" ] ; then
   echo "DISTDIR=\"$DISTDIR\"" >> $NF
fi
if [ -n "$SYNC" ] ; then
   echo "SYNC=\"$SYNC\"" >> $NF
fi
if [ -n "$GENTOO_MIRRORS" ] ; then
   echo "GENTOO_MIRRORS=\"$GENTOO_MIRRORS\"" >> $NF
fi
# Override USE flags with bootstrap specific ones.
echo "USE=\"-* nptl nptlonly bootstrap\"" >> $NF
# Done making new make.conf

This replaces your
Code:
cat > /etc/make.conf << "EOF"...EOF

It looks like this would be a drop-in replacement but it should be tested as I have not run it in your script.
The second instance of the make.conf generation would obviously just remove the "bootstrap" USE flag but otherwise have the same codeblock again.

The last line of the script would now read
Code:
cp -f $OF $NF
instead of
Code:
cp -f /etc/make.conf.build /etc/make.conf


I would also set the timezone file in an environment variable
Code:
export TIMEZONE="/usr/share/zoneinfo/Africa/Johannesburg"
before running the script and then use
Code:
if [ -n "$TIMEZONE" ] ; then
   ln -s $TIMEZONE /etc/localtime
else
   ln -s /usr/share/zoneinfo/Zulu /etc/localtime
fi
so the timezone is correct without needing to edit the script.
Back to top
View user's profile Send private message
warrens
Apprentice
Apprentice


Joined: 04 Jan 2005
Posts: 210
Location: Don't Tread On Me!

PostPosted: Fri Dec 19, 2008 12:26 am    Post subject: Reply with quote

Made some updates due to upstream changes. MPFR now needs lzma-utils, and efs2progs-libs replaced ss and com_err.
_________________
The BIGGER the GOVERNMENT, the smaller the citizen.

DON'T TREAD ON ME!!!

My Bias #1
The best government is the government that governs least.
Back to top
View user's profile Send private message
Hose
n00b
n00b


Joined: 30 Dec 2004
Posts: 35

PostPosted: Sun Dec 28, 2008 7:30 pm    Post subject: Installation on Atom 330 Reply with quote

Hey all,

I've used this method before (2007.0) with no trouble at all. This time on a new (Intel Atom 330 board D945GCLF2) and using the 2008.0 Minimal CD (the guide calls for 2007.0, but I would think that is not the issue here), I'm running into this issue while emerging "sandbox-1.3.2":

sandbox-1.3.2 build.log:
Code:

>>> Unpacking source...
>>> Unpacking sandbox-1.3.2.tar.lzma to /var/tmp/portage/sys-apps/sandbox-1.3.2/work
/usr/lib64/portage/bin/ebuild.sh: line 417: lzma: command not found
tar: This does not look like a tar archive
tar: Error exit delayed from previous errors
 *
 * ERROR: sys-apps/sandbox-1.3.2 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_unpack
 *             environment, line 2458:  Called _eapi0_src_unpack
 *               ebuild.sh, line  588:  Called unpack 'sandbox-1.3.2.tar.lzma'
 *               ebuild.sh, line  418:  Called die
 * The specific snippet of code:
 *                  assert "$myfail"
 *  The die message:
 *   failure unpacking sandbox-1.3.2.tar.lzma
 *
 * 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.3.2/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/sys-apps/sandbox-1.3.2/temp/environment'.
 *
 * If configure failed with a 'cannot run C compiled programs' error, try this:
 * FEATURES=-sandbox emerge sandbox


Since it could not find the "lzma" executable, I decided to "emerge --oneshot --nodeps lzma-utils" and got this error:

lzma-utils-4.32 build.log
Code:

>>> Unpacking source...
>>> Unpacking lzma-4.32.7.tar.gz to /var/tmp/portage/app-arch/lzma-utils-4.32.7/work
>>> Source unpacked.
>>> Compiling source in /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7 ...
 * econf: updating lzma-4.32.7/config.sub with /usr/share/gnuconfig/config.sub
 * econf: updating lzma-4.32.7/config.guess with /usr/share/gnuconfig/config.guess
./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu
checking if debugging code should be compiled... no
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for x86_64-pc-linux-gnu-g++... no
checking for x86_64-pc-linux-gnu-c++... no
checking for x86_64-pc-linux-gnu-gpp... no
checking for x86_64-pc-linux-gnu-aCC... no
checking for x86_64-pc-linux-gnu-CC... no
checking for x86_64-pc-linux-gnu-cxx... no
checking for x86_64-pc-linux-gnu-cc++... no
checking for x86_64-pc-linux-gnu-cl.exe... no
checking for x86_64-pc-linux-gnu-FCC... no
checking for x86_64-pc-linux-gnu-KCC... no
checking for x86_64-pc-linux-gnu-RCC... no
checking for x86_64-pc-linux-gnu-xlC_r... no
checking for x86_64-pc-linux-gnu-xlC... no
checking for g++... no
checking for c++... no
checking for gpp... no
checking for aCC... no
checking for CC... no
checking for cxx... no
checking for cc++... no
checking for cl.exe... no
checking for FCC... no
checking for KCC... no
checking for RCC... no
checking for xlC_r... no
checking for xlC... no
checking for C++ compiler default output file name...
configure: error: C++ compiler cannot create executables
See `config.log' for more details.

!!! Please attach the following file when seeking support:
!!! /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/config.log
 *
 * ERROR: app-arch/lzma-utils-4.32.7 failed.
 * Call stack:
 *               ebuild.sh, line   49:  Called src_compile
 *             environment, line 2103:  Called _eapi0_src_compile
 *               ebuild.sh, line  593:  Called econf
 *               ebuild.sh, line  529:  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/app-arch/lzma-utils-4.32.7/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-arch/lzma-utils-4.32.7/temp/environment'.
 *

lzma-utils-4.32 config.log
Code:

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by LZMA configure 4.32.7, which was
generated by GNU Autoconf 2.62.  Invocation command line was

  $ ./configure --prefix=/usr --host=x86_64-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --libdir=/usr/lib64 --build=x86_64-pc-linux-gnu

## --------- ##
## Platform. ##
## --------- ##

hostname = livecd
uname -m = x86_64
uname -r = 2.6.24-gentoo-r7
uname -s = Linux
uname -v = #1 SMP Mon Aug 18 10:51:43 UTC 2008

/usr/bin/uname -p = Intel(R) Atom(TM) CPU 330 @ 1.60GHz
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo      = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: /usr/local/sbin
PATH: /sbin
PATH: /usr/sbin
PATH: /usr/lib64/portage/bin
PATH: /usr/local/bin
PATH: /bin
PATH: /usr/bin
PATH: /opt/bin
PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/4.1.2


## ----------- ##
## Core tests. ##
## ----------- ##

configure:2053: checking if debugging code should be compiled
configure:2073: result: no
configure:2127: checking for a BSD-compatible install
configure:2195: result: /usr/bin/install -c
configure:2206: checking whether build environment is sane
configure:2249: result: yes
configure:2274: checking for a thread-safe mkdir -p
configure:2313: result: /bin/mkdir -p
configure:2326: checking for gawk
configure:2342: found /bin/gawk
configure:2353: result: gawk
configure:2364: checking whether make sets $(MAKE)
configure:2386: result: yes
configure:2590: checking for x86_64-pc-linux-gnu-g++
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-c++
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-gpp
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-aCC
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-CC
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-cxx
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-cc++
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-cl.exe
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-FCC
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-KCC
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-RCC
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-xlC_r
configure:2620: result: no
configure:2590: checking for x86_64-pc-linux-gnu-xlC
configure:2620: result: no
configure:2634: checking for g++
configure:2664: result: no
configure:2634: checking for c++
configure:2664: result: no
configure:2634: checking for gpp
configure:2664: result: no
configure:2634: checking for aCC
configure:2664: result: no
configure:2634: checking for CC
configure:2664: result: no
configure:2634: checking for cxx
configure:2664: result: no
configure:2634: checking for cc++
configure:2664: result: no
configure:2634: checking for cl.exe
configure:2664: result: no
configure:2634: checking for FCC
configure:2664: result: no
configure:2634: checking for KCC
configure:2664: result: no
configure:2634: checking for RCC
configure:2664: result: no
configure:2634: checking for xlC_r
configure:2664: result: no
configure:2634: checking for xlC
configure:2664: result: no
configure:2692: checking for C++ compiler version
configure:2700: g++ --version >&5
./configure: line 2702: g++: command not found
configure:2704: $? = 127
configure:2711: g++ -v >&5
./configure: line 2713: g++: command not found
configure:2715: $? = 127
configure:2722: g++ -V >&5
./configure: line 2724: g++: command not found
configure:2726: $? = 127
configure:2749: checking for C++ compiler default output file name
configure:2771: g++ -march=nocona -O2 -fomit-frame-pointer -pipe  -Wl,-O1 conftest.cpp  >&5
./configure: line 2773: g++: command not found
configure:2775: $? = 127
configure:2813: result:
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "LZMA"
| #define PACKAGE_TARNAME "lzma"
| #define PACKAGE_VERSION "4.32.7"
| #define PACKAGE_STRING "LZMA 4.32.7"
| #define PACKAGE_BUGREPORT "lasse.collin@tukaani.org"
| #define NDEBUG 1
| #define PACKAGE "lzma"
| #define VERSION "4.32.7"
| /* end confdefs.h.  */
|
| int
| main ()
| {
|
|   ;
|   return 0;
| }
configure:2820: error: C++ compiler cannot create executables
See `config.log' for more details.

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_CCC_set=
ac_cv_env_CCC_value=
ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=set
ac_cv_env_CFLAGS_value='-march=nocona -O2 -fomit-frame-pointer -pipe'
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=set
ac_cv_env_CXXFLAGS_value='-march=nocona -O2 -fomit-frame-pointer -pipe'
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=set
ac_cv_env_LDFLAGS_value=-Wl,-O1
ac_cv_env_LIBS_set=
ac_cv_env_LIBS_value=
ac_cv_env_build_alias_set=set
ac_cv_env_build_alias_value=x86_64-pc-linux-gnu
ac_cv_env_host_alias_set=set
ac_cv_env_host_alias_value=x86_64-pc-linux-gnu
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/usr/bin/install -c'
ac_cv_path_mkdir=/bin/mkdir
ac_cv_prog_AWK=gawk
ac_cv_prog_make_make_set=yes

## ----------------- ##
## Output variables. ##
## ----------------- ##

ACLOCAL='${SHELL} /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/missing --run aclocal-1.10'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/missing --run tar'
AR=''
AUTOCONF='${SHELL} /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/missing --run autoconf'
AUTOHEADER='${SHELL} /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/missing --run autoheader'
AUTOMAKE='${SHELL} /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/missing --run automake-1.10'
AWK='gawk'
CC=''
CCDEPMODE=''
CFLAGS='-march=nocona -O2 -fomit-frame-pointer -pipe'
CPP=''
CPPFLAGS=''
CXX='g++'
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS='-march=nocona -O2 -fomit-frame-pointer -pipe'
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
DSYMUTIL=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77='no'
FFLAGS=''
GETOPT_H=''
GREP=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='$(install_sh) -c -s'
LDFLAGS='-Wl,-O1'
LIBOBJS=''
LIBS=''
LIBTOOL=''
LN_S=''
LTLIBOBJS=''
MAKEINFO='${SHELL} /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/missing --run makeinfo'
MKDIR_P='/bin/mkdir -p'
NMEDIT=''
OBJEXT=''
PACKAGE='lzma'
PACKAGE_BUGREPORT='lasse.collin@tukaani.org'
PACKAGE_NAME='LZMA'
PACKAGE_STRING='LZMA 4.32.7'
PACKAGE_TARNAME='lzma'
PACKAGE_VERSION='4.32.7'
PATH_SEPARATOR=':'
RANLIB=''
SDK_CFLAGS='-D_LZMA_IN_CB -D_LZMA_OUT_READ -D_LZMA_SYSTEM_SIZE_T -D_LZMA_PROB32'
SDK_CXXFLAGS='-DCOMPRESS_MF_BT -DCOMPRESS_MF_BT4 -DCOMPRESS_MF_HC'
SED=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
VERSION='4.32.7'
ac_ct_CC=''
ac_ct_CXX=''
ac_ct_F77=''
am__fastdepCC_FALSE=''
am__fastdepCC_TRUE=''
am__fastdepCXX_FALSE=''
am__fastdepCXX_TRUE=''
am__include=''
am__isrc=''
am__leading_dot='.'
am__quote=''
am__tar='${AMTAR} chof - "$$tardir"'
am__untar='${AMTAR} xf -'
bindir='${exec_prefix}/bin'
build='x86_64-pc-linux-gnu'
build_alias='x86_64-pc-linux-gnu'
build_cpu=''
build_os=''
build_vendor=''
datadir='/usr/share'
datarootdir='${prefix}/share'
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
dvidir='${docdir}'
exec_prefix='NONE'
host='x86_64-pc-linux-gnu'
host_alias='x86_64-pc-linux-gnu'
host_cpu=''
host_os=''
host_vendor=''
htmldir='${docdir}'
includedir='${prefix}/include'
infodir='/usr/share/info'
install_sh='$(SHELL) /var/tmp/portage/app-arch/lzma-utils-4.32.7/work/lzma-4.32.7/install-sh'
libdir='/usr/lib64'
libexecdir='${exec_prefix}/libexec'
localedir='${datarootdir}/locale'
localstatedir='/var/lib'
mandir='/usr/share/man'
mkdir_p='/bin/mkdir -p'
oldincludedir='/usr/include'
pdfdir='${docdir}'
prefix='/usr'
program_transform_name='s,x,x,'
psdir='${docdir}'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_NAME "LZMA"
#define PACKAGE_TARNAME "lzma"
#define PACKAGE_VERSION "4.32.7"
#define PACKAGE_STRING "LZMA 4.32.7"
#define PACKAGE_BUGREPORT "lasse.collin@tukaani.org"
#define NDEBUG 1
#define PACKAGE "lzma"
#define VERSION "4.32.7"

configure: exit 77


It would seem that I don't have a C++ compiler (g++).... ???

Any help would be appreciated. I'll append my make.conf in case that is the problem, since it is a fairly new board from Intel:

Code:

# Silo: Intel/Atop 330 1.60Ghz
#
CHOST="x86_64-pc-linux-gnu"
CFLAGS="-march=nocona -O2 -fomit-frame-pointer -pipe"
CXXFLAGS="${CFLAGS}"
MAKEOPTS="-j5"
ACCEPT_KEYWORDS="~amd64"
PORTAGE_NICENESS=3
LINGUAS="en_US"
AUTOCLEAN="yes"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="vesa"
ALSA_CARDS="intel8x0"
EMERGE_DEFAULT_OPTS="--verbose"
FEATURES="distlocks sandbox userpriv usersandbox"
CCACHE_SIZE=1024
#
USE="acpi apm db2 dbm ftp ipv6 java kerberos lm_sensors nptl nptlonly odbc soap ssl sockets syslog threads usb xinetd xml"
#
GENTOO_MIRRORS="http://gentoo.osuosl.org"
Back to top
View user's profile Send private message
heurist
n00b
n00b


Joined: 21 Jul 2008
Posts: 8

PostPosted: Mon Dec 29, 2008 3:42 am    Post subject: Reply with quote

As the updated first post says, you need to emerge lzma-utils with the USE="nocxx" flag.
Grab the newest script from this thread and it might help your situation.
Essentially you need to use the line:
Code:

USE="nocxx" emerge --oneshot --nodeps lzma-utils
Back to top
View user's profile Send private message
Hose
n00b
n00b


Joined: 30 Dec 2004
Posts: 35

PostPosted: Mon Dec 29, 2008 5:08 am    Post subject: lzma-utils Reply with quote

heurist,

Thanks for pointing out the missing USE="nocxx" in my statement. I am using the latest script from this thread, however I missed the part (and still can't find) about emerging lzma-utils prior to running the script.

None the less, it did emerge correctly and I restarted the script, which will probably run all night (I hope)

Thanks again
Back to top
View user's profile Send private message
heurist
n00b
n00b


Joined: 21 Jul 2008
Posts: 8

PostPosted: Mon Dec 29, 2008 5:34 am    Post subject: Reply with quote

Welcome.

Quote:
will probably run all night (I hope)

Yeah, Gentoo installs take a while.
This script is nice since it let's you leave it and come back to a working system, which is much better than needing to sit with it all night holding its hand.

Always remember that when you are running ~unstable there is a real possibility that an ebuild may fail and break the install, I like to add the --keep-going option to my emerges as that way it will do its best to finish while ignoring any failures.

I hope the script runs start to finish now, and that you have a working system when you get back to it.
Back to top
View user's profile Send private message
Hose
n00b
n00b


Joined: 30 Dec 2004
Posts: 35

PostPosted: Tue Dec 30, 2008 6:56 pm    Post subject: Minimal 2008 CD & Fiordland Reply with quote

Heurist,

As it tuned out, we had a storm at night and it knocked out my DSL, bye-bye install. I cleaned up the environment and re-ran the script last night, as I write this is still going strong. Looks like I'm going to make it to the end on this run...

Thanks for your tips and advice.....Happy New year (to all)
Back to top
View user's profile Send private message
warrens
Apprentice
Apprentice


Joined: 04 Jan 2005
Posts: 210
Location: Don't Tread On Me!

PostPosted: Fri Jul 24, 2009 1:38 pm    Post subject: Reply with quote

Made some updates to the script due to changes upstream. The 2008.0 stage1 tarbell is obsolete. You can use the weekly stage3 tarbells, get a stage1 tarbell from funtoo, or do as I did and make your own stage1 with catalyst or metro. I have not tested the stage1 tarbells from funtoo yet, so the script still shows the 2008.0 stage1, for now.

Good luck, and happy compiling. :D
_________________
The BIGGER the GOVERNMENT, the smaller the citizen.

DON'T TREAD ON ME!!!

My Bias #1
The best government is the government that governs least.
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Unsupported Software All times are GMT
Goto page Previous  1, 2, 3
Page 3 of 3

 
Jump to:  
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