Bugzilla Bug 119178

I need possibility to build jfsutils statically, 
may be include this possibility to official portage tree?

ebuild in attachment, here is patch to show what I changed:

--- /usr/portage/sys-fs/jfsutils/jfsutils-1.1.10.ebuild 2005-10-30
00:37:06.000000000 +0400
+++ jfsutils-1.1.10-r1.ebuild   2006-01-16 13:30:01.584890750 +0300
@@ -9,13 +9,16 @@
 LICENSE="GPL-2"
 SLOT="0"
 KEYWORDS="~amd64 ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sparc ~x86"
-IUSE=""
+IUSE="static"

 DEPEND="virtual/libc"

 src_compile() {
-       econf \
-               --sbindir=/sbin || die "econf failed"
+       if use static; then
+               CFLAGS="${CFLAGS} -static"
+       fi
+       CFLAGS="${CFLAGS}" econf \
+       --sbindir=/sbin || die "econf failed"
        emake || die
 }

Created an attachment (id=77242) [edit]
jfsutils-1.1.10-r1.ebuild

We aren't supposed to modify CFLAGS directly in ebuilds. Any chance you could
rewrite it using the flag-o-matic eclass?

Created an attachment (id=77740) [edit]
jfsutils-1.1.10-r1.ebuild

> Any chance you could
> rewrite it using the flag-o-matic eclass?

You mean something like this?

I looked at some ebuilds under app-shells which have a static USE flag and they
use append-ldflags instead of append-flags. Can you try making that change and
confirm that it still links statically?

>Can you try making that change and
>confirm that it still links statically?

with append-ldflags all work fine.

Thanks, in portage.