Re: MOM: Probe
Hi Malihe,
On Mon, Aug 10, 2015 at 06:15:18PM +0430, Malihe Asemani wrote:
> > I think there is just hybrid_36_c.o missing in the list of linked object
> > files. (This is just an assumption - please try.)
>
> You're right. I checked the making process using the Makefile not the
> Makefile.linux :P
>
> > You need to use
> > quilt new fix_build_issue.patch
> > quilt edit Makefile.linux
> > if this does not work please ask Michael - he previously confirmed that
> > he was able to build the program.
> >
> > The patch is added and It is built correctly :)
> Although, I don't know why there are 2 makefile-s (Makefile and
> Makefile.linux) which are not considerably different.
That's a question only upstream can answer. Generally if you find
manually craftet Makefiles (in contrast to automake or cmake) you need
to prepare for some trouble. Sometimes it can be easier for the Debian
maintainer to provide a modern build system to upstream and hope they
will take this over (I did so in the past in a few projects).
> One of the differences was related to hybrid_36_c, which is added to
> Makefile.linux using the fix_build_issue.patch, And the other is "-static"
> flag at the top. I don't know how much important is a flag to create a
> separate Makefile for it? OR, maybe I've missed some points about the
> Makefile-s.
I guess its not your fault. It is simply that upstream is to lazy to
check how to craft modern build system - but may be this project itself
is simple enough that it is not worth any additional effort. Sometimes
reading upstreams installation documentation clarifies things a bit.
> Hints for the rename:
> > I'd recommend to move the git repository on git.debian.org:
> > /git/debian-med.
> > Please also look into the *metadata *of this repository to reflect the
> > changed name.
> >
> Editing the config file is enough?
In principle yes.
> The renaming inside d/control and d/changelog should be clear.
> > The tricky part is that also the binary needs to be renamed since it is
> > taken in the Debian name space which you can check via
> > $ apt-file search /usr/bin/probe
> > mirmon: /usr/bin/probe
> > So providing the binary as /usr/bin/king-probe is probably also simple
> > but I recently implemented a method to keep the original binary name
> > for users who explicitly declare themselves as Debian Med users. You can
> > find an example in the *plink package. *Since this is also maintained in
> > SVN and you seem to have trouble to check this out I'd recommend to use
> > apt-get source plink
> > to have a look into the way how this is done.
>
> Thanks for the hint. I think the Iran IP range is blocked! I pulled plink
> using a server outside Iran :)
Grrr, I hate such filters ... Good you found some workaround.
I think the last missing bit to enable a `gbp buildpackage` to me is the
pristine-tar branch which I wrote in my last mail to the list.
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: