mingw-cross-env-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] x264 build fails


From: Volker Grabsch
Subject: Re: [Mingw-cross-env-list] x264 build fails
Date: Mon, 4 Oct 2010 14:09:21 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

Tony Theodore <address@hidden> schrieb:
> On 4 October 2010 08:29, Mark Brand <address@hidden> wrote:
> >
> > I am wondering how worried we should be about this type of phenomenon. If
> > the symbol hadn't been changed, linking to the old version of the library
> > might have succeeded and gone unnoticed.
[...]
> I'm thinking this isn't a general problem, but you're right in that it
> would be mostly hidden if it was. The only solution (apart from make
> clean) would be some sort of uninstall functionality that's been
> discouraged before.

I think that this is a very special behaviour that doesn't deserve a
general solution. Every package should be prepared for being reinstalled
over an old version, as this is what usually happens if people build it
manually.

> In this case 'rm' is probably the best short term solution.

Is it possible have an "rm" command that is a long-term solution?
Something like this:

     rm '$(PREFIX)/$(TARGET)'/lib/libx*.a

but with less collateral damage?

> We could disable the .exe build with some sort of 'bin_PROGRAMS= ',

This is always a good idea.

> but it's a free link test;

Maybe, but our explicit test scripts are usually a more reliable
_and_ faster way of testing linking. And our own tests ensure that
linking is always possible with a certain simple command - rather
than some (possibly complicated) autogenerated command of the
package's build system.


Greets,
Volker

-- 
Volker Grabsch
---<<(())>>---



reply via email to

[Prev in Thread] Current Thread [Next in Thread]