[gentoo-amd64] emerge --emptytree problem

[gentoo-amd64] emerge --emptytree problem

[Mark]

I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
It keeps failing in the emerge --emptytree system process. I suspect
my make.conf is the problem. So a couple questions...

1. On the USE flags, this time around, I put in everything that
sounded like I wanted, which ended up being a very long list. Am I
better off having a very short list of USE flags, as shown in the
example in the docs?

2. I have -march=athlon64 in my make.conf file. My processor is an
AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
my whole problem rather than my USE flags list??

Thanks all,
-- 
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[Sean Sullivan]

On Sunday 10 July 2005 09:25, Mark wrote:
> I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
> It keeps failing in the emerge --emptytree system process. I suspect
> my make.conf is the problem. So a couple questions...
>
> 1. On the USE flags, this time around, I put in everything that
> sounded like I wanted, which ended up being a very long list. Am I
> better off having a very short list of USE flags, as shown in the
> example in the docs?
>
> 2. I have -march=athlon64 in my make.conf file. My processor is an
> AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
> my whole problem rather than my USE flags list??
>
> Thanks all,
> --
> Mark
> [unwieldy legal disclaimer would go here - feel free to type your own]

march=athlon64 should be fine for your CPU. I use it and have an AMD64 3000+. 
How exactly does the emerge fail? What is the error you see? Doubtful it has 
anything to do with your USE flags, so we'll prob need to see the error.

Here is my make.conf for comparison (and I have a lot of USE flags)
--------------------------
CHOST="x86_64-pc-linux-gnu"
CFLAGS="-march=athlon64 -O2 -pipe"
CXXFLAGS="${CFLAGS}"

ACCEPT_KEYWORDS="~amd64" 
MAKEOPTS="-j2"

 USE="-gnome -kde -gtk -arts acpi alsa X audiofile avi -bonobo
   cdparanoia cdr crypt cups dbm divx4linux dvd dvdread gtk2
   encode imagemagick mailwrapper mozilla mpeg mysqli multilib
   nvidia ogg oggvorbis oss opengl pam perl python qt samba ssl
   mysql php xine amd64 apache2 cups acl xml readline libclamav" 
--------------------------

-Sean
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[Mark]

