Open GoogleCodeExporter opened 9 years ago
http://buildroot.busybox.net/ doesn't load...
How can I get a mips64 Linux system to test this? With QEMU/KVM perhaps?
Original comment by thestig@chromium.org
on 10 Jul 2014 at 2:46
Hello, and thanks for your answer.
The buildroot website works fine for me. Anyway, this is the command to clone
the repository:
git clone git://git.buildroot.net/buildroot
or if you're behind a firewall blocking git:
git clone git://git.buildroot.net/buildroot
Buildroot will crosscompile, so you don't need a MIPS64 Linux system to
reproduce the failure. Buildroot is a tool to generate embedded Linux systems
by crosscompiling, and let you choose the target architecture. So, the steps to
reproduce the failures are:
-clone the Buildroot repository
-type "make menuconfig" and go to the "Target options" menu.
-choose "MIPS64 Little Endian" target architecture.
-choose "n64" target ABI
-go to the "Toolchain" menu and select "External toolchain" type.
(that will download a toolchain, so you will save time by not building a
toolchain to generate code for your selected target)
-go to "Target packages" -> "Debugging, profiling and benchmark" and select the
"google-breakpad" package.
-exit and save your configuration
-type "make"
And just to answer your question. Yes, QEMU/KVM works if you want to emulate a
MIPS64 Linux system.
Original comment by per...@gmail.com
on 10 Jul 2014 at 9:12
Can you try the attached patch?
Original comment by thestig@chromium.org
on 11 Jul 2014 at 7:12
Attachments:
[deleted comment]
Hello,
the patch you attached doesn't work directly on Buildroot, so I needed
to rewrite it. I have attached the new patch just in case you want to
review it. I think I haven't done any mistake.
It fails with the same problem. I have attached the full build log.
Original comment by per...@gmail.com
on 11 Jul 2014 at 8:09
Attachments:
Actually, this problem went away. You have different problems in the comment 5
build.log, which are outside of the scope of this bug. (Back to Breakpad...)
Original comment by thestig@chromium.org
on 11 Jul 2014 at 6:51
Original comment by vapier@chromium.org
on 16 Jan 2015 at 1:58
Is this still a valid issue or should we close it?
Original comment by pet...@mips.com
on 24 Feb 2015 at 12:37
Original issue reported on code.google.com by
per...@gmail.com
on 8 Jul 2014 at 3:46Attachments: