FreeBSD Port Make process stops at pinentry-1.1.1 #86

Basic information

TDE version: R14.0.10
Distribution: FreeBSD 13.0-RELEASE
Hardware: amd64

Unsure what severity level to call this.

Description

After running "make install clean" to build and install the R14.0.10 port for FreeBSD, the process goes well until gmake leaves the directory /dependencies/pinentry-tqt/work/pinentry-1.1.1.

I've tried this last month and it stopped at the same place, now I removed the desktop environment and login manager I was using to install TDE. (I miss it!)

It also said to set MAKE_JOBS_UNSAFE=yes and attempt to rebuild. I did this and ran "make reinstall clean". Still stops and gives the same output at pinentry.

Steps to reproduce

Run make install clean inside of the freebsd make folder
Once it reaches pinentry, the compilation should stop and give Error code 1.

Screenshots

Attached a picture (sorry that I didnt have a proper screenshot utility, as I removed my entire interface). Note that I have the port inside of my home Projects folder (home/hunter/Projects/freebsd).

## Basic information - TDE version: R14.0.10 - Distribution: FreeBSD 13.0-RELEASE - Hardware: amd64 Unsure what severity level to call this. ## Description After running "make install clean" to build and install the R14.0.10 port for FreeBSD, the process goes well until gmake leaves the directory /dependencies/pinentry-tqt/work/pinentry-1.1.1. I've tried this last month and it stopped at the same place, now I removed the desktop environment and login manager I was using to install TDE. (I miss it!) It also said to set MAKE_JOBS_UNSAFE=yes and attempt to rebuild. I did this and ran "make reinstall clean". Still stops and gives the same output at pinentry. ## Steps to reproduce 1. Run make install clean inside of the freebsd make folder 2. Once it reaches pinentry, the compilation should stop and give Error code 1. ## Screenshots Attached a picture (sorry that I didnt have a proper screenshot utility, as I removed my entire interface). Note that I have the port inside of my home Projects folder (home/hunter/Projects/freebsd).

20210604_121617.jpg

2.3 MiB

I do not have FreeBSD, but IMO you should have curses and TTY enabled (based on your fallback =yes)
IMO it is sufficient to have one fall back though - I set up TTY in debian

./configure --disable-libsecret --enable-maintainer-mode \
                --enable-pinentry-tty \
                --disable-pinentry-curses \
                --disable-fallback-curses \
                --disable-pinentry-gnome3 \
                --disable-pinentry-gtk2 \
                --disable-pinentry-qt5 \
                --disable-pinentry-qt \
                --enable-pinentry-tqt

Let me know if it helps. I am not sure who is taking care of the FreeBSD - I guess Slavek.

I do not have FreeBSD, but IMO you should have curses and TTY enabled (based on your fallback =yes) IMO it is sufficient to have one fall back though - I set up TTY in debian ``` ./configure --disable-libsecret --enable-maintainer-mode \ --enable-pinentry-tty \ --disable-pinentry-curses \ --disable-fallback-curses \ --disable-pinentry-gnome3 \ --disable-pinentry-gtk2 \ --disable-pinentry-qt5 \ --disable-pinentry-qt \ --enable-pinentry-tqt ``` Let me know if it helps. I am not sure who is taking care of the FreeBSD - I guess Slavek.

You cleaned the work directory in pinentry before building?

You cleaned the `work` directory in pinentry before building?

You cleaned the work directory in pinentry before building?

No. Its still there with its contents.

> You cleaned the `work` directory in pinentry before building? No. Its still there with its contents.

Update -- I ran make MAKE_JOBS_UNSAFE=yes install clean, since the variable wasn't set, and now its showing that there is a version mismatch with automake. Automake 1.16.3 is being used, but it says the AM_INIT_AUTOMAKE comes from 1.16.2.

I do not have FreeBSD, but IMO you should have curses and TTY enabled (based on your fallback =yes)
IMO it is sufficient to have one fall back though - I set up TTY in debian
./configure --disable-libsecret --enable-maintainer-mode \
                --enable-pinentry-tty \
                --disable-pinentry-curses \
                --disable-fallback-curses \
                --disable-pinentry-gnome3 \
                --disable-pinentry-gtk2 \
                --disable-pinentry-qt5 \
                --disable-pinentry-qt \
                --enable-pinentry-tqt
Let me know if it helps. I am not sure who is taking care of the FreeBSD - I guess Slavek.

Sorry it took a while, but I didn't understand how to use this until just a few minutes ago. I ran this (using with MAKE="gmake") and then continued the make process. It seemed to make it along further now, but stopped after "pkg-static" was unable to access ../pinentry-tqt/work/stage/usr/local/bin/pinentry-tqt.

> I do not have FreeBSD, but IMO you should have curses and TTY enabled (based on your fallback =yes) > IMO it is sufficient to have one fall back though - I set up TTY in debian > > ``` > ./configure --disable-libsecret --enable-maintainer-mode \ > --enable-pinentry-tty \ > --disable-pinentry-curses \ > --disable-fallback-curses \ > --disable-pinentry-gnome3 \ > --disable-pinentry-gtk2 \ > --disable-pinentry-qt5 \ > --disable-pinentry-qt \ > --enable-pinentry-tqt > ``` > > Let me know if it helps. I am not sure who is taking care of the FreeBSD - I guess Slavek. > > Sorry it took a while, but I didn't understand how to use this until just a few minutes ago. I ran this (using with MAKE="gmake") and then continued the make process. It seemed to make it along further now, but stopped after "pkg-static" was unable to access ../pinentry-tqt/work/stage/usr/local/bin/pinentry-tqt.

You can try to remove an existing work directory and start the build again.

You can try to remove an existing `work` directory and start the build again.

Good morning. I tried to remove the work directory for pinentry-tqt last night, but then it spit out that it couldn't find it and stopped the process right there.

I had quite a headache last night trying to get this to work with the help of somebody else (we had been trying at it for hours) so I decided to come back this morning. I'm using fluxbox temporarily to make communication a bit easier. Thanks for your help and support :)

I downloaded the freebsd port again (I clone the whole r14.0.x branch since I don't know how to get the freebsd directory specifically) since I made a few changes in my attempts to fix it (without backing up the original), so I'm backing it up this time.

If I had to suggest anything, it would be a readme or documentation of some sort for this port because I'm not quite sure if I was doing it the intended way. The person helping me thought gmake (Linux make) should be used instead of our make, but it gives an error (Makefile:8: *** missing separator. Stop.) if I try to do this.

I was treating this like a typical FreeBSD port (where you cd into the directory and make install clean), but let me know if this isn't the intended way since doing this resulted in the snag I came across. Also, are any of the packages included optional? I would like to avoid pulseaudio if possible since we have OSS out of the box on FreeBSD.

After cloning and running make deinstall and then make install again, I get the error mkdir: /usr/ports/misc/findutils/work: Permission denied. Do I need to run this as root? (I did the last attempt as well, but the guy helping me suggested I didn't and typically a port asks for root permission without running it with doas/sudo).

Good morning. I tried to remove the work directory for pinentry-tqt last night, but then it spit out that it couldn't find it and stopped the process right there. I had quite a headache last night trying to get this to work with the help of somebody else (we had been trying at it for hours) so I decided to come back this morning. I'm using fluxbox temporarily to make communication a bit easier. Thanks for your help and support :) I downloaded the freebsd port again (I clone the whole r14.0.x branch since I don't know how to get the freebsd directory specifically) since I made a few changes in my attempts to fix it (without backing up the original), so I'm backing it up this time. If I had to suggest anything, it would be a readme or documentation of some sort for this port because I'm not quite sure if I was doing it the intended way. The person helping me thought `gmake` (Linux make) should be used instead of our `make`, but it gives an error (`Makefile:8: *** missing separator. Stop.`) if I try to do this. I was treating this like a typical FreeBSD port (where you cd into the directory and `make install clean`), but let me know if this isn't the intended way since doing this resulted in the snag I came across. Also, are any of the packages included optional? I would like to avoid pulseaudio if possible since we have OSS out of the box on FreeBSD. After cloning and running ``make deinstall`` and then ``make install`` again, I get the error ``mkdir: /usr/ports/misc/findutils/work: Permission denied``. Do I need to run this as root? (I did the last attempt as well, but the guy helping me suggested I didn't and typically a port asks for root permission without running it with doas/sudo).

Uninstall all trinity stuff, delete the folder, clone it again. go to freebsd/dependencies, enter each folder in the same order you see in the Makefile, "make install clean", and you should be fine. At least that worked for me, as I ran into the same issue.

I finally installed it thanks to the help of all of you. Thank you very much :)

Now, as far as this issue goes, I think it's safe to say something's wrong (it's still possible to install, just not with the make files)..

I finally installed it thanks to the help of all of you. Thank you very much :) Now, as far as this issue goes, I think it's safe to say something's wrong (it's still possible to install, just not with the make files)..

It is important to understand what kind of issue you are facing.
If it is pinentry related, we have to report to the developers of pinentry.
If it is TDE related we have to find the solution and push it upstream.

It is important to understand what kind of issue you are facing. If it is pinentry related, we have to report to the developers of pinentry. If it is TDE related we have to find the solution and push it upstream.

It is important to understand what kind of issue you are facing.
If it is pinentry related, we have to report to the developers of pinentry.
If it is TDE related we have to find the solution and push it upstream.

Since I'm not that smart in this topic (especially since I'm merely a user and also because I faced more issues in the make process), I'm going to agree with Nik that it's an issue with the build system. I noticed that I didn't use gmake at all (since I was using FreeBSD's make install clean), whereas in the above picture it shows that gmake was running right before the error.

I wish I had started the process in a graphical environment so I could copy and paste the output (which may be insightful) instead of taking a picture. Anything I can do to help.

> It is important to understand what kind of issue you are facing. > If it is pinentry related, we have to report to the developers of pinentry. > If it is TDE related we have to find the solution and push it upstream. Since I'm not that smart in this topic (especially since I'm merely a user and also because I faced more issues in the make process), I'm going to agree with Nik that it's an issue with the build system. I noticed that I didn't use gmake at all (since I was using FreeBSD's *make install clean*), whereas in the above picture it shows that gmake was running right before the error. I wish I had started the process in a graphical environment so I could copy and paste the output (which may be insightful) instead of taking a picture. Anything I can do to help.

@hunter0one,
so is it a user error and we can close this issue, or something needs to improve?
Because also @Dr_Nikolaus_Klepp mentioned having troubles with that, I just wonder if this needs improvment in some way and if so, where.

@hunter0one, so is it a user error and we can close this issue, or something needs to improve? Because also @Dr_Nikolaus_Klepp mentioned having troubles with that, I just wonder if this needs improvment in some way and if so, where.

For me, there seems to be something that could be fixed. But for the time being, it is not clear where the problem is.

In my case, I always run the buildings of individual directories, because I test the build of individual preliminary updates. Therefore, building everything using meta-makefiles is not useful for me. Maybe that's why I didn't observe the mentioned problem.

For me, there seems to be *something* that could be fixed. But for the time being, it is not clear where the problem is. In my case, I always run the buildings of individual directories, because I test the build of individual preliminary updates. Therefore, building everything using meta-makefiles is not useful for me. Maybe that's why I didn't observe the mentioned problem.

@deloptes It's not a user error, as I was building it the intended way (make install clean in the r14.0.x/freebsd directory) like a typical FreeBSD port. I believe @Dr_Nikolaus_Klepp did as well.

I can't answer whether it's a problem with pinentry or the build process specifically, all I know is manually entering each package directory and running make install clean there worked (according to the order that the meta-makefile intended), but it didn't for the actual meta-makefile that automates the process.

Edit: Forgot to mention that I also skipped pinentry-tqt when I manually made each package.

@deloptes It's not a user error, as I was building it the intended way (*make install clean* in the r14.0.x/freebsd directory) like a typical FreeBSD port. I believe @Dr_Nikolaus_Klepp did as well. I can't answer whether it's a problem with pinentry or the build process specifically, all I know is manually entering each package directory and running *make install clean* there worked (according to the order that the meta-makefile intended), but it didn't for the actual meta-makefile that automates the process. Edit: Forgot to mention that I also skipped pinentry-tqt when I manually made each package.

