Package Details: jpilot 2.0.3-1

Git Clone URL: https://aur.archlinux.org/jpilot.git (read-only, click to copy)
Package Base: jpilot
Description: A desktop organizer application for the Palm Pilot
Upstream URL: https://github.com/juddmon/jpilot/
Keywords: calendar diary note
Licenses: GPL2
Submitter: ilpianista
Maintainer: eklausmeier (edh)
Last Packager: eklausmeier
Votes: 23
Popularity: 0.000000
First Submitted: 2010-11-13 15:07 (UTC)
Last Updated: 2025-03-06 08:01 (UTC)

Latest Comments

1 2 3 4 Next › Last »

eklausmeier commented on 2023-05-11 16:19 (UTC) (edited on 2023-05-11 16:25 (UTC) by eklausmeier)

Sorry to hear this.

Looking at your output I would estimate that pilot-link is to blame. The assertion is thrown here: dlp.c

To further confirm that this is a pilot-link problem, try to just use the pilot-link command-line tools. In particular try

pilot-read-todos

with proper arguments.

Another note, not directly related to your assertion problem: When my Palm devices still worked, I never hot-synced via root user. I store my Palm data in SQLite, see Accessing J-Pilot Data From Mobile And Web and SQLite Storage for J-Pilot.

jpfox commented on 2023-05-11 13:36 (UTC) (edited on 2023-05-11 13:40 (UTC) by jpfox)

Tnx @eklausmeier, since the last update, jpilot compiles correctly.

But, I encounter an ASSERT error on "user" installation (when sending name and numeric ID on a reinitialized device).

I use pilot-link-git for connection.

sudo jpilot -d gives this detail:

UPTODATE 2023 5 11 15 20
alarms_find_next()
get_days_calendar_events()
Entering jp_read_DB_files: DatebookDB
Leaving jp_read_DB_files
Leaving get_days_calendar_events()
alarms_write_file()
jp_pref_write_rc_file()
cb_check_version
jp_pref_write_rc_file()
jp_pref_write_rc_file()
user is root
user id is 813019180
setting PILOTRATE=[115200]
pref port=[usb:]
num_backups=2
lock succeeded
forking sync process
old user is 
old user id is 0
jp_pref_write_rc_file()
****************************************
 Syncing on device usb:
 Press the HotSync button now
****************************************
command=100 [****************************************]
command=100 [ Syncing on device usb: ]
command=100 [ Press the HotSync button now ]
command=100 [****************************************]
file dlp.c: line 836: assertion failed: (t != NULL)caught signal SIGCHLD

Connection seems fine because the Palm beep and display "Identification" but the connection is lost as soon as the assertion occurs.

I don't understand what happens :-(

jpfox

eklausmeier commented on 2021-11-06 12:16 (UTC)

Thanks Omar007! Corrected in new PKGBUILD.

Omar007 commented on 2021-11-06 11:29 (UTC) (edited on 2021-11-06 11:29 (UTC) by Omar007) 

...
todo_gui.c:31:10: fatal error: slcurses.h: No such file or directory
   31 | #include <slcurses.h>
      |          ^~~~~~~~~~~~
compilation terminated.
make[2]: *** [Makefile:867: todo_gui.o] Error 1
make[2]: *** Waiting for unfinished jobs....

Looks like the 'slang' dependency is missing and at the very least required for build.

eklausmeier commented on 2021-11-01 16:43 (UTC)

As multiple people have asked for the new version, so here it is.

But beware that the new v2.0.1 version looks and feels different!

I copy some helpful comments from the J-Pilot mailing list:

It's using css rather than rc files in version 2.

If you copy /usr/share/jpilot/jpilotcss.default to ~/.jpilot, it will use that file, and you should be able to tweak the settings. I thought it was installing it already to the home directory, but I missed something.

At the bottom of the file there is the following lines:

  • { font-family: Arial Black, sans-serif; font-size: 10pt; }

Change "font-family: Arial Black, sans-serif;" to "font-family: Arial, sans-serif;", and the font won't appear to be bolded everywhere.

Thanks, David Malia

