[sabayon-dev] build error

2014-02-20 Thread Roelof Wobben

Hello,

I try to update Cinnamon.
But I see this output :

ebuild cinnamon-2.0.14.ebuild manifest
 * ERROR: gnome-extra/cinnamon-2.0.14::sabayon failed (depend phase):
 *   autotools.eclass could not be found by inherit()
 *
 * Call stack:
 *ebuild.sh, line 545:  Called source 
'/usr/local/portage/gnome-extra/cinnamon/cinnamon-2.0.14.ebuild'
 *   cinnamon-2.0.14.ebuild, line  11:  Called inherit 'autotools' 
'eutils' 'gnome2' 'multilib' 'pax-utils' 'python-single-r1'

 *ebuild.sh, line 257:  Called die
 * The specific snippet of code:
 *   [[ -z ${location} ]]  die ${1}.eclass could not be 
found by inherit()

 *
 * If you need support, post the output of `emerge --info 
'=gnome-extra/cinnamon-2.0.14::sabayon'`,
 * the complete build log and the output of `emerge -pqv 
'=gnome-extra/cinnamon-2.0.14::sabayon'`.

 * Working directory: '/usr/lib64/portage/pym'
 * S: '/var/tmp/portage/gnome-extra/cinnamon-2.0.14/work/cinnamon-2.0.14'


I have setup my local repo at /usr/local/portage.

Roelof

---
Dit e-mailbericht bevat geen virussen en malware omdat avast! 
Antivirus-bescherming actief is.
http://www.avast.com




Re: [sabayon-dev] build error

2014-02-20 Thread Mitch Harder
On Thu, Feb 20, 2014 at 2:20 AM, Roelof Wobben r.wob...@home.nl wrote:
 Hello,

 I try to update Cinnamon.
 But I see this output :

 ebuild cinnamon-2.0.14.ebuild manifest
  * ERROR: gnome-extra/cinnamon-2.0.14::sabayon failed (depend phase):
  *   autotools.eclass could not be found by inherit()
  *
  * Call stack:
  *ebuild.sh, line 545:  Called source
 '/usr/local/portage/gnome-extra/cinnamon/cinnamon-2.0.14.ebuild'
  *   cinnamon-2.0.14.ebuild, line  11:  Called inherit 'autotools' 'eutils'
 'gnome2' 'multilib' 'pax-utils' 'python-single-r1'
  *ebuild.sh, line 257:  Called die
  * The specific snippet of code:
  *   [[ -z ${location} ]]  die ${1}.eclass could not be found by
 inherit()
  *
  * If you need support, post the output of `emerge --info
 '=gnome-extra/cinnamon-2.0.14::sabayon'`,
  * the complete build log and the output of `emerge -pqv
 '=gnome-extra/cinnamon-2.0.14::sabayon'`.
  * Working directory: '/usr/lib64/portage/pym'
  * S: '/var/tmp/portage/gnome-extra/cinnamon-2.0.14/work/cinnamon-2.0.14'


 I have setup my local repo at /usr/local/portage.


You need to set up a layout.conf file in you local repository.

This will instruct portage to use gentoo's eclasses for the ebuilds in
your repo.

http://wiki.gentoo.org/wiki/Repository_format/metadata/layout.conf



Re: [sabayon-dev] build error

2014-02-20 Thread Steven Cristian
Did he do a --sync to emerge? In order to download the gentoo eclasses?


