On Thu, Jul 2, 2009 at 9:30 AM, Colin Walterswalt...@verbum.org wrote:
On Thu, Jul 2, 2009 at 9:20 AM, Peter Robinsonpbrobin...@gmail.com wrote:
Interestingly with -ggdb it builds fine with out without -O0.
That makes it a lot more likely to be a compiler flaw (though not guaranteed).
Of
Hi All,
I've having some issues with a PPC64 build and was wondering if
someone a bit more ppc savy could have a poke. It builds fine on x86
and ppc32. git head also has the same issue as the current stable
release so unfortunately that doesn't help much.
PPC64 build
On Thu, Jul 2, 2009 at 6:29 AM, Peter Robinsonpbrobin...@gmail.com wrote:
Hi All,
I've having some issues with a PPC64 build and was wondering if
someone a bit more ppc savy could have a poke.
A backtrace would be really useful here (remember to build with -ggdb
-O0 for extra usefulness).
On Thu, Jul 2, 2009 at 11:49 AM, Colin Walterswalt...@verbum.org wrote:
On Thu, Jul 2, 2009 at 6:29 AM, Peter Robinsonpbrobin...@gmail.com wrote:
Hi All,
I've having some issues with a PPC64 build and was wondering if
someone a bit more ppc savy could have a poke.
A backtrace would be
On Thu, Jul 2, 2009 at 9:20 AM, Peter Robinsonpbrobin...@gmail.com wrote:
Interestingly with -ggdb it builds fine with out without -O0.
That makes it a lot more likely to be a compiler flaw (though not guaranteed).
Does 'make check' pass in the source tree you built with -O0?
A backtrace
Interestingly with -ggdb it builds fine with out without -O0.
That makes it a lot more likely to be a compiler flaw (though not guaranteed).
Does 'make check' pass in the source tree you built with -O0?
A backtrace would still be great though. Try setting DEBUG=fcatch in
the environment.
Peter Robinson wrote:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1449113
Unrelated to this issue, but please use make V=1 so we see the actual
build command lines in the build.log (see the thread about the new
automake).
Kevin Kofler
--
fedora-devel-list mailing list
http://koji.fedoraproject.org/koji/taskinfo?taskID=1449113
Unrelated to this issue, but please use make V=1 so we see the actual
build command lines in the build.log (see the thread about the new
automake).
With V=1
http://koji.fedoraproject.org/koji/getfile?taskID=1450335name=build.log
On Thu, 2009-07-02 at 16:28 +0100, Peter Robinson wrote:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1449113
Unrelated to this issue, but please use make V=1 so we see the actual
build command lines in the build.log (see the thread about the new
automake).
With V=1
Peter Robinson wrote:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1449113
Unrelated to this issue, but please use make V=1 so we see the actual
build command lines in the build.log (see the thread about the new
automake).
With V=1
http://koji.fedoraproject.org/koji/taskinfo?taskID=1449113
Unrelated to this issue, but please use make V=1 so we see the actual
build command lines in the build.log (see the thread about the new
automake).
With V=1
http://koji.fedoraproject.org/koji/getfile?taskID=1450335name=build.log
http://koji.fedoraproject.org/koji/taskinfo?taskID=1449113
Unrelated to this issue, but please use make V=1 so we see the actual
build command lines in the build.log (see the thread about the new
automake).
With V=1
Peter Robinson wrote:
http://koji.fedoraproject.org/koji/taskinfo?taskID=1449113
Unrelated to this issue, but please use make V=1 so we see the actual
build command lines in the build.log (see the thread about the new
automake).
With V=1
On Thu, Jul 02, 2009 at 06:30:50PM +0200, Till Maas wrote:
On Thu July 2 2009, Josh Boyer wrote:
On Thu, Jul 02, 2009 at 04:51:50PM +0100, Peter Robinson wrote:
No I didn't. Are the details published anywhere of how to request access?
I'm working on it. Basically, email dwmw2 or me an ssh
14 matches
Mail list logo
