When I tested a ebuild which needed boost 1.35-r2 boost chrashed. Reproducible: Always Steps to Reproduce: 1. emerge boost 1.35-r2 2. 3. Actual Results: Boots chrashed. Expected Results: Boots will compile well
Created attachment 210685 [details] emerge --info
Created attachment 210687 [details] build log
Make sure you don't run out of memory.
(In reply to comment #3) > Make sure you don't run out of memory. > Oke, I have tried it on a machine with 532 MB memory. Today I will try it at a machine with 1G memory. Roelof
(In reply to comment #4) > (In reply to comment #3) > > Make sure you don't run out of memory. > > > > > Oke, > I have tried it on a machine with 532 MB memory. > Today I will try it at a machine with 1G memory. > > Roelof I tried it on a machine with 1G memory but still the same error. Roelof >
Well, that still doesn't tell us if you are running out of memory. You might be hitting a gcc bug. Any reason your are not using latest stable version of boost and gcc?
(In reply to comment #6) > Well, that still doesn't tell us if you are running out of memory. You might be > hitting a gcc bug. Any reason your are not using latest stable version of boost > and gcc? > No, I also tried boost-1.35r5 same problem. What are according to you the last stable versions ? Roelof
(In reply to comment #7) > (In reply to comment #6) > > Well, that still doesn't tell us if you are running out of memory. You might be > > hitting a gcc bug. Any reason your are not using latest stable version of boost > > and gcc? > > > > No, > > I also tried boost-1.35r5 same problem. > What are according to you the last stable versions ? > > Roelof > Another question : how can I check if there is a memory problem ? Roelof
Well, not(In reply to comment #8) > > I also tried boost-1.35r5 same problem. > > What are according to you the last stable versions ? dev-libs/boost-1.35.0-r5 sys-devel/gcc-4.3.4 > Another question : how can I check if there is a memory problem ? I don't have another idea than monitoring the memory usage, sorry. You try with MAKEOPTS="-j1". Btw, happens the error always at the same file? In this case you could go into the build directory and run the command manually. Monitoring memory consumption should be easier then.
(In reply to comment #9) > Well, not(In reply to comment #8) > > > I also tried boost-1.35r5 same problem. > > > What are according to you the last stable versions ? > dev-libs/boost-1.35.0-r5 > sys-devel/gcc-4.3.4 > > > Another question : how can I check if there is a memory problem ? > I don't have another idea than monitoring the memory usage, sorry. > > You try with MAKEOPTS="-j1". Btw, happens the error always at the same file? In > this case you could go into the build directory and run the command manually. > Monitoring memory consumption should be easier then. > With makeopts="-j1" boost compiled. I see no memory problems but I can see that my cpu works a lot of time at 100% with a load of 1.2 to 1.7 according to top. Roelof
(In reply to comment #10) > (In reply to comment #9) > > Well, not(In reply to comment #8) > > > > I also tried boost-1.35r5 same problem. > > > > What are according to you the last stable versions ? > > dev-libs/boost-1.35.0-r5 > > sys-devel/gcc-4.3.4 > > > > > Another question : how can I check if there is a memory problem ? > > I don't have another idea than monitoring the memory usage, sorry. > > > > You try with MAKEOPTS="-j1". Btw, happens the error always at the same file? In > > this case you could go into the build directory and run the command manually. > > Monitoring memory consumption should be easier then. > > > > With makeopts="-j1" boost compiled. I see no memory problems but I can see that > my cpu works a lot of time at 100% with a load of 1.2 to 1.7 according to top. > > Roelof > You can close this bug. I think the problem is that I test my build ebuilds in vmware with a found appliance and this don't work. I can see that almost every ebuild takes 100% of the cpu. Roelof
Thanks for getting it yourself :)
