From unknown Thu Mar 28 11:25:50 2024 X-Loop: git-admin@x2go.org Subject: Bug#84: Hardcoded -O3 in CFLAGS Reply-To: Jan Engelhardt , 84@bugs.x2go.org Resent-From: Jan Engelhardt Resent-To: x2go-dev@lists.berlios.de Resent-CC: X2Go Developers X-Loop: git-admin@x2go.org Resent-Date: Wed, 09 Jan 2013 15:33:02 +0000 Resent-Message-ID: Resent-Sender: git-admin@x2go.org X-X2Go-PR-Message: followup 84 X-X2Go-PR-Package: nx-libs X-X2Go-PR-Keywords: Received: via spool by 84-submit@bugs.x2go.org id=B84.135774497613873 (code B ref 84); Wed, 09 Jan 2013 15:33:02 +0000 Received: (at 84) by bugs.x2go.org; 9 Jan 2013 15:22:56 +0000 Received: from ares07.inai.de (ares07.inai.de [5.9.24.206]) by ymir (Postfix) with ESMTPS id 0E34D5DB0A for <84@bugs.x2go.org>; Wed, 9 Jan 2013 16:22:56 +0100 (CET) Received: by ares07.inai.de (Postfix, from userid 25121) id E161A96A06B1; Wed, 9 Jan 2013 16:22:55 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by ares07.inai.de (Postfix) with ESMTP id AF6F496A068E; Wed, 9 Jan 2013 16:22:55 +0100 (CET) Date: Wed, 9 Jan 2013 16:22:55 +0100 (CET) From: Jan Engelhardt To: Mike Gabriel cc: 84@bugs.x2go.org, Reinhard Tartler , Bernard Cafarelli In-Reply-To: <20130109161041.118432fsrumy2jch@mail.das-netzwerkteam.de> Message-ID: References: <20130109010011.4f92023b@enterprise.cafarelli.fr> <20130109161041.118432fsrumy2jch@mail.das-netzwerkteam.de> User-Agent: Alpine 2.01 (LNX 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Wednesday 2013-01-09 16:10, Mike Gabriel wrote: > > All kind of flags are hard-coded in linux.cf in nx-X11/cf/ (I think). You may > know imake better then I do. If you could take another look at it, that would > be awesome. > > Note: LDFLAGS appear to be named LDOPTIONS in nx-X11. > > Note, that nxcomp, nxcompshad and nxcompext are configured and built from > within nx-X11/programs/Xserver/Makefile.in (IIRC, might be the Makfile.in one > level up). So the nx* builds are prepared by imake. I guess the only way to > address it is to teach imake to let through *FLAGS. > > The nx-X11 build process is a bummer..., I agree with that. Any help and > improvement is really appreciated. Can we split nxcomp, nxcompshad, nxcompext and nxproxy into separate tarballs in any way? After all, they are "just" addons to an existing (X11|nx-libs) tree that gets installed as well and which looks usable.