Buildroot Archive mirror
 help / color / mirror / Atom feed
From: Edgar Bonet <bonet@grenoble.cnrs.fr>
To: buildroot@buildroot.org
Cc: Samuel Martin <s.martin49@gmail.com>
Subject: [Buildroot] Nginx fails to build with GCC 14
Date: Tue, 14 May 2024 22:28:31 +0200	[thread overview]
Message-ID: <5647a701-8c5a-4ce6-92c3-3c252e1cd91b@grenoble.cnrs.fr> (raw)

Hello all!

Building nginx with GCC 14 fails at the configure step with:

    ./configure: error: libatomic_ops library was not found.

Steps to reproduce:

    git checkout 9764258aaf0e  # master as of 2024-05-14
    make clean
    make defconfig
    utils/config --enable GCC_VERSION_14_X
    utils/config --enable PACKAGE_NGINX
    make olddefconfig
    make

If the option GCC_VERSION_14_X is omitted (we then default to GCC 13),
the build succeeds.

Looking at output/build/nginx-1.24.0/objs/autoconf.err, it appears the
error is not caused by a missing library, but by an unrelated
“incompatible pointer type” error on the test program:

    ...
    checking for atomic_ops library
    objs/autotest.c: In function 'main':
    objs/autotest.c:9:48: error: passing argument 1 of 'AO_compare_and_swap' from incompatible pointer type [-Wincompatible-pointer-types]

I did not dig this much further. However, I noticed that the file
package/nginx/nginx.mk contains this comment:

    # disable external libatomic_ops because its detection fails.

which makes me wonder why ./configure is probing for the library anyway.

Regards,

Edgar Bonet.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2024-05-14 20:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-14 20:28 Edgar Bonet [this message]
2024-05-15 15:31 ` [Buildroot] Nginx fails to build with GCC 14 Edgar Bonet
2024-05-15 19:19   ` Arnout Vandecappelle via buildroot
2024-05-16  8:38     ` Edgar Bonet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5647a701-8c5a-4ce6-92c3-3c252e1cd91b@grenoble.cnrs.fr \
    --to=bonet@grenoble.cnrs.fr \
    --cc=buildroot@buildroot.org \
    --cc=s.martin49@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).