This definitely is the pinentry port problem. When I tried in the Makefile in the dependencies directory to put all other SUBDIR += ... into comment and leave only pinentry-tqt, starting make reinstall clean fails, while starting the same in the pinentry-tqt directory (after removing work directory) is successful.

This definitely is the pinentry port problem. When I tried in the Makefile in the dependencies directory to put all other `SUBDIR += ...` into comment and leave only pinentry-tqt, starting `make reinstall clean` fails, while starting the same in the pinentry-tqt directory (after removing `work` directory) is successful.

This definitely is the pinentry port problem. When I tried in the Makefile in the dependencies directory to put all other SUBDIR += ... into comment and leave only pinentry-tqt, starting make reinstall clean fails, while starting the same in the pinentry-tqt directory (after removing work directory) is successful.

@SlavekB should we report this upstream?

> This definitely is the pinentry port problem. When I tried in the Makefile in the dependencies directory to put all other `SUBDIR += ...` into comment and leave only pinentry-tqt, starting `make reinstall clean` fails, while starting the same in the pinentry-tqt directory (after removing `work` directory) is successful. @SlavekB should we report this upstream?

This definitely is the pinentry port problem. When I tried in the Makefile in the dependencies directory to put all other SUBDIR += ... into comment and leave only pinentry-tqt, starting make reinstall clean fails, while starting the same in the pinentry-tqt directory (after removing work directory) is successful.

@SlavekB should we report this upstream?

For now, I do not know if it is a thing to solve in the Makefile in FreeBSD port – it is derived from the official FreeBSD port, or whether it is a problem in pinentry upstream.

> > This definitely is the pinentry port problem. When I tried in the Makefile in the dependencies directory to put all other `SUBDIR += ...` into comment and leave only pinentry-tqt, starting `make reinstall clean` fails, while starting the same in the pinentry-tqt directory (after removing `work` directory) is successful. > > @SlavekB should we report this upstream? For now, I do not know if it is a thing to solve in the Makefile in FreeBSD port – it is derived from the official FreeBSD port, or whether it is a problem in pinentry upstream.

To me it sounds reasonable. May be it is something related to TQT and the upstream guys did not notice, because no on uses TDE there.

To me it sounds reasonable. May be it is something related to TQT and the upstream guys did not notice, because no on uses TDE there.

For me, it seems that it is not related to TQT. Compared to correct build, the difference is that there will be a repeatedly configuration that forgets what is the source code version. First configuration lists:

configure:

        Pinentry v1.1.1 has been configured as follows:

        Revision:  c6202b2  (50720)
        Platform:  amd64-portbld-freebsd13.0

The second unsolicited configuration lists:

configure:

        Pinentry v1.1.1 has been configured as follows:

        Revision:    ()
        Platform:  amd64-portbld-freebsd13.0

At the same time, it is evident that the second configuration is trying to find out the revision by git calls, which is nonsense if the source tarball is used:

gmake[2]: Entering directory '/usr/ports/x11/trinity/dependencies/pinentry-tqt/work/pinentry-1.1.1'
CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /usr/ports/x11/trinity/dependencies/pinentry-tqt/work/pinentry-1.1.1/build-aux/missing autoconf
 cd . && /bin/sh /usr/ports/x11/trinity/dependencies/pinentry-tqt/work/pinentry-1.1.1/build-aux/missing automake-1.16 --gnu Makefile
sh: arithmetic expression: expecting EOF: "0x"
sh: git: not found
/bin/sh ./config.status --recheck
sh: arithmetic expression: expecting EOF: "0x"
sh: git: not found

> To me it sounds reasonable. May be it is something related to TQT and the upstream guys did not notice, because no on uses TDE there. For me, it seems that it is not related to TQT. Compared to *correct* build, the difference is that there will be a repeatedly configuration that *forgets* what is the source code version. First configuration lists: ``` configure: Pinentry v1.1.1 has been configured as follows: Revision: c6202b2 (50720) Platform: amd64-portbld-freebsd13.0 ``` The second *unsolicited* configuration lists: ``` configure: Pinentry v1.1.1 has been configured as follows: Revision: () Platform: amd64-portbld-freebsd13.0 ``` At the same time, it is evident that the second configuration is trying to find out the revision by git calls, which is nonsense if the source tarball is used: ``` gmake[2]: Entering directory '/usr/ports/x11/trinity/dependencies/pinentry-tqt/work/pinentry-1.1.1' CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh /usr/ports/x11/trinity/dependencies/pinentry-tqt/work/pinentry-1.1.1/build-aux/missing autoconf cd . && /bin/sh /usr/ports/x11/trinity/dependencies/pinentry-tqt/work/pinentry-1.1.1/build-aux/missing automake-1.16 --gnu Makefile sh: arithmetic expression: expecting EOF: "0x" sh: git: not found /bin/sh ./config.status --recheck sh: arithmetic expression: expecting EOF: "0x" sh: git: not found ```

I'll leave this open since it's still unsolved AFAIK, but I can close it if it needs to be. Let me know if I can do anything to help!

I sent an email to the mailing list but I think I've found more insight on the problem. It seems to be related with libgpg-error in some way.

configure:
***
*** You need libgpg-error to build this program.
**  This library is for example available at
***   ftp://ftp.gnupg.org/gcrypt/libgpg-error
*** (at least version 1.16 is required.)
***
configure: error: 
***
*** Required libraries not found. Please consult the above messages
*** and install them before running configure again.
***
gmake[3]: *** [Makefile:452: config.status] Error 1
gmake[3]: Leaving directory '/usr/home/hunter/tde-packaging/freebsd/dependencies/pinentry-tqt/work/pinentry-1.1.1'
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1

I sent an email to the mailing list but I think I've found more insight on the problem. It seems to be related with libgpg-error in some way. ``` configure: *** *** You need libgpg-error to build this program. ** This library is for example available at *** ftp://ftp.gnupg.org/gcrypt/libgpg-error *** (at least version 1.16 is required.) *** configure: error: *** *** Required libraries not found. Please consult the above messages *** and install them before running configure again. *** gmake[3]: *** [Makefile:452: config.status] Error 1 gmake[3]: Leaving directory '/usr/home/hunter/tde-packaging/freebsd/dependencies/pinentry-tqt/work/pinentry-1.1.1' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 ```

I believe that the problem appears because of the fact that automake configuration is performed repeatedly, and repeat generation causes a strange state that subsequently fails. There it doesn't seem to be missing some dependencies, but that the repeat generation breaks it.

To be honest, I wish I knew more about the FreeBSD port-building process. Even as a native FBSD user who also uses the ports collection quite a bit, I've never really tinkered with makefiles. I've talked to a few people in the FreeBSD Matrix room about getting help with this port (and maybe even get it included as multiple ports)

Perhaps we can study how KDE3 was structured in the Ports Collection. https://www.freshports.org/x11/kde3/

And here is just a search query for everything KDE3.

To be honest, I wish I knew more about the FreeBSD port-building process. Even as a native FBSD user who also uses the ports collection quite a bit, I've never really tinkered with makefiles. I've talked to a few people in the FreeBSD Matrix room about getting help with this port (and maybe even get it included as multiple ports) Perhaps we can study how KDE3 was structured in the Ports Collection. https://www.freshports.org/x11/kde3/ [And here is just a search query for everything KDE3.](https://www.freshports.org/search.php?stype=name&method=match&query=kde3&num=10&deleted=includedeleted&orderby=category&orderbyupdown=asc&search=Search&format=html&branch=head)

It seems that during the preparation of ports for R14.1.0, I managed to solve the problem of building a pinentry-tqt within the tree. You can look at #214.

It seems that during the preparation of ports for R14.1.0, I managed to solve the problem of building a `pinentry-tqt` within the tree. You can look at #214.

Labels Milestones

FreeBSD Port Make process stops at pinentry-1.1.1 #86

Basic information

Description

Steps to reproduce

Screenshots