21 Dec
2007
21 Dec
'07
12:02 a.m.
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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
8 Jan
8 Jan
9:25 a.m.
Marcus Rueckert wrote:
On 2007-12-21 01:02:39 +0200, Christof Hanke wrote:
Well, I can't build 64bit binaries on my 32bit laptop, can I ?
To be honest, I've never tried.
But I'm happy with the solutions provided above.
Thanks,
Christof
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
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
9:14 a.m.
* Adrian Schröter <adrian(a)suse.de> [2008-01-08 08:47]:
On Tuesday 08 January 2008 08:29:44 wrote Bernhard
Walle:
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 <bwalle(a)suse.de>de>, 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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
* Marcus Rueckert <darix(a)opensu.se>
[2008-01-07 23:23]:
yes, yes, but adding a workaround instead doing a bugfix do not make sense ;) On 2007-12-21 01:02:39 +0200, Christof Hanke
wrote:
Basically I agree, but one problem with this is that "osc build"
doesn't support link'd builds. 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 
8:47 a.m.
On Tuesday 08 January 2008 08:29:44 wrote Bernhard Walle:
* Marcus Rueckert <darix(a)opensu.se> [2008-01-07
23:23]:
yes, yes, but adding a workaround instead doing a bugfix do not make sense ;)
(if we start to provide config.log, questions will come up for other files to
store, so I would like to be strict and to add support for local build of
_link files instead (was part of my yesterdays mail about missing features
for next milestone)).
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian(a)suse.de
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
On 2007-12-21 01:02:39 +0200, Christof Hanke
wrote:
Basically I agree, but one problem with this is that "osc build"
doesn't support link'd builds. 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
8:29 a.m.
* Marcus Rueckert <darix(a)opensu.se> [2008-01-07 23:23]:
On 2007-12-21 01:02:39 +0200, Christof Hanke wrote:
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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
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 
7 Jan
7 Jan
11:23 p.m.
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
darix
--
openSUSE - SUSE Linux is my linux
openSUSE is good for you
www.opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
31 Dec
31 Dec
9:34 a.m.
Christian Boltz wrote:
Hello,
on Freitag, 21. Dezember 2007, Carsten Schoene wrote:
Agreed.
%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.
I'm afraid that this would make it worse in many cases. A build log
whose last line is "configure: error: gtk2 header files not found" is
pretty easy to understand, the same message hidden among 1500 lines of
debug output isn't.
Perhaps the config.log could be stored somewhere as part of the result,
just like a successful build stores *.rpm :)
Michal
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
21 Dec
21 Dec
11:14 p.m.
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:
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
9:15 p.m.
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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
4:15 p.m.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org
iD8DBQFHa9iv6NfbfHY52TsRAgjtAJ9JxGO9ohJ8323xwd5DIhBt2lRekgCfRZPT
7trWpXYp5omNbH2eSuhm+GE=
=vlgb
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe(a)opensuse.org
For additional commands, e-mail: opensuse-buildservice+help(a)opensuse.org
4765
days inactive
4784
days old
buildservice@lists.opensuse.org
9 comments
7 participants
participants (7)
-
Adrian Schröter -
Bernhard Walle -
Carsten Schoene -
Christian Boltz -
Christof Hanke -
Marcus Rueckert -
Michal Marek