Nemiver has a memory widget, extract from help: "The memory widget allows you to view a section of memory directly. This enables you to get a lower-level view of what's happening while your program is running." Reproducible: Always Steps to Reproduce: 1. Start nemiver 2. Seek for memory widget Actual Results: No memory widget present. Expected Results: Ability to choose the memory widget. The memory widget is only build if enabled by configure script. It should be build by default, but the ebuild always disables it.
I'm sorry to bother the bugzilla admins, I selected the bad product and I did only found it out, after I saw in the bug, that was assigned to Bugzilla Admins and not bugwrangler. I'm sorry about that and I apologize for the bug spam. I did change the product by myself, but can't change the "Assigned To" field.
Created attachment 162290 [details] ebuild with additional use flag for memory view widget Attached is a ebuild, whichs build the memory widget based on a use flag.
(mass-change) Please do not use the Bugzilla product for system issues. Per the large red text it is only for problems with the Gentoo bugs.gentoo.org site only.
Some additional informations: nemiver with enabled memory widget works for me on a amd64 machine (most packages are stable). I guess, it would also works with app-editors/ghex-2.21.90 (needs at least gtkhex-2.21.40 to compile), but I didn't test it. # emerge --info (extract) Portage 2.1.4.4 (default/linux/amd64/2008.0, gcc-4.1.2, glibc-2.6.1-r0, 2.6.25-gentoo-r7 x86_64) ================================================================= System uname: 2.6.25-gentoo-r7 x86_64 AMD Athlon(tm) 64 Processor 3400+ Timestamp of tree: Mon, 04 Aug 2008 07:34:01 +0000 app-shells/bash: 3.2_p33 dev-lang/python: 2.5.2-r6 dev-python/pycrypto: 2.0.1-r6 sys-apps/baselayout: 1.12.11.1 sys-apps/sandbox: 1.2.18.1-r2 sys-devel/autoconf: 2.13, 2.61-r2 sys-devel/automake: 1.5, 1.7.9-r1, 1.8.5-r3, 1.9.6-r2, 1.10.1 sys-devel/binutils: 2.18-r3 sys-devel/gcc-config: 1.4.0-r4 sys-devel/libtool: 1.5.26 virtual/os-headers: 2.6.23-r3 ACCEPT_KEYWORDS="amd64" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-march=athlon64 -O2 -pipe" CHOST="x86_64-pc-linux-gnu" CXXFLAGS="-march=athlon64 -O2 -pipe" LANG="en_US.UTF-8" LDFLAGS="-Wl,-O1" MAKEOPTS="-j2" Unset: CPPFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, INSTALL_MASK, LC_ALL, PORTAGE_COMPRESS, PORTAGE_COMPRESS_FLAGS
is this fixed in 0.6.4 ? Is there any upstream bug to refer to ?
The ebuild just needs to be modified. Jean-Marc's proposal seems good, provided we don't forget to update metadata.xml
in 0.6.6. Thanks for reporting and sorry for taking so long to implement.
