This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
omitting all compatibility interfaces from the build
- From: Rasmus Villemoes <rasmus dot villemoes at prevas dot dk>
- To: "libc-alpha at sourceware dot org" <libc-alpha at sourceware dot org>
- Date: Fri, 7 Feb 2020 09:50:35 +0000
- Subject: omitting all compatibility interfaces from the build
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=prevas.dk; dmarc=pass action=none header.from=prevas.dk; dkim=pass header.d=prevas.dk; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sBTT/ixNLZYSMJ/uAyCW3xY5m8Wf/r4aZL0tg11Kzdg=; b=jX+23NmkWi4bXKTH9l63h9odlreKFX0irN26ZVfd88WZ8y+ChztTD2lXPvbcUyYK0r1tBcOaqYfcBVI9fTZSJSYBYObXMrlJIBQSbPT+KP5N6J/xHNr+cv5ugJmEc4OEOpKrgz+wpxysOE7d+jR0ur2tVbENTrmA5+m64q4qFN6crb5wqo8a83aMqIidUyLREsAABJIySyjYQOC9J+MxlE8mdaWJEkvL4yWd8GSdRLKfbRhPa0mkTaNbdEQQtwP8oJc2ZwGxexE+AYlkhB19i7mtkeCiIDcRqIv2b8ATnsIJwgZr5/bUWAImkFx5rrnJvP/9B9rRfyVIHCCwiWF6JQ==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PKuABYmcc4RDMVyQNEMZTHS0/L5bwBuR/kYh5pfI1GG08F0KCIFANI6vf10ygxQ3ZgA3UDbUPT+TWbtvdprffumkkSztmAQHaHJYVxII3vlIcpEhC18020YgR9ZUA8IJGl0nAvwqB7mpL/Gm8bfeSCCYOy28yPGqmwOyUrdSq/FlMrjfGTuBfmIsvfZabS55FRNTZcD03QME669NR4R50l4XUyvQtB/CPk0aiOFQjVv5DN8c3UkzT+w3KLtyGC6e8Phy8FCBsZyIPPrEoNCDluu7g7Z5T+S9s/Vcy+Wm9Ttn/al1YeWPASRvkh0Q6ExNWsDqqwM1MKGBkCVHbvsNBw==
Hi,
When doing a complete BSP build for an embedded target, there are and
will not be any old existing binaries that have been linked against an
older libc. Hence there is no need for any version of any symbol other
than the currently exposed ones. So would it be possible to add a
configure knob for omitting all the code for the unused/unneeded interfaces?
I looked into shlib-compat.h, and it seems doing
-#ifdef SHARED
+#if defined(SHARED) && !defined(OMIT_COMPAT_VERSIONS)
would be a simple first step, but I assume it can't be that simple - I'm
guessing some later steps in the build process would need tweaking as well.
I'd be happy to do the actual work and figure out what actually needs to
be done, but I first want to hear if such a configure knob is completely
off-the-table before digging into this.
Thanks,
Rasmus