headers
Paul Donohue | 2 Jun 2008 16:56

Re: [opennms-devel] Trouble building Debian packages

All of the build-tree stuff it's doing is being automatically done by cdbs...

I'm not all that familiar with cdbs myself...

I wonder if it's looking in the wrong place for the sources?  Try setting "DEB_SRCDIR = $(CURDIR)" in debian/rules...
https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml#id2480198

I haven't compiled iplike and jicmp in quite a while, but I don't remember having any trouble the last time I
did it, so I'm not really sure what might have changed to cause this behavior.

On Fri, May 30, 2008 at 04:39:19PM +0100, Alex Bennee wrote:
> Hi,
> 
> I'm having real trouble building Debian packages for the ancillary
> programs needed for OpenNMS (iplike and jicmp). The main opennms built
> fine with the appropriate debian directory and a "dpkg-buildpackage
> -rfakeroot -b". However when I try that on the other bits they fail on
> me:
> 
> 16:30 ajb <at> pitcairn/x86_64 [jicmp.svn] >dpkg-buildpackage -rfakeroot -b
> dpkg-buildpackage: set CPPFLAGS to default value:
> dpkg-buildpackage: set CFLAGS to default value: -g -O2
> dpkg-buildpackage: set CXXFLAGS to default value: -g -O2
> dpkg-buildpackage: set FFLAGS to default value: -g -O2
> dpkg-buildpackage: set LDFLAGS to default value: -Wl,-Bsymbolic-functions
> dpkg-buildpackage: source package jicmp
> dpkg-buildpackage: source version 1.0.8-1
> dpkg-buildpackage: source changed by Benjamin Reed <ranger <at> opennms.org>
> dpkg-buildpackage: host architecture amd64
>  fakeroot debian/rules clean
(Continue reading)

Permalink | Reply | 0 comments |
headers
Benjamin Reed | 2 Jun 2008 17:03
Favicon
Gravatar

Re: [opennms-devel] Trouble building Debian packages


Paul Donohue wrote:
| All of the build-tree stuff it's doing is being automatically done by
cdbs...
|
| I'm not all that familiar with cdbs myself...
|
| I wonder if it's looking in the wrong place for the sources?  Try
setting "DEB_SRCDIR = $(CURDIR)" in debian/rules...
| https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml#id2480198
|
| I haven't compiled iplike and jicmp in quite a while, but I don't
remember having any trouble the last time I did it, so I'm not really
sure what might have changed to cause this behavior.

Yeah, the cdbs thing is kind of weird.  It actually expects a tarball in
the same directory that the debian/ dir is, and doesn't care about the
local build files at all.

ie, the way to make it work is to do:

m4/autogen.sh
./configure
make
make dist
dpkg-buildpackage

I don't understand debian's build stuff enough to change it to just pack
up the local stuff instead of requiring the extra step of making a
tarball, but if you do that, it should work.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ronny Trommer | 2 Jun 2008 22:13

[opennms-devel] Provisioning Groups - Bug or Feature ?

Hi *

If you add Node in Provisioning Groups with

  Admin --> Provisioning Groups

the "Site-Name" where added to the asset-info --> Building.

Is this a bug or feature :)

--
Ronny Trommer (Germany)
Web: http://www.open-factory.org
IRC: irc.freenode.org - #opennms

PGP key: 46AD 1D66 1898 0264 D6B8 E241 FED7 B3C8 AB34 7382

--

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
(Continue reading)

Permalink | Reply | 0 comments |
headers
Tarus Balog | 3 Jun 2008 00:14
Favicon

Re: [opennms-devel] Provisioning Groups - Bug or Feature ?


On Jun 2, 2008, at 4:13 PM, Ronny Trommer wrote:

> If you add Node in Provisioning Groups with
>
>  Admin --> Provisioning Groups
>
> the "Site-Name" where added to the asset-info --> Building.
>
> Is this a bug or feature :)

It's a feature.

(grin)

When the importer was created (provisioning groups is just a front end  
to the importer) that was the field most similar to "site".

-T
_______________________________________________________________________
Tarus Balog, OpenNMS Maintainer             Main:   +1 919 533 0160
The OpenNMS Group, Inc.                     Fax:    +1 503 961 7746
Email: tarus <at> opennms.org                    URL: http://www.opennms.org
PGP Key Fingerprint: 8945 8521 9771 FEC9 5481  512B FECA 11D2 FD82 B45C

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
(Continue reading)

Permalink | Reply | 0 comments |
headers
Riccardo Magliocchetti | 3 Jun 2008 12:31
Picon

[opennms-devel] [RFC] memory related fixes for mib2opennms

hi,

the attached patch fix a couple of leaks, check for malloc() failures 
and properly call smiExit() before exiting.

The remaining leak and two of three errors appears to be in libsmi, the
only error is mib2opennms is this:

==8184== Invalid write of size 1
==8184==    at 0x40231D7: strcat (mc_replace_strmem.c:186)
==8184==    by 0x804940F: main (mib2opennms.c:261)
==8184==  Address 0x41c4196 is 0 bytes after a block of size 22 alloc'd
==8184==    at 0x4021AB8: malloc (vg_replace_malloc.c:207)
==8184==    by 0x80493C6: main (mib2opennms.c:249)

It's an off by one somewhere near the strlen but i have to check more 
carefully.

Then i think will be fine to exit(1) on errors.

If you run with proper mibs you'll find one more leak fixed. I 
appreciate if you can test with a set of mibs that output is not changed.

How i checked:

valgrind --tool=memcheck --leak-check=yes ./mib2opennms -6 -f foo foobar

before:

==8142== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 13 from 1)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alex Bennee | 3 Jun 2008 14:06
Favicon