On Thu, Feb 20, 2014 at 2:01 PM, Mitch Harder mitch.har...@sabayonlinux.org
 wrote:

 On Thu, Feb 20, 2014 at 2:20 AM, Roelof Wobben r.wob...@home.nl wrote:
  Hello,
 
  I try to update Cinnamon.
  But I see this output :
 
  ebuild cinnamon-2.0.14.ebuild manifest
   * ERROR: gnome-extra/cinnamon-2.0.14::sabayon failed (depend phase):
   *   autotools.eclass could not be found by inherit()
   *
   * Call stack:
   *ebuild.sh, line 545:  Called source
  '/usr/local/portage/gnome-extra/cinnamon/cinnamon-2.0.14.ebuild'
   *   cinnamon-2.0.14.ebuild, line  11:  Called inherit 'autotools'
 'eutils'
  'gnome2' 'multilib' 'pax-utils' 'python-single-r1'
   *ebuild.sh, line 257:  Called die
   * The specific snippet of code:
   *   [[ -z ${location} ]]  die ${1}.eclass could not be found
 by
  inherit()
   *
   * If you need support, post the output of `emerge --info
  '=gnome-extra/cinnamon-2.0.14::sabayon'`,
   * the complete build log and the output of `emerge -pqv
  '=gnome-extra/cinnamon-2.0.14::sabayon'`.
   * Working directory: '/usr/lib64/portage/pym'
   * S: '/var/tmp/portage/gnome-extra/cinnamon-2.0.14/work/cinnamon-2.0.14'
 
 
  I have setup my local repo at /usr/local/portage.
 

 You need to set up a layout.conf file in you local repository.

 This will instruct portage to use gentoo's eclasses for the ebuilds in
 your repo.

 http://wiki.gentoo.org/wiki/Repository_format/metadata/layout.conf




-- 
Lead-Developer at Project Rogentos (Romanian Gentoo Operating System)
GNU/Linux. Based on Sabayon and Gentoo Linux, Rogentos tends to offer
support mainly for all Romanian Linux users and entrepreneurs which seek to
learn an open and free system based on true values :)
http://rogentos.ro
www.facebook.com/RogentosLinux
https://plus.google.com/106559511636021124919/ Google+



Re: [sabayon-dev] build error

2014-02-20 Thread Steven Cristian
Actually it doesn't have a --sync option, because it's binary oriented. If
you build things with portage, then portage must take the eclasses for
itself. Especially if you do a ebuild file.ebuild manifest
The ebuilds that are in /usr/portage/eclasses either they must already be
there or you must emerge --sync to draw them in. Do you see
autotools.eclass in /usr/portage/eclass ?


On Thu, Feb 20, 2014 at 2:47 PM, Roelof Wobben r.wob...@home.nl wrote:

 Steven Cristian schreef op 20-2-2014 13:42:

  Did he do a --sync to emerge? In order to download the gentoo eclasses?


 Nope. or equo must have a --sync option.

 I will make a layout.conf file and hope everything builds fine.


 Roelof


 ---
 Dit e-mailbericht bevat geen virussen en malware omdat avast!
 Antivirus-bescherming actief is.
 http://www.avast.com





-- 
Lead-Developer at Project Rogentos (Romanian Gentoo Operating System)
GNU/Linux. Based on Sabayon and Gentoo Linux, Rogentos tends to offer
support mainly for all Romanian Linux users and entrepreneurs which seek to
learn an open and free system based on true values :)
http://rogentos.ro
www.facebook.com/RogentosLinux
https://plus.google.com/106559511636021124919/ Google+



Re: [sabayon-dev] build error

2014-02-20 Thread Roelof Wobben

Steven Cristian schreef op 20-2-2014 14:29:
Actually it doesn't have a --sync option, because it's binary 
oriented. If you build things with portage, then portage must take the 
eclasses for itself. Especially if you do a ebuild file.ebuild manifest
The ebuilds that are in /usr/portage/eclasses either they must already 
be there or you must emerge --sync to draw them in. Do you see 
autotools.eclass in /usr/portage/eclass ?




Now Im a little bit confused. The wiki says do not mix emerge and equo.

Roelof


---
Dit e-mailbericht bevat geen virussen en malware omdat avast! 
Antivirus-bescherming actief is.
http://www.avast.com




Re: [sabayon-dev] build error

2014-02-20 Thread Steven Cristian
Then what did you try to do with: ebuild file.ebuild manifest ?


