-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
make[2]: *** No rule to make target ../lib/openat-die.c', needed by
wget2.pot-update'. Stop.
#236
Comments
It appears the problem is the following lines in ./po/Makefile:
The first two entries both exist in multiple locations, and most importantly in ./lib
In contrast, "openat-die.c" only exist in ./gnulib/lib, so "make" cannot find them as instructed by ./po/Makefile, while "os2-spawn.c" is not found anywhere at all.
|
Got it. It appears my running "git submodule update --init" unnecessarily was the source that introduced the "openat-die.c" and "os2-spawn.c" references. Now trying to track down whether "./bootstrap --skip-po" would revert the after-effects of "git submodule update --init". |
Never mind. It wasn't due to "git submodule update --init" or anything I added. The two references, "openat-die.c" and "os2-spawn.c", come in regardless, with only openat-die.c actually becoming present in the ./gnulib directory structure:
|
Apparently the newest commit (pending review?), only on gitlab, introduced "openat-die.c" and "os2-spawn.c": |
The mentioned files are auto-generated/copied from gnulib. Not much we can do but wait until they sorted out issues with the latest changes. In the meantime you possibly should build from tarball as that should come with much less headaches. |
@rockdaboot, yes, that's what I did. BTW, I'm getting |
You need the autoconf-archive package. |
Thanks, installing autoconf-archive indeed gets me past that. Now I run into the following, the same issue I have run into with the latest (last I looked as of 2021-01-09) wget-1.x git source code at https://github.com/mirror/wget. This is strange, because I didn't have this issue when I posted above about the openat-die.c issue:
|
Are you sure you are building from tarball with the commands described in README.md ?
It sounds like you are in some knee-deep shit caused by using tarball and then using ./bootstrap or autoreconf. |
@rockdaboot yes, this occurs on both macOS 10.11 and (an almost fresh install of) 10.14, across multiple reboots, in both third-party iTerm and Apple's Terminal, with or without ccache, and as mentioned above also taking place with https://github.com/mirror/wget too after 2021-01-03 (but didn't start occurring with wget2 until now). The only variance is I have to use "./configure --with-ssl=openssl" because I noticed my latest successful build of wget2 was compiled with libwget that has no TLS support (due to bare "./configure" per the Readme.md, because I have LibreSSL but no GnuTLS installed). I also get these errors with the latest github source (adding "bash ./bootstrap" per Readme.md). If I stop git cloning at one of the earlier commits, for example "commit 22162f8" (Commits on Jan 22, 2021 Update copyright year Darshit Shah Darshit Shah committed 9 days ago 22162f8) or "commit 5a4e3ae" (Commits on Jan 2, 2021 * .travis.yml: Remove unneeded packages for Linux @rockdaboot rockdaboot committed on Jan 2), I now get:
Strangely I didn't have such issue with the github src last I built successfully (with no TLS in libwget apparently), according to my comment above on 2021-1-19 #236 (comment) |
Oh, I once had code in configure.ac to automatically fallback to openssl when gnutls wasn't found. Have to check that again. |
No, this issue is part of
So you are using libressl and not openssl. |
@vollkommenheit Could you try again with the latest master (or latest tarball) ? |
@rockdaboot, yes, I will try both and report back. Last night, I tried against the gitlab source, and was still stopped by the "./malloc/dynarray-skeleton.c" errors. I suppose I didn't see the "ssl_openssl.c" issue because it's further down the line in the compile process?? |
With the gitlab source:
With the latest tarball:
Maybe the issue is the same one(s) raised in these? Tried replacing "xx = gcc" with "g++" or "clang++" or "gcc -lc++", or appending either -stdlib=libc++ or -stdlib=libstdc++ to LDFLAGS, in a few places such as ./libwget/Makefile, but no dice. |
It's possibly the missing explicit include of |
Now "make" errors out a bit differently:
Not sure where to stick the libtool flags "-c -static", to deal with Apple's quirkiness. |
This looks like a "your openssl is too old" issue. What version is it ? |
It turns out this issue only surfaces with LibreSSL (either https://github.com/libressl-portable/portable or the 3.3.1 release tarball). Just tried with openssl 1.1.1j-dev from https://github.com/openssl/openssl) and wget2 git code compiles successfully. I switched to LibreSSL recently as it has gained TLS 1.3 support in both client and server, reputed to be a drop-in substitute for OpenSSL for most purposes, with a supposedly smaller attack surface. |
Added an issue for LibreSSL support: https://gitlab.com/gnuwget/wget2/-/issues/552 |
I build https://gnuwget.gitlab.io/wget2/wget2-latest.tar.gz fine on macos 10.11 and 10.14 with Apple clang, but not the latest git source from https://gitlab.com/gnuwget/wget2.git
The same error seemed to be part of https://gitlab.com/gnuwget/wget2/-/issues/353, per google cache, but I'm not finding any of the text on that issue right now.
The text was updated successfully, but these errors were encountered: