On Monday 13 November 2006 20:07, Neil Bothwick wrote:
> On Mon, 13 Nov 2006 19:26:44 +0200, Alan McKinnon wrote:
> > What's the compile doing? I see you don't have PORTAGE_ELOG* set so
> > you won't have full compile session logs in /var/log/portage but
> > you should be able to see on the screen
On Monday 13 November 2006 19:47, James Colby wrote:
> > Also, try unpacking the source somewhere and doing a manual
> > compile. Then at least you'll know if it's portage making the
> > difference or not.
> >
> > alan
> > --
>
> Alan, thanks for the suggestion. I tried this and the compile failed
On Monday 13 November 2006 19:35, James Colby wrote:
> > Interrupt it and post the last 100 lines or so of the output.
> >
> > -Richard
>
> My apologies, for the top posting. I interrupted the compile and
> below is some of the output from the emerge:
This is becoming a big post, but so be it. I
On Mon, 13 Nov 2006 19:26:44 +0200, Alan McKinnon wrote:
> What's the compile doing? I see you don't have PORTAGE_ELOG* set so you
> won't have full compile session logs in /var/log/portage but you should
> be able to see on the screen what's happening and make an intelligent
> summary.
It's P
Also, try unpacking the source somewhere and doing a manual compile.
Then at least you'll know if it's portage making the difference or not.
alan
--
Alan, thanks for the suggestion. I tried this and the compile failed
with an error related to the system time. I checked the system date
and it
Interrupt it and post the last 100 lines or so of the output.
-Richard
My apologies, for the top posting. I interrupted the compile and
below is some of the output from the emerge:
make[1]: Leaving directory
`/var/tmp/portage/device-mapper-1.02.12/work/device-mapper.1.02.12/lib'
make[1]: En
On Monday 13 November 2006 19:05, James Colby wrote:
> I modified my make.conf file to: CFLAGS="-mtune=athlon -O2
> -fomit-frame-pointer"
>
> and the emerge has been running for about 1/2 hour and is still going
> (..and going, and going)
>
> Any other ideas???
Dunno. What version of device-mapper
On 11/13/06, James Colby <[EMAIL PROTECTED]> wrote:
I modified my make.conf file to: CFLAGS="-mtune=athlon -O2 -fomit-frame-pointer"
and the emerge has been running for about 1/2 hour and is still going
(..and going, and going)
Any other ideas???
Interrupt it and post the last 100 lines or so
I modified my make.conf file to: CFLAGS="-mtune=athlon -O2 -fomit-frame-pointer"
and the emerge has been running for about 1/2 hour and is still going
(..and going, and going)
Any other ideas???
The output of emerge --info is below:
gentoo portage # emerge --info
Portage 2.1-r2 (default-linux/x
On Monday 13 November 2006 17:31, James Colby wrote:
> All -
>
> I am trying to emerge sys-fs/device-mapper on an older piece of
> hardware (AMD Duron 800, with 512Mb of Ram). The package has been
> compiling for something like 8 hours already. Is this normal? It
> seems like an awfully long tim
Hi
I don't think it's normal.
Maybe there is a loop in compiling.
Please check, if it's still running, if there is some piece of code that repeats
continuously.
Post your emerge --info output
Lorenzo Marussi
Il giorno lun, 13/11/2006 alle 10.31 -0500, James Colby ha scritto:
All -
I
All -
I am trying to emerge sys-fs/device-mapper on an older piece of
hardware (AMD Duron 800, with 512Mb of Ram). The package has been
compiling for something like 8 hours already. Is this normal? It
seems like an awfully long time to me. As a comparison, I was able to
compile the kernel in
12 matches
Mail list logo
