WARNING: generated for both stdio.h and select.h #7902

issue blue-onyx opened this issue on April 17, 2016
  1. blue-onyx commented at 7:44 PM on April 17, 2016: none

    Please forgive me if I'm not reporting this correctly -- I'm following directions generated by "./configure" and I've never reported an issue to github before...

    Software: Mac OS X Version 10.6.8 Snow Leopard Hardware: 2.66GHz Intel Core i7 4GB 1067 MHz DDR3

    I attempted to install the binary of Bitcoin Core 0.12.1 but it failed and said I'd need to update my OS before I could install the binary. I am currently limited to Snow Leopard due to requirements for other projects, etc. Therefore, I decided to try my hand at building from source.

    When I run "./configure", I receive the following errors:

    configure: WARNING:  stdio.h: present but cannot be compiled
    configure: WARNING:  stdio.h:     check for missing prerequisite headers?
    configure: WARNING:  stdio.h: see the Autoconf documentation
    configure: WARNING:  stdio.h:     section "Present But Cannot Be Compiled"
    configure: WARNING:  stdio.h: proceeding with the compiler's result
    configure: WARNING:      ## -------------------------------------------------------- ##
    configure: WARNING:      ## Report this to https://github.com/bitcoin/bitcoin/issues ##
    configure: WARNING:      ## -------------------------------------------------------- ##
    
    configure: WARNING:  sys/select.h: present but cannot be compiled
    configure: WARNING:  sys/select.h:     check for missing prerequisite headers?
    configure: WARNING:  sys/select.h: see the Autoconf documentation
    configure: WARNING:  sys/select.h:     section "Present But Cannot Be Compiled"
    configure: WARNING:  sys/select.h: proceeding with the compiler's result
    configure: WARNING:      ## -------------------------------------------------------- ##
    configure: WARNING:      ## Report this to https://github.com/bitcoin/bitcoin/issues ##
    configure: WARNING:      ## -------------------------------------------------------- ##
    

    Thanks to all of you for the amazing work you do for the community, I don't know if there is a way for an official binary to still be available for Snow Leopard, but that too, would be greatly appreciated =) Or if someone wants to help me learn how to create the binary installer for Snow Leopard, perhaps I could contribute that back? It is only difficult the first time, right?

    If there is anything more you need from me, I'd be happy to help. Please understand that you may have to help me help you because building from source is something that I have knowledge of, but not much understanding of. I'm reasonably comfortable with the CLI, I just don't know if I can answer some questions you may have.

    Warm regards, blue-onyx

  2. kirkalx commented at 1:00 AM on April 18, 2016: contributor

    Can't be more help yet sorry, but this is the autconf documentation it is referring to (for latest version of autoconf): https://www.gnu.org/software/autoconf/manual/autoconf-2.69/html_node/Present-But-Cannot-Be-Compiled.html#Present-But-Cannot-Be-Compiled

  3. jonasschnelli added the label MacOSX on Apr 18, 2016
  4. jonasschnelli commented at 6:52 AM on April 18, 2016: contributor

    Active support for compiling < OSX10.7 has been dropped, though, it should work. Can you double-check that your Xcode installation (including command line tools) is correct? Can you check what you get when typing xcode-select -p?

  5. laanwj commented at 1:59 PM on April 18, 2016: member

    OSX has huge, incompatible changes between versions, which makes it a large burden to support older versions and still do e.g. code signing correctly - and our experience is that, due to the fast churn, (almost) no one cares about support for old versions of MacOSX (an amusing comparison: see the outrage about dropping Windows XP support in #7681, a whopping 15 year old OS).

    Building it from source should work though. The error about stdio.h looks like a base issue with your build environment and not something related to bitcoin itself. Can you compile other c/c++ code?

  6. paveljanik commented at 2:03 PM on April 18, 2016: contributor

    Please paste config.log file somewhere.

  7. blue-onyx commented at 6:13 PM on April 18, 2016: none

    jonasschnelli, When typing xcode-select -p, I receive the following output:

    <user>$ xcode-select -p
    Usage: xcode-select -print-path
       or: xcode-select -switch <xcode_folder_path>
       or: xcode-select -version
    Arguments:
       -print-path                     Prints the path of the current Xcode folder
       -switch <xcode_folder_path>     Sets the path for the current Xcode folder
       -version                        Prints xcode-select version information
    

    I wasn't sure what you were looking for, so I include the following in anticipation of your needs, xcode-select -version:

    xcode-select -version 895.


    laanwj, Thank you for the background. I do understand how this could be a challenge for the team, and I certainly am not trying to create work. Unfortunately, at this time, I am pretty locked into Snow Leopard. I hope to be able to move forward (perhaps through the use of virtual machines?) at some point during the next 12 months, but I would need a working installation of Bitcoin Core long before then. For me, it isn't a matter of just dragging my feet or not wanting to upgrade, I'd prefer to be on El Cap, if for no other reason than security patches. I just have to be patient for the time being. You asked if I can "compile other c/c++ code?", to which I say, "I'm not sure". I haven't had need to do so recently. Does anyone have a recommendation as to a simple build I could try to test this? My only requirements are...

    1. Needs to be a trusted code base -- I can not afford to add any security vulnerabilities, and
    2. Needs to be easy to build... I'm not afraid of the CLI, but I don't live there. I can follow a well written "how to" but following instructions and understanding what one is doing are two completely different things.

    Thank you, Mr. van der Laan


    paveljanik,

    Hopefully the below file is what you are looking for...

    config.log.txt


    I appreciate the work that you all do for the community. As before, please let me know if there is more that I can do to help... Regards

  8. paveljanik commented at 6:27 PM on April 18, 2016: contributor

    The crucial thing is:

    cc1plus: error: unrecognized command line option "-Wno-self-assign"
    

    Try to remove it from

    configure.ac:  CXXFLAGS="$CXXFLAGS -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -Wno-self-assign"
    

    and run ./autogen.sh again.

  9. blue-onyx commented at 7:40 PM on April 18, 2016: none

    paveljanik,

    Thanks, I think we are making progress...

    Running ./autogen.sh after the edit of configure.ac threw the following warning:

    configure.ac:25: warning: The macro `AC_FOREACH' is obsolete.
    configure.ac:25: You should run autoupdate.
    

    I then ran autoupdate configure.ac and then ./autogen.sh again.

    The autogen.sh warning is still there. HOWEVER, now when I run ./configure, the initial issue I posted is not displayed.

    The last line output after running ./configure now says:

    configure: error: libdb_cxx headers missing, Bitcoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

    For this installation, I will need wallet functionality.

    Question... What does the "-Wno-self-assign" flag do?

    Continued thanks... Regards

  10. paveljanik commented at 7:49 PM on April 18, 2016: contributor

    OK, you can start to follow the instructions at https://github.com/bitcoin/bitcoin/blob/master/doc/build-osx.md

  11. blue-onyx commented at 12:36 AM on April 19, 2016: none

    This has kind of migrated from filing a bug report as prompted by the software, to personal help, for which I'm sorry. However, I'm not figuring this out...

    The latest (as I follow the build-osx.md instructions above) is that I get the following error:

    configure: error: pkg-config not found.

    Yet, when I try a which pkg-config I receive the following:

    <user>$ which pkg-config
    /usr/local/bin/pkg-config
    

    And FYI...

    <user>$ pkg-config --version
    0.29.1
    

    I don't remember now where I stumbled upon the following information:

    Please set GLIB_CFLAGS and GLIB_LIBS to the correct values

    Referring to ./configure -h as well as the internet at large, I can't seem to figure out the format to pass these values. Is that even the problem I need solved???

    Again, I seem to be stumped... Thanks folks, Regards

  12. paveljanik commented at 4:26 AM on April 19, 2016: contributor

    You should try configure from the new shell already containing /usr/local/bin in your PATH. It should work.

    E.g. configure --enable-wallet.

  13. laanwj commented at 8:20 AM on April 19, 2016: member

    cc1plus: error: unrecognized command line option "-Wno-self-assign"

    Why is that an error? Normally unrecognized -W command line options should raise a warning.

  14. paveljanik commented at 8:43 AM on April 19, 2016: contributor

    This is probably because of the old system he is running. gcc is used there, not clang.

  15. paveljanik commented at 8:47 AM on April 19, 2016: contributor
    $ g++ -c q.c -Wno-self-assign
    cc1plus: error: unrecognized command line option "-Wno-self-assign"
    $
    
  16. laanwj commented at 8:55 AM on April 19, 2016: member

    Should be the same for gcc though...

  17. blue-onyx commented at 2:30 PM on April 19, 2016: none

    paveljanik wrote:

    You should try configure from the new shell already containing /usr/local/bin in your PATH. It should work.

    E.g. configure --enable-wallet.

    <user>$ echo $PATH
    /usr/local/bin:/usr/local/sbin:/usr/local/mysql/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
    
    <user>$ which pkg-config
    /usr/local/bin/pkg-config
    

    Then, when I run ./configure --enable-wallet it throws:

    configure: error: pkg-config not found.

  18. paveljanik commented at 4:52 PM on April 19, 2016: contributor

    Can you run pkg-config? What do you have in config.log now?

  19. blue-onyx commented at 5:31 PM on April 19, 2016: none
    <user>$ pkg-config
    Must specify package names on the command line
    

    config.log.txt

  20. paveljanik commented at 5:48 PM on April 19, 2016: contributor
    configure:17146: checking for pkg-config
    configure:17179: result: no
    configure:18412: checking for port
    configure:18442: result: no
    configure:18458: checking for brew
    configure:18488: result: no
    

    Do you use port or brew? Please fix this first...

  21. paveljanik commented at 5:50 PM on April 19, 2016: contributor

    It is quite difficult to debug such old system for us... Isn't it time to update your system? ;-) Using Bitcoin Core on such system is not recommended because there are no updates from Apple.

  22. blue-onyx commented at 5:57 PM on April 19, 2016: none
    <user>$ which brew
    /usr/local/bin/brew
    

    This doesn't make any sense to me... It is present but the system doesn't think it is there. Though I apparently don't have port installed (at least for this user).

  23. blue-onyx commented at 7:50 PM on April 19, 2016: none

    Perhaps I'm going about this all wrong...

    • If I run an older version (say 0.11.2) of Bitcoin Core, are there security risks?
    • Are there trustworthy BTC apps for the iOS platform?
    • If I run one on iOS will it consume gigabytes of storage in order to maintain a copy of the blockchain?
    • Does Apple accept BTC for me to buy a "new" system which will run current software? =-$
  24. achow101 commented at 9:33 PM on April 19, 2016: member

    If I run an older version (say 0.11.2) of Bitcoin Core, are there security risks?

    Probably not, but you should check the release notes of releases since that one to see if any critical vulnerabilities have been patched. Sometimes security vulnerabilities are found and are fixed in later versions

    Are there trustworthy BTC apps for the iOS platform?

    Yes, but Bitcoin Core does not run on iOS.

    If I run one on iOS will it consume gigabytes of storage in order to maintain a copy of the blockchain?

    It depends on the software. Most mobile software will be either an SPV wallet or web wallet so it won't download the entire blockchain.

    Does Apple accept BTC for me to buy a "new" system which will run current software? =-$

    No. Apple does not accept Bitcoin

  25. laanwj commented at 1:22 PM on April 20, 2016: member

    @blue-onyx

    Does Apple accept BTC for me to buy a "new" system which will run current software? =-$

    Hah you should balance your (and other's) time spent getting this to work with the price of just buying new hardware - although it may be a learning experience, I think it's pretty easy to come out in favor of just giving this up.

    Alternatively maybe you can install Ubuntu on the old computer?

  26. paveljanik commented at 5:58 PM on May 3, 2016: contributor

    @blue-onyx Please close this issue, we can't help you unfortunately.

  27. blue-onyx closed this on May 3, 2016

  28. MarcoFalke locked this on Sep 8, 2021

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-18 18:15 UTC

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