Hello, on Freitag, 21. Dezember 2007, Carsten Schoene wrote:

%configure || cat config.log

in your .spec file and the output will be printed to the output log

Right, but I consider this a workaround. The better solution would be to enhance %configure - it should "cat config.log" automatically on failed builds. @SUSE team: Comments? Objections? Who will implement it? ;-) Regards, Christian Boltz -- *** Error: Typical Friday typo! Please do quit working or correct it. [Robert Felber in postfixbuch-users] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

Yes, that certainly helps, but whenever I mess around with the .spec file the whole project gets rebuild, which is not really what I want. But thanks for the hint. An Automatism as proposed by Christian Boltz below would be a nicer idea and help everyone immediately. Thanks, Christof Carsten Schoene wrote:

you may try:

%configure || cat config.log

in your .spec file and the output will be printed to the output log

Christof Hanke schrieb:

...

Hi,

...

don't know if this has been asked before, but it'd be nice to be able to retrieve the config.log in case of a failed configure on an architecture one does not have.

...

Ciao,

...

Christof --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

--------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

* Marcus Rueckert [2008-01-07 23:23]:

On 2007-12-21 01:02:39 +0200, Christof Hanke wrote:

...

don't know if this has been asked before, but it'd be nice to be able to retrieve the config.log in case of a failed configure on an architecture one does not have.

build locally with osc build. osc help build for more

Basically I agree, but one problem with this is that "osc build" doesn't support link'd builds. Bernhard --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org

* Adrian Schröter [2008-01-08 08:47]:

On Tuesday 08 January 2008 08:29:44 wrote Bernhard Walle:

...

* Marcus Rueckert [2008-01-07 23:23]:

...

On 2007-12-21 01:02:39 +0200, Christof Hanke wrote:

...

don't know if this has been asked before, but it'd be nice to be able to retrieve the config.log in case of a failed configure on an architecture one does not have.

build locally with osc build. osc help build for more

Basically I agree, but one problem with this is that "osc build" doesn't support link'd builds.

yes, yes, but adding a workaround instead doing a bugfix do not make sense ;)

One point might be 64 bit errors. People that have 32 bit machines cannot run "osc build" to find 64-bit specific configure problems. But basically I agree that we should encourage people to do local builds to find out build errors instead of using the server again and again which is tedious for the user and produces unnecessary server load ... Bernhard -- Bernhard Walle , Architecture Maintenance II SUSE LINUX Products GmbH, Nürnberg, Germany GF: Markus Rex, HRB 16746 (AG Nürnberg) OpenPGP: F61F 34CC 09CA FB82 C9F6 BA4B 8865 3696 DDAF 6454 --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-buildservice+help@opensuse.org