Hi Ross, after doing a grep to fine the defines, I've found that the defines refer to __USE_TIME_BITS64, instead of _TIME_BITS=64.
The two defined flags appear to do not work "CFLAGS:append = " -D_TIME_BITS=64 -D_USE_TIME_BITS64" At this time only CFLAGS:append = " -D_USE_TIME_BITS64 " compile successfully. I'll keep you in touch Martin Leduc T : (418) 856-6896 [email protected] -----Message d'origine----- De : [email protected] <[email protected]> De la part de Ross Burton Envoyé : 22 février 2022 12:43 À : Martin Leduc <[email protected]> Cc : Phil Blundell <[email protected]>; [email protected] Objet : [EXTERNAL] Re: [Openembedded-architecture] ARM32 Millenium Bug CAUTION: This email originated from outside of Luminator Technology Group. Do not click links or open attachments unless you recognize the sender and know the content is safe. How are you setting -D_TIME_BITS? You want them to be specific to target builds, I'm guessing those errors are what happens when you pass those flags directly to the native build steps. Ross On Tue, 22 Feb 2022 at 13:58, Martin Leduc <[email protected]> wrote: > > Well well well, > > > > I definitely don't understand why bitbake try to compile x86-64 when I've > defined ARM32 architecture. Probably the cross compiler ☹. > > > > --dynamic-linker=/home/ltg/honister/build/tmp/sysroots-uninative/x86_6 > 4-linux/lib/ld-linux-x86-64.so.2 -lsqlite3 -lpthread -ldl -lpthread > > | {standard input}: Assembler messages: > > | {standard input}:20333: Error: symbol `open64' is already defined > > | {standard input}:21238: Error: symbol `openat64' is already defined > > | {standard input}:24673: Error: symbol `stat64' is already defined > > | {standard input}:25158: Error: symbol `lstat64' is already defined > > | {standard input}:25643: Error: symbol `fstat64' is already defined > > | {standard input}:27003: Error: symbol `fstatat64' is already defined > > | {standard input}:31543: Error: symbol `__fxstat64' is already > | defined > > | {standard input}:32524: Error: symbol `__fxstatat64' is already > | defined > > | {standard input}:33546: Error: symbol `__lxstat64' is already > | defined > > | {standard input}:34498: Error: symbol `__openat64_2' is already > | defined > > | {standard input}:36430: Error: symbol `__xstat64' is already defined > > | {standard input}:43039: Error: symbol `creat64' is already defined > > | {standard input}:50405: Error: symbol `fcntl64' is already defined > > | {standard input}:52666: Error: symbol `fopen64' is already defined > > | {standard input}:53998: Error: symbol `freopen64' is already defined > > | {standard input}:56267: Error: symbol `ftw64' is already defined > > | {standard input}:62238: Error: symbol `glob64' is already defined > > | {standard input}:70550: Error: symbol `mkostemp64' is already > | defined > > | {standard input}:71817: Error: symbol `mkstemp64' is already defined > > | {standard input}:73999: Error: symbol `nftw64' is already defined > > | {standard input}:78633: Error: symbol `scandir64' is already defined > > | {standard input}:96084: Error: symbol `truncate64' is already > | defined > > | ERROR: oe_runmake failed > > > > Any idea? > > > > > > Martin Leduc > > T : (418) 856-6896 > > [email protected] > > > > > > -----Message d'origine----- > De : Phil Blundell <[email protected]> > Envoyé : 22 février 2022 08:10 > À : Martin Leduc <[email protected]> Cc : > [email protected] > Objet : [EXTERNAL] Re: [Openembedded-architecture] ARM32 Millenium Bug > > > > CAUTION: This email originated from outside of Luminator Technology Group. Do > not click links or open attachments unless you recognize the sender and know > the content is safe. > > > > On Tue, Feb 22, 2022 at 05:01:55AM -0800, Martin Leduc wrote: > > > I'm wondering how we can manage the Millenium bug (2038-01-19 03:15 AM) on > > the ARM32 Platform. As far as I know, the Kernel 5.14 and GLibc 2.34 are > > require and Honister comply to theses requirements but the bug isn't > > handled. > > > > > > Have you any idea on how to "enable" the differents workaround? > > > > At the moment I think you need to build with -D_TIME_BITS=64 > -D_FILE_OFFSET_BITS=64. This is not the default (in glibc) on aarch32 for > ABI compatibility reasons, but you could add it to your global CFLAGS in your > distro configuration if you wanted. > > > > p. > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1486): https://lists.openembedded.org/g/openembedded-architecture/message/1486 Mute This Topic: https://lists.openembedded.org/mt/89315888/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
