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

./configure issue on FreeBSD for recursor 4.0.5 #5401

Closed
RvdE opened this Issue Jun 14, 2017 · 5 comments

Comments

Projects
None yet
5 participants
@RvdE
Contributor

RvdE commented Jun 14, 2017

  • Program: Recursor
  • Issue type: Bug report

Short description

When running configure on FreeBSD it fails with the following error:
./configure: 2: Syntax error: Unterminated quoted string
./configure: 15888: Syntax error: Error in command substitution

Environment

  • Operating system: FreeBSD 11.0
  • Software version: 4.0.5
  • Software source: PowerDNS repository

Steps to reproduce

  1. ./configure

Other information

As requested by Peter (Habbie on IRC), this is to blame:
commit 6484f26 pieterlexis: Check if we can link against libatomic if needed https://git.io/vH5SS

@tjikkun

This comment has been minimized.

Show comment
Hide comment
@tjikkun

tjikkun Jun 14, 2017

Contributor

This also prevents the Fedora build to succeed, because ppc64 and ppc64le are broken by this.

Contributor

tjikkun commented Jun 14, 2017

This also prevents the Fedora build to succeed, because ppc64 and ppc64le are broken by this.

@Habbie

This comment has been minimized.

Show comment
Hide comment
@Habbie

Habbie Jun 15, 2017

Member
  case "$host" in
  mips* | powerpc* )
    as_CACHEVAR=`$as_echo "ax_cv_check_ldflags_cannot continue" "$LINENO" 5
    _-latomic" | $as_tr_sh`
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the linker accepts -latomic" >&5
$as_echo_n "checking whether the linker accepts -latomic... " >&6; }

is the offending bit - line 15888 in the tarball.

Member

Habbie commented Jun 15, 2017

  case "$host" in
  mips* | powerpc* )
    as_CACHEVAR=`$as_echo "ax_cv_check_ldflags_cannot continue" "$LINENO" 5
    _-latomic" | $as_tr_sh`
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the linker accepts -latomic" >&5
$as_echo_n "checking whether the linker accepts -latomic... " >&6; }

is the offending bit - line 15888 in the tarball.

@pieterlexis pieterlexis self-assigned this Jun 15, 2017

Habbie added a commit to Habbie/pdns that referenced this issue Jun 15, 2017

@Habbie Habbie assigned Habbie and unassigned pieterlexis Jun 15, 2017

Habbie added a commit to Habbie/pdns that referenced this issue Jun 15, 2017

Habbie added a commit that referenced this issue Jun 19, 2017

@Habbie

This comment has been minimized.

Show comment
Hide comment
@Habbie

Habbie Jun 19, 2017

Member

Fixed in #5411

Member

Habbie commented Jun 19, 2017

Fixed in #5411

@Habbie Habbie closed this Jun 19, 2017

Habbie added a commit to Habbie/pdns that referenced this issue Jun 21, 2017

@Habbie Habbie referenced this issue Jun 21, 2017

Merged

unbreak quoting; fixes #5401 #5440

2 of 7 tasks complete

pieterlexis added a commit that referenced this issue Jun 21, 2017

@danel1

This comment has been minimized.

Show comment
Hide comment
@danel1

danel1 Jun 26, 2017

@Habbie Build is still broken on FreeBSD 10.3, even when applying the patch of #5411

checking dynamic linker characteristics... freebsd10.3 ld.so
checking how to hardcode library paths into programs... immediate
./configure: 2: Syntax error: Unterminated quoted string
./configure: 15888: Syntax error: Error in command substitution

[ AC_MSG_ERROR([Unable to link against libatomic, cannot continue]) ]

danel1 commented Jun 26, 2017

@Habbie Build is still broken on FreeBSD 10.3, even when applying the patch of #5411

checking dynamic linker characteristics... freebsd10.3 ld.so
checking how to hardcode library paths into programs... immediate
./configure: 2: Syntax error: Unterminated quoted string
./configure: 15888: Syntax error: Error in command substitution

[ AC_MSG_ERROR([Unable to link against libatomic, cannot continue]) ]

@Habbie

This comment has been minimized.

Show comment
Hide comment
@Habbie

Habbie Jun 26, 2017

Member

@danel1 after applying the patch, you need to run autoreconf -vfi

Member

Habbie commented Jun 26, 2017

@danel1 after applying the patch, you need to run autoreconf -vfi

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment