Skip to content
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

[libidn2] build failure on osx pipeline #17057

Closed
autoantwort opened this issue Apr 3, 2021 · 11 comments
Closed

[libidn2] build failure on osx pipeline #17057

autoantwort opened this issue Apr 3, 2021 · 11 comments
Assignees
Labels
category:port-bug The issue is with a library, which is something the port should already support

Comments

@autoantwort
Copy link
Contributor

autoantwort commented Apr 3, 2021

Host Environment

  • OS: macOS CI
  • Compiler: unknown

To Reproduce
Steps to reproduce the behavior:
Run pipeline of #17049

Failure logs
https://dev.azure.com/vcpkg/c1ee48cb-0df2-4ab3-8384-b1df5a79fe53/_apis/build/builds/51476/artifacts?artifactName=failure%20logs%20for%20x64-osx&api-version=6.0&%24format=zip

autoconf-x64-osx-err.log:

autoreconf: export WARNINGS=
autoreconf: Entering directory '.'
autoreconf: running: autopoint --force
autoreconf: running: aclocal --force -I m4 -I unistring/m4
autoreconf: configure.ac: tracing
autoreconf: running: glibtoolize --copy --force
autoreconf: configure.ac: not using Intltool
autoreconf: running: gtkdocize --copy
Can't exec "gtkdocize": No such file or directory at /usr/local/Cellar/autoconf/2.71/share/autoconf/Autom4te/FileUtils.pm line 293.
autoreconf: error: gtkdocize failed with exit status: 2

Additional context
It seems to be similar to #16990

@autoantwort
Copy link
Contributor Author

@NancyLi1013
Copy link
Contributor

Hi @autoantwort

Thanks for posting this issue.
I noticed that all CI checks have passed on #17049 now. Does this issue also exist on your machine?

On my virtual box machine, the failures like this:

  autoreconf: Entering directory `.'
  autoreconf: running: autopoint --force
  Can't exec "autopoint": No such file or directory at /usr/local/Cellar/autoconf/2.69/share/autoconf/Autom4te/FileUtils.pm line 345.
  autoreconf: failed to run autopoint: No such file or directory
  autoreconf: autopoint is needed because this package uses Gettext

I investigated this error and found the reference https://dausruddin.com/autoreconf-failed-to-run-autopoint-no-such-file-or-directory/ and http://tutorialspots.com/how-to-fix-error-autoreconf-failed-to-run-autopoint-no-such-file-or-directory-on-centos-4724.html.

Seems need to install gettext. But I cannot install it without permission.

So I'm not sure if it can solve the problem. If possible, you can try on your local machine.

@autoantwort
Copy link
Contributor Author

Does this issue also exist on your machine?

Yes

@NancyLi1013 NancyLi1013 added the category:port-bug The issue is with a library, which is something the port should already support label Apr 7, 2021
@autoantwort
Copy link
Contributor Author

brew install gtk-doc solves the issue

@NancyLi1013
Copy link
Contributor

Thanks for your reply. This seems be related our test environment. For me, gettext is required.

@dg0yt
Copy link
Contributor

dg0yt commented Apr 11, 2021

IMO this is a problem with the ports which rely on autoconf:
While some host dependencies (such as gettext, gtk-doc) could be disabled by parameters to configure, they are mandatory when running autoconf.

@strega-nil
Copy link
Contributor

Seems like this should be solved by changing the array here to also include gettext (and perhaps gtk-doc?)

Once this is PR'd, I can do the actual updates.

@dg0yt
Copy link
Contributor

dg0yt commented Apr 13, 2021

gtk-doc is already waiting for your review at #17227. I will add gettext and comment there.

@NancyLi1013
Copy link
Contributor

brew install gettext solves the issue on my machine. We may need to add message to reminder users to install required dependency library.

But I'm not sure if other users have the same required dependency as mine. For now, I cannot confirm which one is needed for this port. Such as gettext or gtk-doc.

@dg0yt
Copy link
Contributor

dg0yt commented Apr 25, 2021

#17419 got merged, so this should be solved.

@NancyLi1013
Copy link
Contributor

Thanks for your information @dg0yt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:port-bug The issue is with a library, which is something the port should already support
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants