From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/14241 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Reinoud Koornstra Newsgroups: gmane.linux.lib.musl.general Subject: Re: where to find musl-gcc wrapper script Date: Tue, 18 Jun 2019 11:27:51 -0700 Message-ID: References: <20190617233023.GK1506@brightrain.aerifal.cx> <20190618024755.GM1506@brightrain.aerifal.cx> <20190618174926.GN1506@brightrain.aerifal.cx> Reply-To: musl@lists.openwall.com Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="93442"; mail-complaints-to="usenet@blaine.gmane.org" Cc: musl@lists.openwall.com To: Rich Felker Original-X-From: musl-return-14257-gllmg-musl=m.gmane.org@lists.openwall.com Tue Jun 18 20:28:18 2019 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.89) (envelope-from ) id 1hdIqA-000OD2-3r for gllmg-musl@m.gmane.org; Tue, 18 Jun 2019 20:28:18 +0200 Original-Received: (qmail 22015 invoked by uid 550); 18 Jun 2019 18:28:15 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 21997 invoked from network); 18 Jun 2019 18:28:15 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0RCK8LNsCJiiLunf3CThMBm9SppYJpdylywI/D309MQ=; b=M33d4s6ZflbklNqA6YmBB+Eo8oynUIq+z9u8gfsOnDCguJFZymzk+ckWeCLOE29iUI VGIBxq33XxXBgtXleSB+fcianTvUrH71HfKjRsMyVeXisvsFa1TA3RgUGziyiiWY+e0U /L84nbOqkGr34t0kcZCWPlJnrTCEM70l94p1lmZXUhqE9BftD+PNcREQJuCdmqY3WTh+ FO/fh9byr7vAlT6GN7zrc5i4LlPbN62t5b4cwoEJvGmXz/Ce6bgxrQav+D2dcaRRXKJE zDJnPhziw+YxsUsN77+hOqkSBvUhpR3jtIju2UuyTOSQ7n0vmYAseTUo5kN8cx6asPYV GfZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0RCK8LNsCJiiLunf3CThMBm9SppYJpdylywI/D309MQ=; b=ruxl8Eyv6qAjSMLXC1w3EmffRmZuSsXMBJguDfh7W7KL0wYJXOFI9OZCktdzsEC0/5 BaL/ZAREPhgx1qDUM357fqf0T7BBDTcFr4d2yt/vM6O+9KmfIwtNO9o8kME/szdBk4H8 aON3kfr2gxALjfmQA1/0cwx8DzdyZutTbbCxRC3mwgqHevjUK3sHNBzN4llV+f/Il9Sj IJ/NEKJveaDGRrK2T72C+Ms/4ZNTXozLRLl553/13jJNZtOPKGbBDKCJtnnQm7+YQWVe p/IQxIVcUEBlHFLLcbTxyT1kMQcXE/1IuX2GvlEonVRQZ8AqUY1IoYfpxCtq+ybp42o7 Z8tw== X-Gm-Message-State: APjAAAV8WI+X2M/jas1B+XyhCfPE5Sbi25umR3du/pJ5h3ansXGZ55eg WcJaID1DPILJQxQ271P+Ydnr0y3bQuzbFeQCxsc= X-Google-Smtp-Source: APXvYqw2rYgMRxFOnQNBS5h1a8N2O7haGv98rZ7nWwxnPznA9q52KZJ+1stQpCo0ufbc2FldMb3Y8//6YNIUBsIGCKk= X-Received: by 2002:a9d:6a19:: with SMTP id g25mr4044125otn.77.1560882482998; Tue, 18 Jun 2019 11:28:02 -0700 (PDT) In-Reply-To: <20190618174926.GN1506@brightrain.aerifal.cx> Xref: news.gmane.org gmane.linux.lib.musl.general:14241 Archived-At: On Tue, Jun 18, 2019 at 10:49 AM Rich Felker wrote: > > On Mon, Jun 17, 2019 at 08:28:12PM -0700, Reinoud Koornstra wrote: > > On Mon, Jun 17, 2019, 7:47 PM Rich Felker wrote: > > > > > On Mon, Jun 17, 2019 at 07:30:00PM -0700, Reinoud Koornstra wrote: > > > > Ok the wrapper is included in the musl library itself in the obj > > > directory. > > > > > > Yes, or installed in $prefix/bin if you install. If you don't install > > > it won't be able to find its spec file. > > > > > > > c++ isn't supported yet? > > > > > > Right. Nobody I'm aware of understands the details of this, but > > > apparently either GCC's actual C++ headers or its "precompiled header" > > > versions of them pull in a bunch of stuff from glibc, and then it > > > breaks when you try to reuse them with musl. It's probably not that > > > hard to figure out the root cause and maybe even make it work, but > > > nobody has done it and interest is low because it's still a big hack > > > compared to just building a proper cross toolchain. > > > > > > > Currently I configure with CC=musl-gcc > > > > CFLAGS="-I/home/me/MUSL/include" LDFLAGS="-L/home/me/lib" ./configure > > > > the final g++ comand also add -lrt, need more changes for this to work? > > > > > > If you do that you're compiling against musl's headers but then > > > linking against glibc, which is going to make a huge broken mess. > > > > Yes, I noticed, so how can I force it to link against musl as well? > > You can't, because things already went wrong as soon as you compiled > against glibc's C++ headers using the glibc-based host g++. > > > > If you need C++, you really should just build a cross toolchain with > > > musl-cross-make. It's as simple as clining the mcm repo and running > > > "make TARGET=x86_64-linux-musl OUTPUT=/some/dir install" -- it will > > > download, check hashes on, and patch all the components you need and > > > give you a clean self-contained cross toolchain in the OUTPUT dir. > > > > > > > Also done that, in that case should I just use the compiled gcc as cc? > > You can pass the resulting x86_64-linux-musl-gcc and > x86_64-linux-musl-g++ as CC and CXX, but for software using the > standard tuple prefix conventions, you'd tell it you're cross > compiling for x86_64-linux-musl (e.g. by passing > --host=x86_64-linux-musl to configure) and it would automatically pick > them up as long as they're in your PATH (which you probably need to > add them to, e.g. PATH=$PATH:/path/to/mcm/output/bin). This is better > if the software has reason to need to know it's being cross compiled, > or if it uses other utilities like ar, ranlib, direct use of ld, etc. > in the build process, since it will pick up the right ones from the > cross toolchain. Ok, this seemed to have worked nicely. Question, it does add -lrt in the end, do I need this in musl or is it build in libc? Also, is there a way to verify everything linked nicely by the musl-ld? Thanks, Reinoud. > > Rich