On Thu, Feb 20, 2014 at 4:12 PM, Roelof Wobben r.wob...@home.nl wrote:

 Steven Cristian schreef op 20-2-2014 14:29:

  Actually it doesn't have a --sync option, because it's binary oriented.
 If you build things with portage, then portage must take the eclasses for
 itself. Especially if you do a ebuild file.ebuild manifest
 The ebuilds that are in /usr/portage/eclasses either they must already be
 there or you must emerge --sync to draw them in. Do you see
 autotools.eclass in /usr/portage/eclass ?


 Now Im a little bit confused. The wiki says do not mix emerge and equo.


 Roelof


 ---
 Dit e-mailbericht bevat geen virussen en malware omdat avast!
 Antivirus-bescherming actief is.
 http://www.avast.com





-- 
Lead-Developer at Project Rogentos (Romanian Gentoo Operating System)
GNU/Linux. Based on Sabayon and Gentoo Linux, Rogentos tends to offer
support mainly for all Romanian Linux users and entrepreneurs which seek to
learn an open and free system based on true values :)
http://rogentos.ro
www.facebook.com/RogentosLinux
https://plus.google.com/106559511636021124919/ Google+



Re: [sabayon-dev] build error

2014-02-20 Thread Roelof Wobben

Steven Cristian schreef op 20-2-2014 16:00:

Then what did you try to do with: ebuild file.ebuild manifest ?



Oke, I did that because I could not find how to build packages with equo.
I only found that command to make the manifest.

Roelof


---
Dit e-mailbericht bevat geen virussen en malware omdat avast! 
Antivirus-bescherming actief is.
http://www.avast.com




Re: [sabayon-dev] build error

2014-02-20 Thread Steven Cristian
Building equo packages means you need to start building with portage.
Portage ebuilds create packages, eit + equo puts them into repos [eit] and
manages them [equo]
I can help you with the technique of building packages if you need :) I've
made a special tutorial for funtoo also to build their equo packages.

Here it is, and send me private email of you need further help!
http://www.funtoo.org/Entropy


On Thu, Feb 20, 2014 at 5:30 PM, Roelof Wobben r.wob...@home.nl wrote:

 Steven Cristian schreef op 20-2-2014 16:00:

  Then what did you try to do with: ebuild file.ebuild manifest ?


 Oke, I did that because I could not find how to build packages with equo.
 I only found that command to make the manifest.


 Roelof


 ---
 Dit e-mailbericht bevat geen virussen en malware omdat avast!
 Antivirus-bescherming actief is.
 http://www.avast.com





-- 
Lead-Developer at Project Rogentos (Romanian Gentoo Operating System)
GNU/Linux. Based on Sabayon and Gentoo Linux, Rogentos tends to offer
support mainly for all Romanian Linux users and entrepreneurs which seek to
learn an open and free system based on true values :)
http://rogentos.ro
www.facebook.com/RogentosLinux
https://plus.google.com/106559511636021124919/ Google+



Re: [sabayon-dev] build error

2014-02-20 Thread Roelof Wobben

Fabio Erculiani schreef op 20-2-2014 18:52:

On Thu, Feb 20, 2014 at 3:12 PM, Roelof Wobben r.wob...@home.nl wrote:

Steven Cristian schreef op 20-2-2014 14:29:


Actually it doesn't have a --sync option, because it's binary oriented. If
you build things with portage, then portage must take the eclasses for
itself. Especially if you do a ebuild file.ebuild manifest
The ebuilds that are in /usr/portage/eclasses either they must already be
there or you must emerge --sync to draw them in. Do you see autotools.eclass
in /usr/portage/eclass ?


Now Im a little bit confused. The wiki says do not mix emerge and equo.

emerge --sync only updates the portage tree checkout on your disk
(which is located at /usr/portage)




Thanks for the explanation.

Roelof


---
Dit e-mailbericht bevat geen virussen en malware omdat avast! 
Antivirus-bescherming actief is.
http://www.avast.com