Rene Rebe wrote:
Hi,

your work on mips64 came back to my mind. I wonder how well your build and use 
goes? Looking forward to hear about your experience.
I have a snapshot of the trunk from Sept. 2009 that is working very well on our Mips based Cavium Octeon machine, but it is not a 64 bit muilit-lib build. The userspace progs were built as mips32-r2 . The T2 toolchain & user space binaries were built on a Suse 9.2 machine, but then copied over to one of our production build servers, and overlays of custom kernel & 64-bit libs & drivers were added for the embedded linux image for one of our products. This version is undergoing testing, and we will use it for our next release.

I have continued working on the current trunk, but since the switch to GCC 4.4 and the newest glibc, I can no longer build it on Suse 9.2, so I have switched the T2 build server over to Ubuntu 9.10. I can now build almost all of the generic minimal target as a single lib Mips64 N32 or N64 ABI, but the full muililib build is still failing. I have been unable to fully test the current trunk builds on my hardware yet, because our production build servers are too old, and can't run the latest T2 crosstools on them because the host's glibc is too old.

I have been working on setting up a newer build server where I can build the final product image, but that is on the back burner for now due to other pressing tasks. Once I am able to test every thing I will submit all the patches for all changes that I have made. I will try to send out some of the "low risk" patches shortly. along with a better status update.

 If you feel comfortable with T2 we could also add you to the list of 
developers at:

  http://www.t2-project.org/developer/people.html

I would be honored to be included in the list.
Here is my info:

Jan Rovins
Date of birth: 19 November 1954, Nationality: USA
Location: Mt. Laurel, New Jersey (USA), Occupation: Software Engineer @ Adax Inc.
Main field: embedded work, ports  MIPS64
CPUs in use: PowerPC, MIPS64, ARM, x86
Mail: janr [at] adax.com



Jan
René

On Mar 17, 2010, at 8:07 PM, Jan Rovins wrote:

All,

Got the following error when cross building strace for mips64,

The attached patch fixes this, the patch should go upstream too.

Jan



make[1]: Entering directory 
`/opt/T2/t2-trunk/src.strace.GW-Octeon-Pure64.20100317.141859.25474.ubuntu1/strace-4.5.19'
mips64-octeon-linux-gnu-gcc -DHAVE_CONFIG_H -I. -Ilinux/mips -I./linux/mips 
-Ilinux -I./linux   -Wall -g -O2 -MT strace.o -MD -MP -MF .deps/strace.Tpo -c 
-o strace.o strace.c
mips64-octeon-linux-gnu-gcc -DHAVE_CONFIG_H -I. -Ilinux/mips -I./linux/mips 
-Ilinux -I./linux   -Wall -g -O2 -MT syscall.o -MD -MP -MF .deps/syscall.Tpo -c 
-o syscall.o syscall.c
mips64-octeon-linux-gnu-gcc -DHAVE_CONFIG_H -I. -Ilinux/mips -I./linux/mips 
-Ilinux -I./linux   -Wall -g -O2 -MT count.o -MD -MP -MF .deps/count.Tpo -c -o 
count.o count.c
mips64-octeon-linux-gnu-gcc -DHAVE_CONFIG_H -I. -Ilinux/mips -I./linux/mips 
-Ilinux -I./linux   -Wall -g -O2 -MT util.o -MD -MP -MF .deps/util.Tpo -c -o 
util.o util.c
syscall.c: In function 'syscall_enter':
syscall.c:2038: error: 'pid' undeclared (first use in this function)
syscall.c:2038: error: (Each undeclared identifier is reported only once
syscall.c:2038: error: for each function it appears in.)
mv -f .deps/count.Tpo .deps/count.Po
make[1]: *** [syscall.o] Error 1
make[1]: *** Waiting for unfinished jobs....

diff -ur strace-4.5.19/syscall.c strace-4.5.19.fix/syscall.c
--- strace-4.5.19/syscall.c     2009-10-12 15:54:21.000000000 -0400
+++ strace-4.5.19.fix/syscall.c 2010-03-17 14:47:17.000000000 -0400
@@ -2035,7 +2035,7 @@
                else
                        nargs = tcp->u_nargs = MAX_ARGS;

-               if (ptrace (PTRACE_GETREGS, pid, NULL, (long) &regs) < 0)
+               if (ptrace (PTRACE_GETREGS, tcp->pid, NULL, (long) &regs) < 0)
                        return -1;

                for(i = 0; i < nargs; i++) {
----------------------------------------------------------- If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2


----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2

Reply via email to