mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: build fail with message "error: redefinition of 'index' as different kind of symbol"
Date: Tue, 30 Jul 2019 11:50:59 -0400	[thread overview]
Message-ID: <20190730155059.GY1506@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAFa4zD2iG7zvGNt+3M6amMqLivkiJFtrLTFzFN-9VTKVXv65tg@mail.gmail.com>

On Wed, Jul 31, 2019 at 12:31:17AM +0900, Jeeyong Um wrote:
> Hello.
> I have a question about building musl with `_BSD_SOURCE` definition.
> 
> `src/time/__tz.c` has static variable named by `index` (line 25) and
> include `string.h` header file (line 5).
> 5  #include <string.h>
> 25 static const unsigned char *zi, *trans, *index, *types, *abbrevs,
> *abbrevs_end;
> 
> By the way, `include/string.h` includes `strings.h` when _BSD_SOURCE is
> defined (line 57).
> 56 #if defined(_BSD_SOURCE) || defined(_GNU_SOURCE)
> 57 #include <strings.h>
> 58 #endif
> 
> `include/strings.h` has a function named by `index` too (line 19).
> 13 #if defined(_GNU_SOURCE) || defined(_BSD_SOURCE) ||
> defined(_POSIX_SOURCE) \
> 14  || (defined(_POSIX_C_SOURCE) && _POSIX_C_SOURCE+0 < 200809L) \
> 15  || (defined(_XOPEN_SOURCE) && _XOPEN_SOURCE+0 < 700)
> 16 int bcmp (const void *, const void *, size_t);
> 17 void bcopy (const void *, void *, size_t);
> 18 void bzero (void *, size_t);
> 19 char *index (const char *, int);
> 20 char *rindex (const char *, int);
> 21 #endif
> 
> Is it possible to build musl with _BSD_SOURCE definition in this case?
> Even though `static` modifier limits the scope of variable to the file, the
> conflict between `index` of `strings.h` and `index` of `__tz.c` seems
> unavoidable.
> Please let me know if you find any mistakes here.

The musl source files assume the default feature test macros provided
by their makefile, -D_XOPEN_SOURCE=700 which also includes POSIX base,
no extensions. Extensions by their nature bring into the namespace
things that might conflict with valid code.

If -D_BSD_SOURCE is getting into the build for musl, it likely means
you have a larger build system problem, like injecting it into CFLAGS
for every package you build. This might be making some "spurious"
problems go away, but it very well could create others. It would be
much better to fix whatever prompted you to do this to begin with. If
that's not practical, at least remove it from your build for musl.

Rich


  reply	other threads:[~2019-07-30 15:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-30 15:31 Jeeyong Um
2019-07-30 15:50 ` Rich Felker [this message]
2019-07-30 16:09   ` Jeeyong Um
2019-07-30 16:11     ` Rich Felker

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=20190730155059.GY1506@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).