Snafu with Hal, upgrading from 2.4.6 to 2.6.

[attachment:1]IMG_20160630_233833.jpg[/attachment

After a fresh install on a new hd and load of lcnc 2.6.2( i think), I compiled my components and went to run lcnc only to get the message.



I don't use the <= or => in my Hal file, as they supposedly don't make a difference and I find them confusing, any way, as soon as lcnc sees an = with out the pointer , it throws this error. If I add a pointer , problem goes away until the next = . I can change them all to having a pointer. Any one have any idea what is causing this? Thanks

I can attach the Hal file if it will help

From the source code commit:

halcmd: Better detection of some arrow-related typos

This fixes a confusing result where the command

net name firstpin <=secondpin => thirdpin

(note the missing space) would connect firstpin and thirdpin, but leave

secondpin unconnected, and would not give an error.



With this change, only the three expected arrows: =>, <=, <=> (see man halcmd)

are accepted, and only if they are a separate word that matches exactly; this

causes the net command above to fail with:

Pin '<=secondpin' does not exist

This will fail unexpected arrows like ===> that were previously accepted but

never documented as accepted.