From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Behun <marek.behun@nic.cz>
Date: Fri, 5 Mar 2021 16:37:11 +0100
Subject: [RFC PATCH u-boot 02/12] sandbox: errno: avoid conflict with
 libc's errno
In-Reply-To: <CAEUhbmWtwZgqfvNV_CZXt5GLoiqkwtahqqB6seqVMjyb7DrC-w@mail.gmail.com>
References: <20210303041211.26945-1-marek.behun@nic.cz>
 <20210303041211.26945-3-marek.behun@nic.cz>
 <CAEUhbmWtwZgqfvNV_CZXt5GLoiqkwtahqqB6seqVMjyb7DrC-w@mail.gmail.com>
Message-ID: <20210305163711.55a953f1@nic.cz>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On Fri, 5 Mar 2021 11:00:45 +0800
Bin Meng <bmeng.cn@gmail.com> wrote:

> On Wed, Mar 3, 2021 at 12:13 PM Marek Beh?n <marek.behun@nic.cz> wrote:
> >
> > When building with LTO, the system libc's `errno` variable used in
> > arch/sandbox/cpu/os.c conflicts with U-Boot's `errno` (defined in
> > lib/errno.c) with the following error:
> >  .../ld: errno@@GLIBC_PRIVATE: TLS definition in /lib64/libc.so.6
> >          section .tbss mismatches non-TLS reference in
> >          /tmp/u-boot.EQlEXz.ltrans0.ltrans.o  
> 
> Do you know if this is the expected behavior when enabling LTO on the compiler?

I don't, but this is a bug anyway. The symbol clashes with the symbol
from glibc. Does somebody know whether the usage of this symbol in os.c
does really use glibc's version or U-Boot's one?