|
On 23/02/17 19:39, Daniel Skrlin wrote:
It indicates incorrect linkage in the build of the component. Without the component code and knowing how it was built, unable to guess further If hal_exit() did not exist, machinekit would not run, there are about 1230 binaries and libs linked against it. Running nm -C hal_p260c | grep " U " from the dir it is in, will list all the symbols which are undefined. (U) I would suspect a great deal more than just hal_exit() hal_exit() is an inline accessor to halg_exit() contained in https://github.com/machinekit/machinekit/blob/master/src/hal/lib/hal.h#L379 So you may see references to halg_exit
-- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout. |
- Re: [Machinekit] Re: Machinekit mul... Robert Nelson
- [Machinekit] Re: Machinekit mul... Marius Alksnys
- Re: [Machinekit] Re: Machinekit... Alexander Rössler
- Re: [Machinekit] Re: Machinekit mul... [email protected]
- Re: [Machinekit] Re: Machinekit multico... Charles Steinkuehler
- Re: [Machinekit] Re: Machinekit mul... Charles Steinkuehler
- [Machinekit] Re: Machinekit multicore merge Daniel Skrlin
- [Machinekit] Re: Machinekit multicore merge Daniel Skrlin
- Re: [Machinekit] Re: Machinekit multico... [email protected]
- Re: [Machinekit] Re: Machinekit mul... Daniel Skrlin
