jpilot@lists.jpilot.org

General support, questions, patches for J-Pilot.

View all threads

Jpilot on MacPorts

AW
Alan Wehmann
Sun, Dec 14, 2025 3:40 PM

I had jpilot working on my Mac Book Air 2024 (Silicon), with some inconsequential error messages that didn’t keep it from satisfying my needs.  I then tried having MacPorts build a new version.  It didn’t build.  Anyone interested in the log files can look at this Google Drive folder https://drive.google.com/drive/folders/1AlT_2wqyiIhY1kuk-bJVzfL4StIG05xi?usp=drive_link.  At this URL https://trac.macports.org/search?q=jpilot&noquickjump=1&portsummarysearch=on there is evidence that the jpilot port on MacPorts is no longer being maintained.  Is there any likelihood that someone with the right expertise would fix it?

In the meantime I’m going to see if I can resurrect the jpilot version that I had working, from my backup file for the computer.

I had jpilot working on my Mac Book Air 2024 (Silicon), with some inconsequential error messages that didn’t keep it from satisfying my needs. I then tried having MacPorts build a new version. It didn’t build. Anyone interested in the log files can look at this Google Drive folder <https://drive.google.com/drive/folders/1AlT_2wqyiIhY1kuk-bJVzfL4StIG05xi?usp=drive_link>. At this URL <https://trac.macports.org/search?q=jpilot&noquickjump=1&portsummarysearch=on> there is evidence that the jpilot port on MacPorts is no longer being maintained. Is there any likelihood that someone with the right expertise would fix it? In the meantime I’m going to see if I can resurrect the jpilot version that I had working, from my backup file for the computer.
UZ
Ulf Zibis
Sun, Dec 14, 2025 7:44 PM

Am 14.12.25 um 16:40 schrieb Alan Wehmann:

I had jpilot working on my Mac Book Air 2024 (Silicon), with some inconsequential error messages that didn’t keep it from satisfying my needs.  I then tried having MacPorts build a new version.  It didn’t build.

You may try version 2.0.2 of JPilot instead 1.8.2.

Am 14.12.25 um 16:40 schrieb Alan Wehmann: > I had jpilot working on my Mac Book Air 2024 (Silicon), with some inconsequential error messages that didn’t keep it from satisfying my needs. I then tried having MacPorts build a new version. It didn’t build. You may try version 2.0.2 of JPilot instead 1.8.2.
EK
Elmar Klausmeier
Mon, Dec 15, 2025 11:35 AM

The main culprit seems to be this:

:info:configure checking pilot-link version... configure: error:
pilot-link header pi-version.h not found

I.e., you lack pilot-link.

Regardless of the version of J-Pilot, 1.8 or 2.0, for the compilation of
J-Pilot you need pilot-link.

I know nothing about Mac and packages, but can you check whether there is
any pilot-link package you can use?

On Sun, Dec 14, 2025 at 8:45 PM Ulf Zibis Ulf.Zibis@cosoco.de wrote:

Am 14.12.25 um 16:40 schrieb Alan Wehmann:

I had jpilot working on my Mac Book Air 2024 (Silicon), with some

inconsequential error messages that didn’t keep it from satisfying my
needs.  I then tried having MacPorts build a new version.  It didn’t build.
You may try version 2.0.2 of JPilot instead 1.8.2.


Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org

The main culprit seems to be this: :info:configure checking pilot-link version... configure: error: pilot-link header pi-version.h not found I.e., you lack pilot-link. Regardless of the version of J-Pilot, 1.8 or 2.0, for the compilation of J-Pilot you need pilot-link. I know nothing about Mac and packages, but can you check whether there is any pilot-link package you can use? On Sun, Dec 14, 2025 at 8:45 PM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: > > Am 14.12.25 um 16:40 schrieb Alan Wehmann: > > I had jpilot working on my Mac Book Air 2024 (Silicon), with some > inconsequential error messages that didn’t keep it from satisfying my > needs. I then tried having MacPorts build a new version. It didn’t build. > You may try version 2.0.2 of JPilot instead 1.8.2. > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org >
AW
Alan Wehmann
Mon, Dec 15, 2025 4:24 PM

Thanks, Elmer, for your investigation.  Below I add more detail to what I had done.