Barry2 commented on 2021-09-18 01:58 (UTC) (edited on 2021-09-18 01:59 (UTC) by Barry2)

Hi eklausmeier,

Thank you very much for verifying that pilot-link still compiles. I will assume for now that the problem lies in my Manjaro setup, and I will continue to troubleshoot that with help from people using and maintaining Manjaro.

Also, thank you very much for maintaining jpilot. While Palm devices are obviously not the latest technology, they did some things better than their successors have done. And even for people who've moved on, it's useful to have the ability to go back for purposes such as data retrieval.

Best wishes, Barry

eklausmeier commented on 2021-09-17 23:12 (UTC)

Hello Barry2,

I checked, whether I can compile pilot-link 0.12.5-5 with makepkg: Yes, works without any hickups.

According your log-output it seems like a problem with compiling pilot-link. Just for reference I add output of part of the pilot-link compilation. I clipped some boring parts (marked with: ...)

Regards,

Elmar.

klm@ryzen /tmp/T/pilot-link: makepkg
==> Making package: pilot-link 0.12.5-2 (Sat 18 Sep 2021 12:55:30 AM CEST)
==> Checking runtime dependencies...
==> Making package: pilot-link 0.12.5-2 (Sat 18 Sep 2021 12:55:30 AM CEST)                                                                               [1461/1964]
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading pilot-link-0.12.5.tar.bz2...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   285  100   285    0     0    187      0  0:00:01  0:00:01 --:--:--   187
100 1541k  100 1541k    0     0   865k      0  0:00:01  0:00:01 --:--:--  865k
  -> Found pilot-link-png14.patch
  -> Found config.guess
  -> Found config.sub
==> Validating source files with md5sums...
    pilot-link-0.12.5.tar.bz2 ... Passed
    pilot-link-png14.patch ... Passed
    config.guess ... Passed
    config.sub ... Passed
==> Extracting sources...
  -> Extracting pilot-link-0.12.5.tar.bz2 with bsdtar
