On Wed, Sep 9, 2020 at 12:28 PM jonnymo <[email protected]> wrote: > > Yeah, I missed where this was shown in the email. > > As far as the link for Drerk's web page is concerned, I suspect it is a > reference to the first ed of his book. > > From what I gathered, syscall is not POSIX compliant and could cause > compatibility issues so it's use is discouraged. This I would suspect is why > there are suggestions from the error when running the example to use > 'swscanf' and 'getpt' instead. > > However, as you found, 'syscall' is defined in 'unistd.h' so having this > included is required which does not seem that new. Then again, the code on > Derek's site is at least 6 years old and may not be kept up to date which > could explain the use of syscall there.
I've found a few references to 4.7.x gcc and C89/C99 that this changed, but haven't found the git commit/explanation.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CAOCHtYjC3jsb-F%2BJoCWkNT0aKRxtKFxO75AuJD%2BcT8KSvyn4cQ%40mail.gmail.com.
