Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

version=git not installed at configure time #111

Closed
ArcEye opened this issue Aug 3, 2018 · 2 comments
Closed

version=git not installed at configure time #111

ArcEye opened this issue Aug 3, 2018 · 2 comments
Labels
bug Cross-Stacks Issue Issue relevant to both HAL and CNC stack

Comments

@ArcEye
Copy link
Contributor

ArcEye commented Aug 3, 2018

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 ArcEye added the bug label Aug 3, 2018
@ArcEye
Copy link
Contributor Author

ArcEye commented Aug 3, 2018

See machinekit/machinekit-cnc#37 for full text, this is a copy header only.

@ArcEye ArcEye added the Cross-Stacks Issue Issue relevant to both HAL and CNC stack label Aug 3, 2018
@cerna
Copy link
Contributor

cerna commented Jul 3, 2020

This is - I think - passé now.

The current build flow requires the git executable as build dependency, so on (Buster) you cannot run the dpkg-buildpackage without it. Building from tarball is also not supported in build flow and as such anybody who wants to do it has to implement his own flow.

I am going to close this issue as solved by passage of time.

@cerna cerna closed this as completed Jul 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Cross-Stacks Issue Issue relevant to both HAL and CNC stack
Projects
None yet
Development

No branches or pull requests

2 participants