Since I hadn't made much progress on the problem, I started over and it worked 
like a champ.  Moral of the story: don't let your friend start an 
installation that you have to finish....

Thanx all,

Mike.

On Friday 18 January 2008 08:28:42 pm Mike Diehl wrote:
> Hi all,
>
> I'm building a new machine and I'm having trouble getting apache to emerge.
>
> This is a BRAND NEW BOX, with nothing else done to it, so I expected apache
> to load just fine.
>
> Here is the error message I'm getting.  Any help would be appreciated.
> Mike.
>
> ---------------------------------------------------------------------------
>----------------------------
>
> g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtbeginS.o: No such file or
> directory
> g++: /usr/lib/gcc/i486-pc-linux-gnu/4.1.1/crtendS.o: No such file or
> directory make[1]: *** [libapr-1.la] Error 1
> make[1]: Leaving directory
> `/var/tmp/portage/dev-libs/apr-1.2.11/work/apr-1.2.11'
> make: *** [all-recursive] Error 1
>  *
>  * ERROR: dev-libs/apr-1.2.11 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
>  *   apr-1.2.11.ebuild, line   68:  Called die
>  * The specific snippet of code:
>  *      emake || die "Make failed"
>  *  The die message:
>  *   Make 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/dev-libs/apr-1.2.11/temp/build.log'.
>  *
>
>  * Messages for package dev-libs/apr-1.2.11:
>
>  *
>  * ERROR: dev-libs/apr-1.2.11 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
>  *   apr-1.2.11.ebuild, line   68:  Called die
>  * The specific snippet of code:
>  *      emake || die "Make failed"
>  *  The die message:
>  *   Make 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/dev-libs/apr-1.2.11/temp/build.log'.
>
> --
> Mike Diehl



-- 
Mike Diehl
-- 
[email protected] mailing list

Reply via email to