public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos_odonell at mentor dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/14068] New: Split top-level config.h.in into machine dependent and machine independent pieces.
Date: Sun, 06 May 2012 23:48:00 -0000 [thread overview]
Message-ID: <bug-14068-131@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=14068
Bug #: 14068
Summary: Split top-level config.h.in into machine dependent and
machine independent pieces.
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: libc
AssignedTo: carlos_odonell@mentor.com
ReportedBy: carlos_odonell@mentor.com
CC: drepper.fsp@gmail.com
Classification: Unclassified
At present the glibc sources have one top-level config.h.in file.
The config.h.in file contains several definitions for x86, x86_64, Power, and
ARM.
Logically speaking this file should contain only machine independent
definitions.
Instead each machine should have a config.h.in fragment that is aggregated
together with the top-level config.h.in to produce a final config.h.
At present each machine needs to add defines to the top-level config.h.in.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2012-05-06 23:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-06 23:48 carlos_odonell at mentor dot com [this message]
2012-05-07 10:23 ` [Bug libc/14068] " joseph at codesourcery dot com
2012-05-07 20:04 ` roland at gnu dot org
2012-05-07 20:13 ` carlos_odonell at mentor dot com
2012-12-03 23:52 ` carlos at systemhalted dot org
2014-06-25 11:06 ` fweimer at redhat dot com
2015-08-27 22:08 ` [Bug build/14068] " jsm28 at gcc dot gnu.org
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=bug-14068-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.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.
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).