version=git not installed at configure time

[ArcEye]

Issue by cdsteinkuehler
Sun Jul 6 01:14:52 2014
Originally opened as machinekit/machinekit#236

---

I am using the BeagleBone packages on a fresh install of the current latest BeagleBone Debian image (bone-debian-7.4-2014-04-23-2gb.img.xz), and I am having issues getting things running. While reviewing the logs, I notice the following every time I attempt to launch LinuxCNC:

Jul 6 01:09:03 beaglebone msgd:0: MSGD:0 mlock(global) failed: 12 'Cannot allocate memory'
Jul 6 01:09:03 beaglebone msgd:0: startup instance=inst0 pid=6003 flavor=xenomai rtlevel=1 usrlevel=1 halsize=512000 shm=Posix gcc=4.6.3 version=git not installed at configure time
Jul 6 01:09:03 beaglebone msgd:0: configured: Jul 1 2014 12:27:54 sha=git not installed or executable
Jul 6 01:09:03 beaglebone msgd:0: built: Jul 1 2014 12:29:13 sha=git not installed or executable

I am working on the "cannot allocate memory" issue, but it looks like the version= and sha= are a goof in the way packages are getting built.

[ArcEye]

Comment by mhaberler
Sun Jul 6 03:11:33 2014

---

yes, thats a bugger - it is a consequence of the fact that currently debian packages are built from tarballs which do not carry the git SHA.

John and me discussed several ways to get around that - "mere work" :-/

[ArcEye]

Comment by zultron
Sun Jul 6 03:17:01 2014

---

Related to #163 and #67

[ArcEye]

Comment by cdsteinkuehler
Sun Jan 4 18:35:34 2015

---

Looks like this is still an issue. Is any of the "mere work" something that "mere mortals" can do, or is it a John vs. the Buildbot sort of thing?

[ArcEye]

Comment by zultron
Tue Jan 13 17:01:39 2015

---

(Sorry, dealing with inbox backlog in FILO order :P )

The version=git not installed at configure time and sha=git not installed or executable messages are confusing to me, and there are some funky messages that come up during a build from tarball (as opposed to build from git tree). The worst few might be addressed in #327 (almost ready for merge), but I'd like to see the rest fixed.

The 'mere work' @mhaberler mentions is, erm, I don't remember exactly, but probably some way to get the git rev from e.g. an environment variable (maybe $MACHINEKIT_GIT_REV) if not building in a git tree. That piece is something 'mere mortals' can do.

Once that's present, adding such an environment variable to the Buildbot is trivial, but can only be done by the vermin deities of the Buildbot underbelly.

[ArcEye]

Comment by luminize
Tue Jan 13 17:29:55 2015

---

zultron/machinekit@b5a70b5

zultron/machinekit@171692c

zultron/machinekit@39a4701

FWIW, These are probably not needed anymore.

On 13 Jan 2015, at 18:01, John Morris [email protected] wrote:

(Sorry, dealing with inbox backlog in FILO order :P )

The version=git not installed at configure time and sha=git not installed or executable messages are confusing to me, and there are some funky messages that come up during a build from tarball (as opposed to build from git tree). The worst few might be addressed in #327 (almost ready for merge), but I'd like to see the rest fixed.

The 'mere work' @mhaberler mentions is, erm, I don't remember exactly, but probably some way to get the git rev from e.g. an environment variable (maybe $MACHINEKIT_GIT_REV) if not building in a git tree. That piece is something 'mere mortals' can do.

Once that's present, adding such an environment variable to the Buildbot is trivial, but can only be done by the vermin deities of the Buildbot underbelly.

—
Reply to this email directly or view it on GitHub.