==> Starting build()...
patching file src/pilot-read-notepad.c
patching file src/pilot-read-palmpix.c
patching file src/pilot-read-screenshot.c
patching file src/pilot-read-veo.c
checking whether to enable maintainer-specific portions of Makefiles... no
checking build system type... x86_64-pc-linux-gnu
checking host system type... x86_64-pc-linux-gnu
checking target system type... x86_64-pc-linux-gnu
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for g77... no
checking dependency style of gcc... gcc3                                                                                                                 [1418/1964]
checking for g77... no
checking for g77-3.2... no
checking for g77-3.3... no
checking for fl32... no
checking for f77... no
checking for fort77... no
checking for xlf... no
checking for f90... no
checking for xlf90... no
checking whether we are using the GNU Fortran 77 compiler... no
checking whether  accepts -g... no
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /bin/ld
checking if the linker (/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /bin/nm -B
checking the name lister (/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /bin/nm -B output from gcc object... ok
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for g77... no
checking for xlf... no
checking for g77... no                                                                                                                                   [1375/1964]
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... (cached) no
checking whether gfortran accepts -g... (cached) no
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gfortran option to produce PIC...
checking if gfortran static flag  works... yes
checking if gfortran supports -c -o file.o... yes
checking if gfortran supports -c -o file.o... (cached) yes
checking whether the gfortran linker (/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for bison... bison -y
checking for ANSI C header files... (cached) yes
checking for an ANSI C-conforming const... yes
. . .
  Options detected/selected
  -------------------------.
  pilot-link version...... : 0.12.5
  libpisock version....... : 9.0.2
  libpisync version....... : 1.0.3
  Build for host.......... : x86_64-pc-linux-gnu
  Extra Warnings.......... : no
  Direct USB support...... : yes, libusb
  BlueZ support........... : yes
  Thread-safe libpisock... : no
  ElectricFence checks.... : no
  CPPFLAGS................ : -D_FORTIFY_SOURCE=2
  CFLAGS.................. : -march=native -mtune=generic -O2 -pipe -fstack-protector-strong -fno-plt

  Userland Tools
  -------------------------.
  Build userland tools.... : yes
  Support for popt........ : yes (system)
  Readline support........ : yes
  PNG support............. : yes

  Internal Language Support
  -------------------------.
  Iconv support........... : yes

  External Language Support
  -------------------------.
  TCL support............. : false
  Java support............ : false
  Python support.......... : false
  Perl support............ : false

make  all-recursive
make[1]: Entering directory '/tmp/T/pilot-link/src/pilot-link-0.12.5'
Making all in popt
make[2]: Entering directory '/tmp/T/pilot-link/src/pilot-link-0.12.5/popt'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/tmp/T/pilot-link/src/pilot-link-0.12.5/popt'
Making all in libpisock
make[2]: Entering directory '/tmp/T/pilot-link/src/pilot-link-0.12.5/libpisock'
/bin/sh ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../include -I../include  -D_FORTIFY_SOURCE=2    -march=native -mtune=gener
ic -O2 -pipe -fstack-protector-strong -fno-plt -MT libpisock_la-bluetooth.lo -MD -MP -MF .deps/libpisock_la-bluetooth.Tpo -c -o libpisock_la-bluetooth.lo `test -f '
bluetooth.c' || echo './'`bluetooth.c
. . .
make[2]: Nothing to be done for 'install-exec-am'.
test -z "/usr/share/aclocal" || /bin/mkdir -p "/tmp/T/pilot-link/pkg/pilot-link/usr/share/aclocal"
test -z "/usr/lib/pkgconfig" || /bin/mkdir -p "/tmp/T/pilot-link/pkg/pilot-link/usr/lib/pkgconfig"
 /bin/install -c -m 644 pilot-link.m4 '/tmp/T/pilot-link/pkg/pilot-link/usr/share/aclocal'
 /bin/install -c -m 644 pilot-link.pc '/tmp/T/pilot-link/pkg/pilot-link/usr/lib/pkgconfig'
make[2]: Leaving directory '/tmp/T/pilot-link/src/pilot-link-0.12.5'
make[1]: Leaving directory '/tmp/T/pilot-link/src/pilot-link-0.12.5'
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Stripping unneeded symbols from binaries and libraries...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "pilot-link"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: pilot-link 0.12.5-2 (Sat 18 Sep 2021 12:55:55 AM CEST)

Barry2 commented on 2021-09-17 18:22 (UTC)

Thanks for the quick reply, eklausmeier. The only dependency missing is pilot-link. Whether I try to build it on its own or as part of jpilot, an error occurs. I could post config.log, but I'm having trouble seeing how to do it nicely on the Markdown page. In the meantime, I can direct you here: https://forum.manjaro.org/t/aur-package-build-aborts/82897.

eklausmeier commented on 2021-09-17 17:21 (UTC)

Hello Barry2,

can you please double-check that the required dependencies have been successfully installed? I.e., gtk2, pilot-link, etc.

Thanks.

Elmar.

Barry2 commented on 2021-09-17 17:01 (UTC) (edited on 2021-09-17 17:11 (UTC) by Barry2)

I'm getting error messages trying to build jpilot in Manjaro:

gcc: error: unrecognized command-line option '-V'

gcc: fatal error: no input files

gcc: error: unrecognized command-line option '-qversion'; did you mean '--version'?

gcc: fatal error: no input files

/usr/bin/ld: cannot find format-security: No such file or directory

collect2: error: ld returned 1 exit status

configure:3648: error: in `/var/tmp/pamac-build-barry/pilot-link/src/pilot-link-0.12.5':

configure:3652: error: C compiler cannot create executables

I have base-devel installed. Also, for what it's worth, I successfully installed jpilot earlier this year in a full Manjaro XFCE installation; I'm trying it now in a minimal Manjaro XFCE installation. So, if nothing seems to have changed in how the AUR in general, or the jpilot package in particular, would work with Manjaro, perhaps my setup is missing something from the full Manjaro XFCE installation.

The steps that bitreactor notes in their 2021-07-12 03:15 comment don't change the results.

Sorry that I haven't been able to format the error messages better.

1 2 3 4 Next › Last »