mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Scherbatiy Alexander <alexander.scherbatiy@bell-sw.com>
To: musl <musl@lists.openwall.com>
Subject: gnu autoconf AC_CANONICAL_BUILD returns linux-gnu build_os on Alpine Linux 3.10.3
Date: Mon, 30 Dec 2019 14:24:56 +0300	[thread overview]
Message-ID: <1504261577705096@sas1-0ef7a84b6a92.qloud-c.yandex.net> (raw)

Hello,

gnu autoconf AC_CANONICAL_BUILD returns linux-gnu build_os variable on Alpine Linux 3.10.3.

Here is a snippet from the configure.ac file which I tested in docker alpine:3.10.3
----------------
AC_CANONICAL_BUILD
AC_MSG_NOTICE([build_os=$build_os])
----------------
Output:
----------------
checking build system type... x86_64-pc-linux-gnu
configure: build_os=linux-gnu
----------------

The same code on Alpine 3.8.4 (docker alpine:3.8 ) returns:
----------------
checking build system type... x86_64-pc-linux-musl
configure: build_os=linux-musl
----------------

Is it expected that build_os is detected as linux-gnu instead of linux-musl on Alpine 3.0.3?

Thanks,
Alexander.

Simple project:

--- configure.ac ---
AC_INIT([amhello], [1.0], [bug-automake@gnu.org])
AM_INIT_AUTOMAKE([-Wall -Werror foreign])

# Environment
AC_CANONICAL_BUILD
AC_MSG_NOTICE([build_os=$build_os])

AC_PROG_CC
AC_CONFIG_HEADERS([config.h])
AC_CONFIG_FILES([
 Makefile
])
AC_OUTPUT

--- Makefile.am ---
bin_PROGRAMS = hello
hello_SOURCES = main.c

--- Makefile.am ---
bin_PROGRAMS = hello
hello_SOURCES = main.c
/tmp/sample/autoconf-sample # cat main.c 
#include <config.h>
#include <stdio.h>

int main (void)
{
  printf("Hello World!\n");
  return 0;
}

----------------
autoreconf -i
./configure



             reply	other threads:[~2019-12-30 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 11:24 Scherbatiy Alexander [this message]
2019-12-30 16:54 ` Rich Felker
2020-01-10 12:34   ` Alexander Scherbatiy

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=1504261577705096@sas1-0ef7a84b6a92.qloud-c.yandex.net \
    --to=alexander.scherbatiy@bell-sw.com \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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 NNTP newsgroup(s).