Hi Christos,
Christos Zoulas wrote:
On Oct 6, 9:18pm, riccardo.mott...@libero.it (Riccardo Mottola) wrote:
-- Subject: Re: build broken -groff and c++ compiler
| Hi Christos,
|
| Thanks.
|
| Christos Zoulas wrote:
| On Oct 6, 2:21pm, riccardo.mott...@libero.it (Riccardo Mottola) wrote
Christos Zoulas wrote:
On Oct 6, 9:18pm, riccardo.mott...@libero.it (Riccardo Mottola) wrote:
-- Subject: Re: build broken -groff and c++ compiler
| Hi Christos,
|
| Thanks.
|
| Christos Zoulas wrote:
| On Oct 6, 2:21pm, riccardo.mott...@libero.it (Riccardo Mottola) wrote:
| -- Subject: Re
Hi,
Christos Zoulas wrote:
#include iostream
int
main(int argc, char *argv[])
{
std::cerr Hello World std::endl;
return 0;
}
it compiles, but fails:
grid$ g++ hello.cc
grid$ ./a.out
[1] Segmentation fault (core dumped) ./a.out
grid$ ldd a.out
a.out:
-lstdc++.7 =
In article 5252c26a.6040...@libero.it,
Riccardo Mottola riccardo.mott...@libero.it wrote:
PS: building gcc naively as I proposed, fails when compiling libm...
The compiler has nothing to do with this failure. It is all binutils.
The only reason I can think of that this is happening is that your
Hi,
Christos Zoulas wrote:
In article5252c26a.6040...@libero.it,
Riccardo Mottolariccardo.mott...@libero.it wrote:
PS: building gcc naively as I proposed, fails when compiling libm...
The compiler has nothing to do with this failure. It is all binutils.
The only reason I can think of that
Hi,
On 10/07/2013 08:23 PM, Aran Clauson wrote:
All,
I have the same problem. Following the Riccardo's lead, I removed all of the
objdirs in /src/external/gpl3/binults. I changed in to the lib directory and
executed the following:
$ make cleandir make obj make dependall USETOOLS=never
Hi,
Nick Hudson wrote:
On 10/04/13 13:39, Riccardo Mottola wrote:
Hi,
is the current build still expected to be broken?
no, but your system is hosed from an earlier problem... the easiest
fix is probably downloading
In article 52509454.9060...@libero.it,
Riccardo Mottola riccardo.mott...@libero.it wrote:
Hi,
Nick Hudson wrote:
On 10/04/13 13:39, Riccardo Mottola wrote:
Hi,
is the current build still expected to be broken?
no, but your system is hosed from an earlier problem... the easiest
fix is