I'll have to try again and see, I've already rebooted to start again.
When it fails (most recently it was at the qt-xxxx package install, it
has the usual "post the topmost error" message. But since I'm in the
console, I can't scroll up higher than the current screen displays.
How do I get to the error you would need to see? Thanks for the
help...

On 7/10/05, Sean Sullivan <sean@sfsullivan.org> wrote:
> On Sunday 10 July 2005 09:25, Mark wrote:
> > I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
> > It keeps failing in the emerge --emptytree system process. I suspect
> > my make.conf is the problem. So a couple questions...
> >
> > 1. On the USE flags, this time around, I put in everything that
> > sounded like I wanted, which ended up being a very long list. Am I
> > better off having a very short list of USE flags, as shown in the
> > example in the docs?
> >
> > 2. I have -march=athlon64 in my make.conf file. My processor is an
> > AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
> > my whole problem rather than my USE flags list??
> >
> > Thanks all,
> > --
> > Mark
> > [unwieldy legal disclaimer would go here - feel free to type your own]
> 
> march=athlon64 should be fine for your CPU. I use it and have an AMD64 3000+.
> How exactly does the emerge fail? What is the error you see? Doubtful it has
> anything to do with your USE flags, so we'll prob need to see the error.
> 
> Here is my make.conf for comparison (and I have a lot of USE flags)
> --------------------------
> CHOST="x86_64-pc-linux-gnu"
> CFLAGS="-march=athlon64 -O2 -pipe"
> CXXFLAGS="${CFLAGS}"
> 
> ACCEPT_KEYWORDS="~amd64"
> MAKEOPTS="-j2"
> 
>  USE="-gnome -kde -gtk -arts acpi alsa X audiofile avi -bonobo
>    cdparanoia cdr crypt cups dbm divx4linux dvd dvdread gtk2
>    encode imagemagick mailwrapper mozilla mpeg mysqli multilib
>    nvidia ogg oggvorbis oss opengl pam perl python qt samba ssl
>    mysql php xine amd64 apache2 cups acl xml readline libclamav"
> --------------------------
> 
> -Sean
> 


-- 
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[Zac Medico]

Mark wrote:
> I'll have to try again and see, I've already rebooted to start again.
> When it fails (most recently it was at the qt-xxxx package install, it
> has the usual "post the topmost error" message. But since I'm in the
> console, I can't scroll up higher than the current screen displays.
> How do I get to the error you would need to see? Thanks for the
> help...
> 

If you emerge app-misc/screen then you can run emerge inside screen and use C-a esc to enter scrollback mode.

Zac
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[Mathieu Seigneurin]

Mark wrote:

>I'll have to try again and see, I've already rebooted to start again.
>When it fails (most recently it was at the qt-xxxx package install, it
>has the usual "post the topmost error" message. But since I'm in the
>console, I can't scroll up higher than the current screen displays.
>How do I get to the error you would need to see? Thanks for the
>help...
>
>  
>
emerge [whatever] >& log.txt

your can also use Shift+PgUp to scrool a console.

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[Peter Humphrey]

Mark wrote:

>I'll have to try again and see, I've already rebooted to start again.
>When it fails (most recently it was at the qt-xxxx package install, it
>has the usual "post the topmost error" message. But since I'm in the
>console, I can't scroll up higher than the current screen displays.
>How do I get to the error you would need to see? Thanks for the
>help...
>  
>

Shift-PgUp should scroll the screen up provided you haven't switched
consoles. Or you could define a portage log directory in your make.conf,
remembering to create it of course, then ls -lrt will show you the most
recent file and you can read there what happened.

My make.conf includes: PORT_LOGDIR=/var/log/portage.

HTH.

-- 
Rgds
Peter Humphrey
Linux Counter 5290, Aug 93.

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[A.Watson]

Sean Sullivan wrote:

>On Sunday 10 July 2005 09:25, Mark wrote:
>  
>
>>I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
>>It keeps failing in the emerge --emptytree system process. I suspect
>>my make.conf is the problem. So a couple questions...
>>
>>1. On the USE flags, this time around, I put in everything that
>>sounded like I wanted, which ended up being a very long list. Am I
>>better off having a very short list of USE flags, as shown in the
>>example in the docs?
>>
>>2. I have -march=athlon64 in my make.conf file. My processor is an
>>AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
>>my whole problem rather than my USE flags list??
>>
>>Thanks all,
>>--
>>Mark
>>[unwieldy legal disclaimer would go here - feel free to type your own]
>>    
>>
>
>march=athlon64 should be fine for your CPU. I use it and have an AMD64 3000+. 
>How exactly does the emerge fail? What is the error you see? Doubtful it has 
>anything to do with your USE flags, so we'll prob need to see the error.
>
>Here is my make.conf for comparison (and I have a lot of USE flags)
>--------------------------
>CHOST="x86_64-pc-linux-gnu"
>CFLAGS="-march=athlon64 -O2 -pipe"
>CXXFLAGS="${CFLAGS}"
>
>ACCEPT_KEYWORDS="~amd64" 
>MAKEOPTS="-j2"
>
> USE="-gnome -kde -gtk -arts acpi alsa X audiofile avi -bonobo
>   cdparanoia cdr crypt cups dbm divx4linux dvd dvdread gtk2
>   encode imagemagick mailwrapper mozilla mpeg mysqli multilib
>   nvidia ogg oggvorbis oss opengl pam perl python qt samba ssl
>   mysql php xine amd64 apache2 cups acl xml readline libclamav" 
>--------------------------
>
>-Sean
>  
>
You said it failed on the QT package, maybe you should enable kde in
your USE flags. If you dont want kde then do you really need QT? Also
running ~amd64 can and will b0rk you. Use package.keywords for any
~amd64 packages that you require.

If you continue to have errors post you output of "emerge info".
Hope that helped
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: emerge --emptytree problem

[Mark]

Well, I *think* I have it figured out. After setting up the logging, I
fired up the build again, and when it finally failed, there was a
message "you need perl 5" during the openssl package install. So I
tried emerging perl by itself, and it fails because the java ebuild
was not in the portage directory. So I changed java in my USE= list to
-java, and restarted the build. So far, it's going well. My question I
guess is, did I come up with the right solution, or will having -java
in my USE= list cause me problems later on?

On 7/10/05, Mark <whitetr6@gmail.com> wrote:
> I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
> It keeps failing in the emerge --emptytree system process. I suspect
> my make.conf is the problem. So a couple questions...
> 
> 1. On the USE flags, this time around, I put in everything that
> sounded like I wanted, which ended up being a very long list. Am I
> better off having a very short list of USE flags, as shown in the
> example in the docs?
> 
> 2. I have -march=athlon64 in my make.conf file. My processor is an
> AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
> my whole problem rather than my USE flags list??
> 
> Thanks all,
> --
> Mark
> [unwieldy legal disclaimer would go here - feel free to type your own]
> 


-- 
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: emerge --emptytree problem

[Jared Lindsay]

I seem to remember an older version of the handbook (2004.0 or so)
suggesting you compile with -java so that your compile time was
greatly reduced.  So I think you are fine.

Besides, I can't think of any system package that requires java...

On 7/10/05, Mark <whitetr6@gmail.com> wrote:
> Well, I *think* I have it figured out. After setting up the logging, I
> fired up the build again, and when it finally failed, there was a
> message "you need perl 5" during the openssl package install. So I
> tried emerging perl by itself, and it fails because the java ebuild
> was not in the portage directory. So I changed java in my USE= list to
> -java, and restarted the build. So far, it's going well. My question I
> guess is, did I come up with the right solution, or will having -java
> in my USE= list cause me problems later on?
> 
> On 7/10/05, Mark <whitetr6@gmail.com> wrote:
> > I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
> > It keeps failing in the emerge --emptytree system process. I suspect
> > my make.conf is the problem. So a couple questions...
> >
> > 1. On the USE flags, this time around, I put in everything that
> > sounded like I wanted, which ended up being a very long list. Am I
> > better off having a very short list of USE flags, as shown in the
> > example in the docs?
> >
> > 2. I have -march=athlon64 in my make.conf file. My processor is an
> > AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
> > my whole problem rather than my USE flags list??
> >
> > Thanks all,
> > --
> > Mark
> > [unwieldy legal disclaimer would go here - feel free to type your own]
> >
> 
> 
> --
> Mark
> [unwieldy legal disclaimer would go here - feel free to type your own]
> 
> --
> gentoo-amd64@gentoo.org mailing list
> 
>

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: emerge --emptytree problem

[Duncan]

Mark posted <1f81f7e0050710155471f76f63@mail.gmail.com>, excerpted below, 
on Sun, 10 Jul 2005 18:54:37 -0400:

> Well, I *think* I have it figured out. After setting up the logging, I
> fired up the build again, and when it finally failed, there was a message
> "you need perl 5" during the openssl package install. So I tried emerging
> perl by itself, and it fails because the java ebuild was not in the
> portage directory. So I changed java in my USE= list to -java, and
> restarted the build. So far, it's going well. My question I guess is, did
> I come up with the right solution, or will having -java in my USE= list
> cause me problems later on?

As Jared says, nothing in the system or normal non-system core packages
require Java (save for OOo, which might, I know the 2.x versions do, if
you call that "core" for your use). USE=-java /does/ speed up gcc compile
time in particular, and as long as you don't have any specific packages in
your personal "must-have" list that are Java based, it should be fine.

For this reason, it's likely many/most devs and list regulars have
USE=-java, so system building with +java is likely far less tested than
with -java.  It's quite possible there's some circular dependency issue
involving the java USE flag, that simply hasn't been discovered yet, for
that reason.  Once you get your USE=-java emerge --emptytree completed, if
desired, you can probably reactivate USE=java and do an emerge --newuse,
with no further issues.  If indeed that's the case, and you feel like
pursuing the issue far enough to file a decent bug report on whatever
circular dependency was killing the emerge --emptytree, with USE=java,
it's quite likely the devs involved would be appreciative, as those
circular dependency issues can be tough to track down, as well as
challenging to resolve, but doing so results in a much more dependable
Gentoo.  

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: emerge --emptytree problem

[John C. Shimek]

I remember having problems with java and perl dependencies on the Gentoo 
1.4 I think it was.  I don't remember exactly what being 2 years ago and 
that being my very first experience to Gentoo.  I thought it had been 
fixed but I don't know anymore.  Setting -java in the USE flags was my 
work around too and I have not had any problems.  I have since added it 
back in.  It was just required for the initial build for me.

John C. Shimek

Duncan wrote:

>Mark posted <1f81f7e0050710155471f76f63@mail.gmail.com>, excerpted below, 
>on Sun, 10 Jul 2005 18:54:37 -0400:
>
>  
>
>>Well, I *think* I have it figured out. After setting up the logging, I
>>fired up the build again, and when it finally failed, there was a message
>>"you need perl 5" during the openssl package install. So I tried emerging
>>perl by itself, and it fails because the java ebuild was not in the
>>portage directory. So I changed java in my USE= list to -java, and
>>restarted the build. So far, it's going well. My question I guess is, did
>>I come up with the right solution, or will having -java in my USE= list
>>cause me problems later on?
>>    
>>
>
>As Jared says, nothing in the system or normal non-system core packages
>require Java (save for OOo, which might, I know the 2.x versions do, if
>you call that "core" for your use). USE=-java /does/ speed up gcc compile
>time in particular, and as long as you don't have any specific packages in
>your personal "must-have" list that are Java based, it should be fine.
>
>For this reason, it's likely many/most devs and list regulars have
>USE=-java, so system building with +java is likely far less tested than
>with -java.  It's quite possible there's some circular dependency issue
>involving the java USE flag, that simply hasn't been discovered yet, for
>that reason.  Once you get your USE=-java emerge --emptytree completed, if
>desired, you can probably reactivate USE=java and do an emerge --newuse,
>with no further issues.  If indeed that's the case, and you feel like
>pursuing the issue far enough to file a decent bug report on whatever
>circular dependency was killing the emerge --emptytree, with USE=java,
>it's quite likely the devs involved would be appreciative, as those
>circular dependency issues can be tough to track down, as well as
>challenging to resolve, but doing so results in a much more dependable
>Gentoo.  
>
>  
>

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: emerge --emptytree problem

[Mark]

Thanks all. Well, sometime in the middle of the night, the build
failed again, this time on ldap, while trying to install samba. I
think what I'll do is scale the USE list wayyyy back.

As I'm reading more, and especially from the comments from those who
have responded here, I think my approach is wrong. The first time I
installed Gentoo, which was 2004.3, I used a USE list almost identical
to what's in the manual, because I had no idea what would work and
what wouldn't.

That gave me a pretty stable system, except some programs would grab
all of the CPU for a minute or two (e.g. PAN newsreader). Then one
night I did an emerge --update world, made the suggested updates with
etc-update, and rebooted. I no longer had a usable kde at that point.
So, not worrying about the few things I'd lose, I just started
rebuilding from scratch, which brings me to now.

I'm going to research some more and see how much I can learn about
setting these options before I try again.

On 7/11/05, John C. Shimek <jcshimek@mn.rr.com> wrote:
> I remember having problems with java and perl dependencies on the Gentoo
> 1.4 I think it was.  I don't remember exactly what being 2 years ago and
> that being my very first experience to Gentoo.  I thought it had been
> fixed but I don't know anymore.  Setting -java in the USE flags was my
> work around too and I have not had any problems.  I have since added it
> back in.  It was just required for the initial build for me.
> 
> John C. Shimek
> 
> Duncan wrote:
> 
> >Mark posted <1f81f7e0050710155471f76f63@mail.gmail.com>, excerpted below,
> >on Sun, 10 Jul 2005 18:54:37 -0400:
> >
> >
> >
> >>Well, I *think* I have it figured out. After setting up the logging, I
> >>fired up the build again, and when it finally failed, there was a message
> >>"you need perl 5" during the openssl package install. So I tried emerging
> >>perl by itself, and it fails because the java ebuild was not in the
> >>portage directory. So I changed java in my USE= list to -java, and
> >>restarted the build. So far, it's going well. My question I guess is, did
> >>I come up with the right solution, or will having -java in my USE= list
> >>cause me problems later on?
> >>
> >>
> >
> >As Jared says, nothing in the system or normal non-system core packages
> >require Java (save for OOo, which might, I know the 2.x versions do, if
> >you call that "core" for your use). USE=-java /does/ speed up gcc compile
> >time in particular, and as long as you don't have any specific packages in
> >your personal "must-have" list that are Java based, it should be fine.
> >
> >For this reason, it's likely many/most devs and list regulars have
> >USE=-java, so system building with +java is likely far less tested than
> >with -java.  It's quite possible there's some circular dependency issue
> >involving the java USE flag, that simply hasn't been discovered yet, for
> >that reason.  Once you get your USE=-java emerge --emptytree completed, if
> >desired, you can probably reactivate USE=java and do an emerge --newuse,
> >with no further issues.  If indeed that's the case, and you feel like
> >pursuing the issue far enough to file a decent bug report on whatever
> >circular dependency was killing the emerge --emptytree, with USE=java,
> >it's quite likely the devs involved would be appreciative, as those
> >circular dependency issues can be tough to track down, as well as
> >challenging to resolve, but doing so results in a much more dependable
> >Gentoo.
> >
> >
> >
> 
> --
> gentoo-amd64@gentoo.org mailing list
> 
> 


-- 
Mark
[unwieldy legal disclaimer would go here - feel free to type your own]

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[Pete Pardoe]

Mark

It should be march=k8 and yes put only the essentials in your USE
flags, you can the others as required later.

Pete

On 7/10/05, Mark <whitetr6@gmail.com> wrote:
> I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
> It keeps failing in the emerge --emptytree system process. I suspect
> my make.conf is the problem. So a couple questions...
> 
> 1. On the USE flags, this time around, I put in everything that
> sounded like I wanted, which ended up being a very long list. Am I
> better off having a very short list of USE flags, as shown in the
> example in the docs?
> 
> 2. I have -march=athlon64 in my make.conf file. My processor is an
> AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
> my whole problem rather than my USE flags list??
> 
> Thanks all,
> --
> Mark
> [unwieldy legal disclaimer would go here - feel free to type your own]
> 
> --
> gentoo-amd64@gentoo.org mailing list
> 
> 


-- 
Pete Pardoe

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] emerge --emptytree problem

[Jared Lindsay]

I second going more minimalist on your USE flags for the installation,
then adding the rest of what you want after the system is up.  That
way, you won't be installing a bunch of extra things with the system
metapackage, which will lead to a smaller initial install (and
faster).  For instance, I have never seen samba be a required
installation, which means it is part of your USE variable.

On 7/11/05, Pete Pardoe <pete.pardoe@gmail.com> wrote:
> Mark
> 
> It should be march=k8 and yes put only the essentials in your USE
> flags, you can the others as required later.
> 
> Pete
> 
> On 7/10/05, Mark <whitetr6@gmail.com> wrote:
> > I'm rebuilding my system from scratch, using 2005 and a stage 2 build.
> > It keeps failing in the emerge --emptytree system process. I suspect
> > my make.conf is the problem. So a couple questions...
> >
> > 1. On the USE flags, this time around, I put in everything that
> > sounded like I wanted, which ended up being a very long list. Am I
> > better off having a very short list of USE flags, as shown in the
> > example in the docs?
> >
> > 2. I have -march=athlon64 in my make.conf file. My processor is an
> > AMD64 Athlon 3200+. Is that the correct march= setting? Maybe that's
> > my whole problem rather than my USE flags list??
> >
> > Thanks all,
> > --
> > Mark
> > [unwieldy legal disclaimer would go here - feel free to type your own]
> >
> > --
> > gentoo-amd64@gentoo.org mailing list
> >
> >
> 
> 
> --
> Pete Pardoe
> 
> --
> gentoo-amd64@gentoo.org mailing list
> 
>

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: emerge --emptytree problem

[Duncan]

Pete Pardoe posted <6c6bf1720507111328106c237b@mail.gmail.com>, excerpted
below,  on Mon, 11 Jul 2005 17:28:21 -0300:

> It should be march=k8 and yes put only the essentials in your USE flags,
> you can the others as required later.

At this point, gcc,'s march= option treats k8, opteron, athlon64, and
athlon-fx, as synonyms for the exact same optimizations.  It doesn't
really matter which one you use, they all do exactly the same thing.

(List checked against the gcc 3.4.4 and 4.0.1 man pages, since I have
3.3.4 and a 4.0.1 preview merged, here.)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman in
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html


-- 
gentoo-amd64@gentoo.org mailing list