gpsd-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

PI3 vs. PI4 - libpthread possible issue?


From: scorpion7
Subject: PI3 vs. PI4 - libpthread possible issue?
Date: Fri, 29 Nov 2019 16:27:57 -0500
User-agent: Microsoft-MacOutlook/10.1f.0.191110

Yes – this is a gpsd forum with ntp (itself) being a bit off topic, however ran into something that may have a related to concern if one were to attempt to compile gpsd on a PI4 with Raspbian (lite/buster).  Short version – both utilize the Adafruit Ultimate GPS Hat with the notion that the PI4 (4G version) would be a “drop-in” replacement for the PI3B+ and the PI3 would be utilized as a time keeper elsewhere.  Thus, only two logical “differences” is the PI “itself” and the fact that the PI3 started out with a much earlier version of Raspbian, but has seen regularly updates/upgrades of the OS.  The PI3 was moved to the Adafruit Ultimate GPS Hat about a month prior – so it’s even the same Hat.

 

If you are using a Pi4 – ntpd won’t even complete the ‘configure’ portion.  While I haven’t tried to compile gpsd (yet), wondering if the same issue would present itself (as gpsd utilizes libpthread, no?) – has anyone tried?  Noticing this for ntpd, created concern of possible issue(s) for gpsd as it fails on the libpthread requirement.  The configure stanza and resultant output looks something like:

 

./configure \

    --disable-dependency-tracking --disable-local-libopts \

    --disable-all-clocks --disable-parse-clocks \

    --enable-ATOM --enable-pps --enable-SHM --enable-NMEA --enable-LOCAL-CLOCK \

    --with-yielding-select=yes --enable-linuxcaps \

    --with-lineeditlibs=edit \

    --without-ntpsnmpd \

    --enable-thread-support --with-threads \

    --with-crypto

 

<skipping vast output for brevity>

checking for pthread_create in default libraries... no

checking for pthread link with -kthread... no

checking for pthread link with -pthread... no

checking for pthread link with -pthreads... no

checking for pthread link with -mthreads... no

checking for pthread link with -thread... no

checking for pthread link with -lpthread -lmach -lexc -lc_r... no

checking for pthread link with -lpthread -lmach -lexc... no

checking for pthread link with -lpthread -Wl,-woff,85... no

checking for pthread link with -lpthread... no

checking for pthread link with -lc_r... no

checking for pthread link with -threads... no

checking for pthread link with -lpthread -lmach -lexc -lc_r... no

checking for pthread link with -lpthread -lmach -lexc... no

checking for pthread link with -lpthread -lexc... no

checking for pthread link with -lpthread... no

configure: ol_link_threads: <no> ol_link_pthreads <>

configure: error: could not locate usable POSIX Threads

 

Anyone happen to run into this on a PI4?  ntp compiles clean on PI3 (using exact same configure stanza).  Granted, gpsd runs on PI4 (seemingly without issue from apt installed variant), but given libpthread (eg: POSIX threads) would be used by both…. Wondering if there could be any possible subtle issue(s) if gpsd relies on the any of the same library functions.  One should note that the shared object libpthread is present.

 

Can’t help but think that there’s something ?else? missing as both the PI3 and the PI4 are Raspbian lite/buster – the only delta is that the PI3 was a much earlier install that has seen more updates/upgrades (minimum of monthly “apt-get update && apt-upgrade && sync && reboot” – so to speak).  Both have same installed packages, at least for all required functionality.

 

Thanks! 


reply via email to

[Prev in Thread] Current Thread [Next in Thread]