public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Alain GUILLEMOT <alain.guillemot@asn.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: RE: Glibc on target 32 bits with 64-bit time support
Date: Tue, 16 May 2023 17:20:14 +0000	[thread overview]
Message-ID: <PAZP264MB4414CBC4FEDFA0D820FCC3B3E4799@PAZP264MB4414.FRAP264.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87h6sd73st.fsf@oldenburg.str.redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]

Hi Florian

In « glibc-2.34/configure » file, for "   CFLAGS="-g -O2 -D_FILE_OFFSET_BITS=64 -D_TIME_BITS=64"" and CXXFLAGS, and with CPPFLAGS environment variable.

A+


De : Florian Weimer <fweimer@redhat.com>
Envoyé : lundi 15 mai 2023 22:12
À : Alain GUILLEMOT <alain.guillemot@asn.com>
Cc : libc-help@sourceware.org
Objet : Re: Glibc on target 32 bits with 64-bit time support

* Alain GUILLEMOT: > In which file I have to add the option "-D_FILE_OFFSET_BITS=64 > -D_TIME_BITS=64", or are these options to be passed on the command > line? All ABI variants are automatically built. You don't have to do anything


* Alain GUILLEMOT:



> In which file I have to add the option "-D_FILE_OFFSET_BITS=64

> -D_TIME_BITS=64", or are these options to be passed on the command

> line?



All ABI variants are automatically built.  You don't have to do anything

while building glibc.  These flags are for building applications with

glibc.



Thanks,

Florian



  reply	other threads:[~2023-05-16 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 18:25 Alain GUILLEMOT
2023-05-15 20:11 ` Florian Weimer
2023-05-16 17:20   ` Alain GUILLEMOT [this message]
2023-05-16 17:53     ` Florian Weimer
2023-05-18 10:31   ` Alain GUILLEMOT
2023-05-18 10:46     ` Lukasz Majewski
2023-05-18 19:49       ` Alain GUILLEMOT

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=PAZP264MB4414CBC4FEDFA0D820FCC3B3E4799@PAZP264MB4414.FRAP264.PROD.OUTLOOK.COM \
    --to=alain.guillemot@asn.com \
    --cc=fweimer@redhat.com \
    --cc=libc-help@sourceware.org \
    /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).