From jrytoung at gmail.com Mon Nov 10 12:38:44 2008 From: jrytoung at gmail.com (Jerry Toung) Date: Mon Nov 10 12:38:51 2008 Subject: buildworld for octeon, HEAD Message-ID: <86068e730811101238m3dbb9ab6w754e5a929017d964@mail.gmail.com> Hello list, could someone help or direct which way to go, to get rid of these error messages? I am trying complete buildworld for octeon with code from HEAD. The build is currently failing while building the C library. #mips64-octeon-linux-gnu-gcc -v Using built-in specs. Target: mips64-octeon-linux-gnu Configured with: ../src/configure --target=mips64-octeon-linux-gnu --prefix=/usr/local/Cavium_Networks/toolchain/tools --disable-sim --enable-symvers=gnu --enable-__cxa_atexit --enable-languages=c,c++ --with-local-prefix=/usr/local/Cavium_Networks/toolchain/tools/mips64-octeon-linux-gnu/sys-root --with-sysroot Thread model: posix gcc version 4.1.2 (Cavium Networks Version: 1_7_2, build 50) -------------------------------------------------------------- >>> stage 4.2: building libraries -------------------------------------------------------------- mips64-octeon-linux-gnu-gcc :cc -O2 -pipe -fno-strict-aliasing -pipe -U linux -U __linux -U __linux__ -I/home/builduser/HEAD8/src/../obj32/usr/include -L /home/tester/HEAD8/src/../obj32/usr/lib -mabi=32 -fno-builtin -nostdinc -nostdlib -G0 -march=mips32r2 -D__mips_o32 -D__FreeBSD__=5 -ggdb -msoft-float -I/home/tester/HEAD8/src/lib/libc/include -I/home/tester/HEAD8/src/lib/libc/../../include -I/home/tester/HEAD8/src/lib/libc/mips -DSOFTFLOAT -D__DBINTERFACE_PRIVATE -I/home/tester/HEAD8/src/lib/libc/../../contrib/gdtoa -DINET6 -I/home/tester/HEAD8/src/../obj32/mips/home/tester/HEAD8/src/lib/libc -I/home/tester/HEAD8/src/lib/libc/resolv -DPOSIX_MISTAKE -I/home/tester/HEAD8/src/lib/libc/locale -DBROKEN_DES -DPORTMAP -DDES_BUILTIN -I/home/tester/HEAD8/src/lib/libc/rpc -DNS_CACHING -DSYMBOL_VERSIONING -c /home/tester/HEAD8/src/lib/libc/mips/gen/_setjmp.S mips64-octeon-linux-gnu-gcc :/home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S: Assembler messages: /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:68: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:69: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:70: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:71: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:72: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:73: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:74: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:75: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:76: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:77: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:78: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:82: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:94: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:95: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:98: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:99: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:100: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:101: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:102: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:103: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:104: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:105: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:106: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:107: Error: expression too complex /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:113: Warning: No .cprestore pseudo-op used in PIC code /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:115: Warning: No .cprestore pseudo-op used in PIC code *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 From imp at bsdimp.com Mon Nov 10 13:03:10 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Mon Nov 10 13:03:16 2008 Subject: buildworld for octeon, HEAD In-Reply-To: <86068e730811101238m3dbb9ab6w754e5a929017d964@mail.gmail.com> References: <86068e730811101238m3dbb9ab6w754e5a929017d964@mail.gmail.com> Message-ID: <20081110.140113.-262812654.imp@bsdimp.com> In message: <86068e730811101238m3dbb9ab6w754e5a929017d964@mail.gmail.com> "Jerry Toung" writes: : Hello list, : could someone help or direct which way to go, to get rid of these error : messages? : I am trying complete buildworld for octeon with code from HEAD. The build is : currently failing while building the : C library. Where did you get your octeon sources? The ones that I have, that are integrated into the tree, aren't released yet... They also use the in-tree tools, rather than the octeon ones. Warner : #mips64-octeon-linux-gnu-gcc -v : Using built-in specs. : Target: mips64-octeon-linux-gnu : Configured with: ../src/configure --target=mips64-octeon-linux-gnu : --prefix=/usr/local/Cavium_Networks/toolchain/tools --disable-sim : --enable-symvers=gnu --enable-__cxa_atexit --enable-languages=c,c++ : --with-local-prefix=/usr/local/Cavium_Networks/toolchain/tools/mips64-octeon-linux-gnu/sys-root : --with-sysroot : Thread model: posix : gcc version 4.1.2 (Cavium Networks Version: 1_7_2, build 50) : : : -------------------------------------------------------------- : >>> stage 4.2: building libraries : -------------------------------------------------------------- : : mips64-octeon-linux-gnu-gcc :cc -O2 -pipe -fno-strict-aliasing -pipe -U : linux -U __linux -U __linux__ : -I/home/builduser/HEAD8/src/../obj32/usr/include -L : /home/tester/HEAD8/src/../obj32/usr/lib -mabi=32 -fno-builtin -nostdinc : -nostdlib -G0 -march=mips32r2 -D__mips_o32 -D__FreeBSD__=5 -ggdb : -msoft-float -I/home/tester/HEAD8/src/lib/libc/include : -I/home/tester/HEAD8/src/lib/libc/../../include : -I/home/tester/HEAD8/src/lib/libc/mips -DSOFTFLOAT -D__DBINTERFACE_PRIVATE : -I/home/tester/HEAD8/src/lib/libc/../../contrib/gdtoa -DINET6 : -I/home/tester/HEAD8/src/../obj32/mips/home/tester/HEAD8/src/lib/libc : -I/home/tester/HEAD8/src/lib/libc/resolv -DPOSIX_MISTAKE : -I/home/tester/HEAD8/src/lib/libc/locale -DBROKEN_DES -DPORTMAP : -DDES_BUILTIN -I/home/tester/HEAD8/src/lib/libc/rpc -DNS_CACHING : -DSYMBOL_VERSIONING -c /home/tester/HEAD8/src/lib/libc/mips/gen/_setjmp.S : mips64-octeon-linux-gnu-gcc : :/home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S: Assembler messages: : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:68: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:69: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:70: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:71: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:72: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:73: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:74: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:75: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:76: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:77: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:78: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:82: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:94: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:95: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:98: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:99: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:100: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:101: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:102: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:103: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:104: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:105: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:106: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:107: Error: expression : too complex : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:113: Warning: No : .cprestore pseudo-op used in PIC code : /home/builduser/HEAD8/src/lib/libc/mips/gen/_setjmp.S:115: Warning: No : .cprestore pseudo-op used in PIC code : *** Error code 1 : : Stop. : *** Error code 1 : : Stop. : *** Error code 1 : : Stop. : *** Error code 1 From alancyang at gmail.com Fri Nov 14 11:17:08 2008 From: alancyang at gmail.com (alan yang) Date: Fri Nov 14 11:17:15 2008 Subject: FreeBSD on RMI Message-ID: <290865fd0811141044i46399307ob44e53642beac15d@mail.gmail.com> Hi, All, Wonder any work / progress towards porting of FreeBSD on RMI chip. If is, can people provide some pointers on the build environment and target XLR chip. Thanks in advance. Alan From bms at incunabulum.net Sat Nov 15 07:00:57 2008 From: bms at incunabulum.net (Bruce Simpson) Date: Sat Nov 15 07:01:03 2008 Subject: MIPS port repository question Message-ID: <491EE062.2070705@incunabulum.net> Hi, Apologies for cross-post: I'm confused about which repository we should be doing active MIPS development in. Should we still be using Perforce for this? I would like to push back my changes to bfe(4) which enable it to probe and attach to the Sonics SiliconBackplane in the BCM5365P, currently these are in an SVN checkout of HEAD on my main dev box. I see gonzo@ is active on the SiBa stuff right now... go gonzo! thanks BMS From imp at bsdimp.com Sat Nov 15 08:59:27 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Nov 15 08:59:41 2008 Subject: MIPS port repository question In-Reply-To: <491EE062.2070705@incunabulum.net> References: <491EE062.2070705@incunabulum.net> Message-ID: <20081115.100002.-1384053695.imp@bsdimp.com> In message: <491EE062.2070705@incunabulum.net> Bruce Simpson writes: : Hi, : : Apologies for cross-post: : I'm confused about which repository we should be doing active MIPS : development in. : : Should we still be using Perforce for this? : : I would like to push back my changes to bfe(4) which enable it to probe : and attach to the Sonics SiliconBackplane in the BCM5365P, currently : these are in an SVN checkout of HEAD on my main dev box. : : I see gonzo@ is active on the SiBa stuff right now... go gonzo! Most of the mips stuff has been pushed into the tree. The bleeding edge stuff is still just in p4. I didn't merge your bfe(4) changes into svn, but if you have something that's stable, there's no reason not to do so. I'd commit to p4 first, then do the normal merge, personally, but it is up to you. The next IFC will take care of merging. Warner From gonzo at bluezbox.com Sat Nov 15 13:23:33 2008 From: gonzo at bluezbox.com (Oleksandr Tymoshenko) Date: Sat Nov 15 13:23:39 2008 Subject: FreeBSD on RMI In-Reply-To: <290865fd0811141044i46399307ob44e53642beac15d@mail.gmail.com> References: <290865fd0811141044i46399307ob44e53642beac15d@mail.gmail.com> Message-ID: <491F39F7.7010401@bluezbox.com> alan yang wrote: > Hi, All, > > Wonder any work / progress towards porting of FreeBSD on RMI chip. If > is, can people provide some pointers on the build environment and > target XLR chip. As far as I know none of FreeBSD/MIPS developers has access to the hardware, hence there is no port for RMI. From imp at bsdimp.com Sat Nov 15 14:32:46 2008 From: imp at bsdimp.com (M. Warner Losh) Date: Sat Nov 15 14:32:56 2008 Subject: FreeBSD on RMI In-Reply-To: <491F39F7.7010401@bluezbox.com> References: <290865fd0811141044i46399307ob44e53642beac15d@mail.gmail.com> <491F39F7.7010401@bluezbox.com> Message-ID: <20081115.153058.1716877238.imp@bsdimp.com> In message: <491F39F7.7010401@bluezbox.com> Oleksandr Tymoshenko writes: : alan yang wrote: : > Hi, All, : > : > Wonder any work / progress towards porting of FreeBSD on RMI chip. If : > is, can people provide some pointers on the build environment and : > target XLR chip. : As far as I know none of FreeBSD/MIPS developers has access to the : hardware, hence there is no port for RMI. Actually, some of the FreeBSD/mips developers do have access to the RMI chipset. The problem is that the NDA required to use the RMI documentation makes it impossible to release the code to support it... I don't have such hardware, but I know that those that do tell me this... Warner From goncalves.v.andre at gmail.com Sun Nov 23 09:36:23 2008 From: goncalves.v.andre at gmail.com (AVG) Date: Sun Nov 23 09:36:29 2008 Subject: Mips Open image Message-ID: <20648401.post@talk.nabble.com> how can i open one imagem in mips? it always give me: "Unknown System call: 13" I have: .data # Data declaration section image_rgb: .space 786432 # 512*512 (image size) * 3 (1 bit per colour) image_gray: .space 262144 # 512*512 file: .asciiz "lena.rgb" read: la $a0, ficheiro # string containing filename to open li $a1, 0 # li $a2, 0 # read only li $v0, 13 # open syscall # v0 = file descriptor move $a0, $v0 la $a1, image_rgb li $a2, 786432 li $v0, 14 syscall main: # Start of code section j read -- View this message in context: http://www.nabble.com/Mips-Open-image-tp20648401p20648401.html Sent from the freebsd-mips mailing list archive at Nabble.com. From PublicServicePartnershipLtd_769894 at dotmailer.co.uk Tue Nov 25 02:20:24 2008 From: PublicServicePartnershipLtd_769894 at dotmailer.co.uk (Mike Cross) Date: Tue Nov 25 02:20:31 2008 Subject: Emailing to the Public Sector Made Easy Message-ID: From bms at incunabulum.net Tue Nov 25 07:47:12 2008 From: bms at incunabulum.net (Bruce M. Simpson) Date: Tue Nov 25 07:47:18 2008 Subject: Mips Open image In-Reply-To: <20648401.post@talk.nabble.com> References: <20648401.post@talk.nabble.com> Message-ID: <492C1DF9.7070809@incunabulum.net> AVG wrote: > how can i open one imagem in mips? it always give me: "Unknown System call: > 13" > Sure you've got the right mailing list here? This list is about the port of FreeBSD to MIPS hardware. It looks like you're writing some app in assembler which needs specific libraries, and there isn't enough context to go on to be more helpful than this. thanks BMS