From mint-bounce@lists.fishpool.fi Tue Jan 12 17:13:33 2010 X-Virus-Scanned: Debian amavisd-new at pp.htv.fi From: Eero Tamminen Organization: Koti To: mint@lists.fishpool.fi Subject: Re: [MiNT] Mikro GCC 4.4.2 build Library Paths Date: Wed, 13 Jan 2010 00:09:07 +0200 User-Agent: KMail/1.9.9 Cc: Paul Wratt References: <4B48AFAF.3090202@atari-source.org> <201001120125.28070.oak@helsinkinet.fi> <11a6f2b11001111534i7df5f2e5p950fa2ddeb163ad7@mail.gmail.com> In-Reply-To: <11a6f2b11001111534i7df5f2e5p950fa2ddeb163ad7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <201001130009.07272.oak@helsinkinet.fi> X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: oak@helsinkinet.fi Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Hi, On Tuesday 12 January 2010, Paul Wratt wrote: > On Tue, Jan 12, 2010 at 10:25 AM, Eero Tamminen > > One reason why they're evil is that at least in in systems using shared > > libraries, they cause also indirect dependencies being directly linked > > into the binary which means that the directly dependencies dependencies > > cannot be remove/changed. > > > > This is bad from package management point of view on such systems. > > I'm not sure how much of a problem this could be on a system using > > static libs. > > That does imply the possibility of HUGE binaries, outside of the > normal debug hugeness. When building static binaries, compiler skips unreferenced objects. I was thinking possible problem with static libs being more about .la files in dev packages trying to link obsolete/non-existing indirect libraries, but that should be much rarer than the issue on systems like Debian which have large amount of shared libs and deps between them. > Is there any way to check for these? On Linux? Yes. - Eero