From 2bb8e1ff550ef2b2676e4f7ec3fdaf17aee8d715 Mon Sep 17 00:00:00 2001
From: LemonBoy <thatlemon@gmail.com>
Date: Tue, 11 May 2021 12:43:58 +0200
Subject: stage2: Change libc components' linking order

Use the same order as Clang (and, by extension, GCC) for the three most
important libc components: lm comes first, followed by lpthread and then
lc.
---
 src/glibc.zig | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

(limited to 'src/glibc.zig')

diff --git a/src/glibc.zig b/src/glibc.zig
index a1f02e2f11..7600f19503 100644
--- a/src/glibc.zig
+++ b/src/glibc.zig
@@ -40,10 +40,11 @@ pub const ABI = struct {
     }
 };
 
+// The order of the elements in this array defines the linking order.
 pub const libs = [_]Lib{
-    .{ .name = "c", .sover = 6 },
     .{ .name = "m", .sover = 6 },
     .{ .name = "pthread", .sover = 0 },
+    .{ .name = "c", .sover = 6 },
     .{ .name = "dl", .sover = 2 },
     .{ .name = "rt", .sover = 1 },
     .{ .name = "ld", .sover = 2 },
-- 
cgit v1.2.3