Re: [opennms-devel] Trouble building Debian packages

On Mon, 2008-06-02 at 11:03 -0400, Benjamin Reed wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Paul Donohue wrote:
> | All of the build-tree stuff it's doing is being automatically done by
> cdbs...
> |
> | I'm not all that familiar with cdbs myself...
> |
> | I wonder if it's looking in the wrong place for the sources?  Try
> setting "DEB_SRCDIR = $(CURDIR)" in debian/rules...
> | https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml#id2480198
> |
> | I haven't compiled iplike and jicmp in quite a while, but I don't
> remember having any trouble the last time I did it, so I'm not really
> sure what might have changed to cause this behavior.
> 
> Yeah, the cdbs thing is kind of weird.  It actually expects a tarball in
> the same directory that the debian/ dir is, and doesn't care about the
> local build files at all.

I suspect this can be changed but I guess when it finally gets to debian
it would build with the usual tar + patches approach?

> 
> ie, the way to make it work is to do:
> 
> m4/autogen.sh
> ./configure
(Continue reading)

Permalink | Reply | 0 comments |
headers
Stefan Mikuszeit | 3 Jun 2008 14:13
Picon

Re: [opennms-devel] Trouble building Debian packages

This will help: apt-get install sun-java6-bin

:-)

Regards
Stefan

-----Original Message-----
From: opennms-devel-bounces <at> lists.sourceforge.net
[mailto:opennms-devel-bounces <at> lists.sourceforge.net] On Behalf Of Alex Bennee
Sent: Dienstag, 3. Juni 2008 14:06
To: OpenNMS Code Development and Bugs
Subject: [*****SPAM***** HOM02EX - Header Check] - Re: [opennms-devel] Trouble building Debian
packages - Email found in subject

On Mon, 2008-06-02 at 11:03 -0400, Benjamin Reed wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Paul Donohue wrote:
> | All of the build-tree stuff it's doing is being automatically done 
> | by
> cdbs...
> |
> | I'm not all that familiar with cdbs myself...
> |
> | I wonder if it's looking in the wrong place for the sources?  Try
> setting "DEB_SRCDIR = $(CURDIR)" in debian/rules...
> | https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml#id2480198
> |
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alex Bennee | 3 Jun 2008 14:58
Favicon

Re: [opennms-devel] Trouble building Debian packages

On Tue, 2008-06-03 at 14:13 +0200, Stefan Mikuszeit wrote:
> apt-get install sun-java6-bin

What does it need from here? It's actually installed but I'm using the
openjdk jre and jdk because I want to avoid any pitfalls with the
non-free Java's.

javac does exist whatever configure may think:

10:45 ajb <at> pitcairn/x86_64 [jicmp.svn] >which javac
/usr/bin/javac
13:57 ajb <at> pitcairn/x86_64 [jicmp.svn] >javac -version
javac 1.6.0-internal

--

-- 
Alex Bennee, Software Engineer
As the trials of life continue to take their toll, remember that there
is always a future in Computer Maintenance. -- National Lampoon,
"Deteriorata"

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-devel mailing list
(Continue reading)

Permalink | Reply | 0 comments |
headers
Riccardo Magliocchetti | 3 Jun 2008 15:10
Picon

Re: [opennms-devel] [RFC] memory related fixes for mib2opennms

[added to cc alex benee because he found and fixed the same off by one]

Riccardo Magliocchetti wrote:
> hi,
> 
> the attached patch fix a couple of leaks, check for malloc() failures 
> and properly call smiExit() before exiting.
> 
> The remaining leak and two of three errors appears to be in libsmi, the
> only error is mib2opennms is this:
> 
> ==8184== Invalid write of size 1
> ==8184==    at 0x40231D7: strcat (mc_replace_strmem.c:186)
> ==8184==    by 0x804940F: main (mib2opennms.c:261)
> ==8184==  Address 0x41c4196 is 0 bytes after a block of size 22 alloc'd
> ==8184==    at 0x4021AB8: malloc (vg_replace_malloc.c:207)
> ==8184==    by 0x80493C6: main (mib2opennms.c:249)
> 
> It's an off by one somewhere near the strlen but i have to check more 
> carefully.

Rediffed the patch with this changelog:

- fixed the off by one, this fixed the three read / write error reported 
by memcheck
- removed the exit in case of file open error in order to avoid the leaks
- readded the removal of unneeded initialization in order to keep the 
diff smaller, will redo later

If you agree i'd like to post this patch to bug 2501 which alex already
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jeff Gehlbach | 3 Jun 2008 15:27
Favicon

Re: [opennms-devel] Trouble building Debian packages

On Jun 3, 2008, at 8:58 AM, Alex Bennee wrote:
>> apt-get install sun-java6-bin
>
> What does it need from here? It's actually installed but I'm using the
> openjdk jre and jdk because I want to avoid any pitfalls with the
> non-free Java's.

We would love to run with a fully free JDK, but so far it just hasn't  
been possible.  OpenNMS has historically needed a real Sun JDK, or an  
equivalent real Sun-derived JDK on platforms where Sun does not  
distribute one.  Over the years people have tried Kaffe / GCJ / GIJ /  
IcedTea JDKs, but they have never measured up.  Some lack features  
necessary to bootstrap OpenNMS, others just aren't robust enough to  
run OpenNMS at any real-world scale.

So for now, stick with the Sun JDK.  You're welcome to edit  
OPENNMS_HOME/etc/java.conf after running runjava -s and see what  
happens, but it's not likely to be pretty -- if it breaks, you get to  
keep both pieces :)

-jeff

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ
(Continue reading)

Permalink | Reply | 0 comments |

Gmane