I did have pilot-link installed.  I had used it to transfer the memo database file from my Palm Tungsten E2, to my Mac Book Air 2024 (which has the M3 silicon processor).  I then had used my working version of jpilot 1.8.2 to view memos in the memo database and I had copied one of the memos to a text file on the Mac computer.  I even re-installed pilot-link from Macports.

My working version of jpilot 1.8.2 was complaining about a missing crypto library when first loaded, so I thought of using Macports to reinstall jpilot.  That didn’t work, but it installed new versions of the libraries that jpilot needs (the new libraries are meant for the M3 processor, instead of the older Intel processor that Macs used to use).

I also saw that “pi-version.h” was present in /opt/local/include, while attempting the Macports install.  I looked some at the log files to see what config was doing, but didn’t understand what was the problem.

I restored jpilot 1.8.2 and its desired libraries from my backup file and it is now working again, as before.  This is probably working in compatibility mode, using code for an Intel Mac.

I’ll try finding the crypto library that jpilot wants, on a backup file for my older Intel Mac & see if that gets rid of the complaint that jpilot makes when it starts up (on my M3 processor Mac).

In the future, when I have a lot of spare time, I might attempt to again build from Macports, or do an unassisted build on my own.

On Dec 15, 2025, at 5:35 AM, Elmar Klausmeier elmar.klausmeier@gmail.com wrote:

The main culprit seems to be this:

:info:configure checking pilot-link version... configure: error:
pilot-link header pi-version.h not found

I.e., you lack pilot-link.

Regardless of the version of J-Pilot, 1.8 or 2.0, for the compilation of
J-Pilot you need pilot-link.

I know nothing about Mac and packages, but can you check whether there is
any pilot-link package you can use?

On Sun, Dec 14, 2025 at 8:45 PM Ulf Zibis Ulf.Zibis@cosoco.de wrote:

Am 14.12.25 um 16:40 schrieb Alan Wehmann:

I had jpilot working on my Mac Book Air 2024 (Silicon), with some

inconsequential error messages that didn’t keep it from satisfying my
needs.  I then tried having MacPorts build a new version.  It didn’t build.
You may try version 2.0.2 of JPilot instead 1.8.2.


Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org


Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org

Thanks, Elmer, for your investigation. Below I add more detail to what I had done. I did have pilot-link installed. I had used it to transfer the memo database file from my Palm Tungsten E2, to my Mac Book Air 2024 (which has the M3 silicon processor). I then had used my working version of jpilot 1.8.2 to view memos in the memo database and I had copied one of the memos to a text file on the Mac computer. I even re-installed pilot-link from Macports. My working version of jpilot 1.8.2 was complaining about a missing crypto library when first loaded, so I thought of using Macports to reinstall jpilot. That didn’t work, but it installed new versions of the libraries that jpilot needs (the new libraries are meant for the M3 processor, instead of the older Intel processor that Macs used to use). I also saw that “pi-version.h” was present in /opt/local/include, while attempting the Macports install. I looked some at the log files to see what config was doing, but didn’t understand what was the problem. I restored jpilot 1.8.2 and its desired libraries from my backup file and it is now working again, as before. This is probably working in compatibility mode, using code for an Intel Mac. I’ll try finding the crypto library that jpilot wants, on a backup file for my older Intel Mac & see if that gets rid of the complaint that jpilot makes when it starts up (on my M3 processor Mac). In the future, when I have a lot of spare time, I might attempt to again build from Macports, or do an unassisted build on my own. > On Dec 15, 2025, at 5:35 AM, Elmar Klausmeier <elmar.klausmeier@gmail.com> wrote: > > The main culprit seems to be this: > > :info:configure checking pilot-link version... configure: error: > pilot-link header pi-version.h not found > > I.e., you lack pilot-link. > > Regardless of the version of J-Pilot, 1.8 or 2.0, for the compilation of > J-Pilot you need pilot-link. > > I know nothing about Mac and packages, but can you check whether there is > any pilot-link package you can use? > > On Sun, Dec 14, 2025 at 8:45 PM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: > >> >> Am 14.12.25 um 16:40 schrieb Alan Wehmann: >>> I had jpilot working on my Mac Book Air 2024 (Silicon), with some >> inconsequential error messages that didn’t keep it from satisfying my >> needs. I then tried having MacPorts build a new version. It didn’t build. >> You may try version 2.0.2 of JPilot instead 1.8.2. >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >> > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org