build: configure script warnings on macOS #896

issue hebasto openend this issue on February 17, 2021
  1. hebasto commented at 8:26 am on February 17, 2021: member

    Configuring the recent master branch (24d1656c328c932cd533f6f4bf80b345b6591f0d) on macOS Big Sur 11.2.1 (20D74), and receiving 4 messages rm: conftest.dSYM: is a directory:

     0% ./configure -q
     1rm: conftest.dSYM: is a directory
     2rm: conftest.dSYM: is a directory
     3rm: conftest.dSYM: is a directory
     4rm: conftest.dSYM: is a directory
     5
     6Build Options:
     7  with ecmult precomp     = yes
     8  with external callbacks = no
     9  with benchmarks         = yes
    10  with tests              = yes
    11  with openssl tests      = yes
    12  with coverage           = no
    13  module ecdh             = no
    14  module recovery         = no
    15  module extrakeys        = no
    16  module schnorrsig       = no
    17
    18  asm                     = x86_64
    19  bignum                  = no
    20  ecmult window size      = 15
    21  ecmult gen prec. bits   = 4
    22
    23  valgrind                = no
    24  CC                      = gcc
    25  CFLAGS                  = -O2 -fvisibility=hidden -std=c89 -pedantic -Wall -Wextra -Wcast-align -Wnested-externs -Wshadow -Wstrict-prototypes -Wundef -Wno-unused-function -Wno-long-long -Wno-overlength-strings -W -g
    26  CPPFLAGS                = -I/usr/local/Cellar/valgrind/3.16.1/include 
    27  LDFLAGS                 = 
    28
    29  CC_FOR_BUILD            = gcc
    30  CFLAGS_FOR_BUILD        = -O2 -fvisibility=hidden -std=c89 -pedantic -Wall -Wextra -Wcast-align -Wnested-externs -Wshadow -Wstrict-prototypes -Wundef -Wno-unused-function -Wno-long-long -Wno-overlength-strings -W -g
    31  CPPFLAGS_FOR_BUILD      = -I/usr/local/Cellar/valgrind/3.16.1/include 
    32  LDFLAGS_FOR_BUILD       =
    

    Detailed:

     0% ./configure
     1...
     2checking whether gcc understands -c and -o together... rm: conftest.dSYM: is a directory
     3yes
     4...
     5checking the name lister (/usr/bin/nm -B) interface... rm: conftest.dSYM: is a directory
     6BSD nm
     7...
     8checking for archiver [@FILE](/bitcoin-core-secp256k1/contributor/file/) support... rm: conftest.dSYM: is a directory
     9no
    10...
    11checking command to parse /usr/bin/nm -B output from gcc object... rm: conftest.dSYM: is a directory
    12ok
    13...
    
  2. real-or-random commented at 11:14 am on February 17, 2021: contributor

    Did you run autogen.sh again just to be sure?

    So I guess you may have figured that out already but that’s not a serious issue, it just means that some conftest.dSYM directory will be left in your tree. See https://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html

    What’s the output of glibtool --version and autoconf --version? edit: and autoreconf --version?

  3. hebasto commented at 12:48 pm on February 17, 2021: member

    Did you run autogen.sh again just to be sure?

    Yess :)

    So I guess you may have figured that out already but that’s not a serious issue, it just means that some conftest.dSYM directory will be left in your tree. See https://lists.gnu.org/archive/html/bug-autoconf/2007-11/msg00017.html

    Yeah, I’ve read some mls, including that you point at, and I agree that’s not a serious issue.

    What’s the output of glibtool --version and autoconf --version? edit: and autoreconf --version?

    0% glibtool --version
    1glibtool (GNU libtool) 2.4.6
    2Written by Gordon Matzigkeit, 1996
    3
    4Copyright (C) 2014 Free Software Foundation, Inc.
    5This is free software; see the source for copying conditions.  There is NO
    6warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
    
    0% autoconf --version
    1autoconf (GNU Autoconf) 2.69
    2Copyright (C) 2012 Free Software Foundation, Inc.
    3License GPLv3+/Autoconf: GNU GPL version 3 or later
    4<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
    5This is free software: you are free to change and redistribute it.
    6There is NO WARRANTY, to the extent permitted by law.
    7
    8Written by David J. MacKenzie and Akim Demaille.
    
    0% autoreconf --version
    1autoreconf (GNU Autoconf) 2.69
    2Copyright (C) 2012 Free Software Foundation, Inc.
    3License GPLv3+/Autoconf: GNU GPL version 3 or later
    4<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
    5This is free software: you are free to change and redistribute it.
    6There is NO WARRANTY, to the extent permitted by law.
    7
    8Written by David J. MacKenzie and Akim Demaille.
    
  4. real-or-random commented at 4:54 pm on February 17, 2021: contributor

    Hm, these are not the most recent versions but they should be recent enough then… Cirrus CI shows the same issue: https://cirrus-ci.com/task/5325071847784448?command=test#L51

    Can you try removing the directory and see if the error persists?

    Looking at the the (old) Travis logs, I believe this was introduced by #862. Can you confirm this?

    before: https://travis-ci.org/github/bitcoin-core/secp256k1/builds/754093307 after: https://travis-ci.org/github/bitcoin-core/secp256k1/builds/754127317 Make sure to look at “gcc” build (which is Apple’s fake gcc).

  5. hebasto commented at 5:47 pm on February 17, 2021: member

    Hm, these are not the most recent versions but they should be recent enough then…

    Both packages are installed via Homebrew, btw:

    Can you try removing the directory and see if the error persists?

    find . -type d does not list such directories…

  6. hebasto commented at 5:55 pm on February 17, 2021: member

    Looking at the the (old) Travis logs, I believe this was introduced by #862. Can you confirm this?

    0# just cloned repo
    1% git checkout 328aaef22a4378817dbc5b7f27cd6351858c0b6c
    2% ./autogen.sh
    3% ./configure -q
    4rm: conftest.dSYM: is a directory
    5rm: conftest.dSYM: is a directory
    6rm: conftest.dSYM: is a directory
    7rm: conftest.dSYM: is a directory
    8...
    
  7. hebasto commented at 6:11 pm on February 17, 2021: member
    I think 83fb1bcef49b1c12ef349f62d90bfcc83f0f7398 (#700) is the cause of warnings.
  8. hebasto cross-referenced this on Feb 17, 2021 from issue Allow overriding default flags by jonasnick
  9. real-or-random referenced this in commit 595efa0104 on May 13, 2021
  10. real-or-random cross-referenced this on May 13, 2021 from issue Various improvements related to CFLAGS by real-or-random
  11. real-or-random referenced this in commit 301d835275 on May 25, 2021
  12. real-or-random referenced this in commit 80dfdba19c on Jun 10, 2021
  13. real-or-random referenced this in commit b924e1e605 on Jul 1, 2021
  14. jonasnick closed this on Jul 1, 2021

  15. hebasto cross-referenced this on Mar 17, 2023 from issue build: Ensure no optimization when building for coverage analysis by hebasto
  16. dderjoel referenced this in commit 702d91f7cc on May 23, 2023

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin-core/secp256k1. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2024-11-22 09:15 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me