Bug 128468 – [NEW EBUILD] sys-power/s2ram

• Product: Gentoo Linux
• Status: VERIFIED DUPLICATE

[Description Matt Whitlock 2006-04-01 21:42:25 UTC]

This ebuild is for the s2ram program.

From the s2ram web page (http://en.opensuse.org/S2ram):
"The goal of the s2ram binary is to get suspend to RAM working out of the box on as many machines as possible."

Support for s2ram is integrated into the powersave daemon, for which an ebuild is presently pending inclusion into Portage (see bug #122278).

[Comment 1 Matt Whitlock 2006-04-01 21:43:15 UTC]

Created attachment 83684 [details]
sys-power/s2ram-cvs/s2ram-cvs-0.ebuild

[Comment 2 Petric Frank 2006-07-09 15:27:19 UTC]

SourceForge CVS server URL notation have changed.
Old:
  :pserver:[e-mail]:/cvsroot/suspend

New:
  :pserver:[e-mail]:/cvsroot/suspend

After patching the ebuild above the emerge works.

[Comment 3 Jakub Moc (RETIRED) 2007-02-22 03:06:20 UTC]

Now in sunrise overlay (0.5, not this live cvs version)

http://gentoo-sunrise.org/svn/reviewed/sys-power/s2ram

[Comment 4 Torsten Kaiser 2007-03-10 11:09:47 UTC]

sunrise-ebuild fails with newer pciutils:

make[1]: Leaving directory `/var/tmp/portage/sys-power/s2ram-0.5/work/suspend-0.5/vbetool/x86em
u'
x86_64-pc-linux-gnu-gcc -O3 -ffast-math -fomit-frame-pointer -march=opteron -pipe -O2 -Wall -g
s2ram.c vt.o vbetool/thunk.o vbetool/x86-common.o vbetool/vbetool.o vbetool/x86emu/libx86emu.a
radeontool.o dmidecode.o -lpci -o s2ram
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_lo
ad_name_list':
: undefined reference to `gzopen'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_lo
ad_name_list':
: undefined reference to `gzgets'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_lo
ad_name_list':
: undefined reference to `gzclose'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_lo
ad_name_list':
: undefined reference to `gzclose'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_lo
ad_name_list':
: undefined reference to `gzeof'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_lo
ad_name_list':
: undefined reference to `gzopen'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_load_name_list':
: undefined reference to `gzerror'
/usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libpci.a(names.o): In function `pci_load_name_list':
: undefined reference to `gzclose'
collect2: ld returned 1 exit status
make: *** [s2ram] Error 1

!!! ERROR: sys-power/s2ram-0.5 failed.
Call stack:
  ebuild.sh, line 1614:   Called dyn_compile
  ebuild.sh, line 971:   Called qa_call 'src_compile'
  environment, line 2486:   Called src_compile
  s2ram-0.5.ebuild, line 42:   Called die

I have the following version installed:
[I] sys-apps/pciutils
     Available versions:  2.2.3-r2 (~)2.2.4 (~)2.2.4-r2
     Installed versions:  2.2.4-r2(18:35:48 02/15/07)(zlib)

Using the following commandline, I got it do compile on ~amd64:
USE=-zlib emerge -1 pciutils s2ram

[Comment 5 Jakub Moc (RETIRED) 2007-03-10 11:36:44 UTC]

(In reply to comment #4)
> sunrise-ebuild fails with newer pciutils:
> Using the following commandline, I got it do compile on ~amd64:
> USE=-zlib emerge -1 pciutils s2ram

Yeah, use this... I have no intent to debug a retarded pciutils flag; if you have a patch, attach it here and I'll add it.

[Comment 6 Nathan Caldwell 2007-11-13 03:26:02 UTC]

I just checked out the 0.5 ebuild, and have a few things to report.

First, as of kernel 2.6.23 CONFIG_SOFTWARE_SUSPEND has been changed to CONFIG_HIBERNATION.

Also, I bumped the ebuild to 0.7 and everything seems to work, except there needs to be an added DEPEND on dev-libs/libx86.

[Comment 7 Jakub Moc (RETIRED) 2007-11-13 09:16:50 UTC]

suspend-0.9_pre20070917 (17 Sep 2007)

  17 Sep 2007; Alon Bar-Lev <[e-mail]> +metadata.xml,
  +suspend-0.9_pre20070917.ebuild:
  Initial add, bug#156431


*** This bug has been marked as a duplicate of bug 156431 ***