Menu
▾
▴
ps2hacking-devel
|
From: Joseph P. <pa...@mc...> - 2001-08-28 18:26:00
|
Heya, I want to build the chain on a mandrake 7.2 box, but everything i've tried so far has failed. Can you guys give me some advice on building the gcc chain and how to compile that will create a linux-mips executable? thanks, Joe |
|
From: now3d <n3...@an...> - 2001-08-31 13:59:22
|
check our site below for the compiler source and follow the ps2 links for a linux veriosn of the compiler source now3d Joseph Paris wrote: > > Heya, > > I want to build the chain on a mandrake 7.2 box, but everything i've tried > so far has failed. Can you guys give me some advice on building the gcc > chain and how to compile that will create a linux-mips executable? > > thanks, > Joe > > _______________________________________________ > Ps2hacking-devel mailing list > Ps2...@li... > http://lists.sourceforge.net/lists/listinfo/ps2hacking-devel -- ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
From: Joseph P. <pa...@mc...> - 2001-08-31 15:42:03
|
Right, i did get that. I'm getting an error on creating mips-tfile. I remember there being an issue with that, but not sure what the fix is. Any advice? Thanks, Joe On Fri, 31 Aug 2001, now3d wrote: > check our site below for the compiler source > and follow the ps2 links for a linux veriosn of the compiler source > > now3d > > Joseph Paris wrote: > > > > Heya, > > > > I want to build the chain on a mandrake 7.2 box, but everything i've tried > > so far has failed. Can you guys give me some advice on building the gcc > > chain and how to compile that will create a linux-mips executable? > > > > thanks, > > Joe > > > > _______________________________________________ > > Ps2hacking-devel mailing list > > Ps2...@li... > > http://lists.sourceforge.net/lists/listinfo/ps2hacking-devel > > -- > > ICQ: #11122941 IRC: EFnet #PS2Dev > PS2-Anarchists Dev site > http://www.anarchists.co.uk/ > > |
|
From: M. R. B. <mr...@0x...> - 2001-08-31 17:18:53
|
* Joseph Paris <pa...@mc...> on Fri, Aug 31, 2001: > Right, i did get that. I'm getting an error on creating mips-tfile. I > remember there being an issue with that, but not sure what the fix is. > Any advice? > Configure gcc with --with-gnu-ld and --with-gnu-as. M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-05 15:23:41
|
Works great! Thanks for all your help! --Joe On Fri, 31 Aug 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Fri, Aug 31, 2001: > > > Right, i did get that. I'm getting an error on creating mips-tfile. I > > remember there being an issue with that, but not sure what the fix is. > > Any advice? > > > > Configure gcc with --with-gnu-ld and --with-gnu-as. > > M. R. > > |
|
From: Joseph P. <pa...@mc...> - 2001-09-05 22:53:01
|
I was wondering if anyone had experience with creating a ps2 ready cd-rom to test developed software on. Since sony has released the dev kit, i had assumed there was a way of creating bootable cdroms.... Have any of you tried this yet? Thanks, Joe On Wed, 5 Sep 2001, Joseph Paris wrote: > Works great! Thanks for all your help! > > --Joe > > On Fri, 31 Aug 2001, M. R. Brown wrote: > > > * Joseph Paris <pa...@mc...> on Fri, Aug 31, 2001: > > > > > Right, i did get that. I'm getting an error on creating mips-tfile. I > > > remember there being an issue with that, but not sure what the fix is. > > > Any advice? > > > > > > > Configure gcc with --with-gnu-ld and --with-gnu-as. > > > > M. R. > > > > > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-07 06:13:30
|
* Joseph Paris <pa...@mc...> on Wed, Sep 05, 2001: > I was wondering if anyone had experience with creating a ps2 ready cd-rom > to test developed software on. Since sony has released the dev kit, i had > assumed there was a way of creating bootable cdroms.... Have any of you > tried this yet? > Released what dev kit? Sony is selling the PS2/Linux kit in Japan, which comes with a bootable Linux DVD. There is no method of creating bootable CD-ROMs. M. R. |
|
From: now3d <n3...@an...> - 2001-09-07 14:29:44
|
u can use the AR2 to boot your cdrs (of linux etc) just make your ISO MODE2/XA with iso9660 filenames with version ;1 etc now3d Joseph Paris wrote: > > I was wondering if anyone had experience with creating a ps2 ready cd-rom > to test developed software on. Since sony has released the dev kit, i had > assumed there was a way of creating bootable cdroms.... Have any of you > tried this yet? > > Thanks, > Joe > > On Wed, 5 Sep 2001, Joseph Paris wrote: > > > Works great! Thanks for all your help! > > > > --Joe > > > > On Fri, 31 Aug 2001, M. R. Brown wrote: > > > > > * Joseph Paris <pa...@mc...> on Fri, Aug 31, 2001: > > > > > > > Right, i did get that. I'm getting an error on creating mips-tfile. I > > > > remember there being an issue with that, but not sure what the fix is. > > > > Any advice? > > > > > > > > > > Configure gcc with --with-gnu-ld and --with-gnu-as. > > > > > > M. R. > > > > > > > > > > -- ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
From: Joseph P. <pa...@mc...> - 2001-09-07 15:57:51
|
What is AR2? Which cd-burning program did you use? A linux one, or a windows one? Thanks, Joe On Fri, 7 Sep 2001, now3d wrote: > u can use the AR2 to boot your cdrs (of linux etc) > just make your ISO MODE2/XA with iso9660 filenames with version ;1 etc > now3d > > Joseph Paris wrote: > > > > I was wondering if anyone had experience with creating a ps2 ready cd-rom > > to test developed software on. Since sony has released the dev kit, i had > > assumed there was a way of creating bootable cdroms.... Have any of you > > tried this yet? > > > > Thanks, > > Joe > > > > On Wed, 5 Sep 2001, Joseph Paris wrote: > > > > > Works great! Thanks for all your help! > > > > > > --Joe > > > > > > On Fri, 31 Aug 2001, M. R. Brown wrote: > > > > > > > * Joseph Paris <pa...@mc...> on Fri, Aug 31, 2001: > > > > > > > > > Right, i did get that. I'm getting an error on creating mips-tfile. I > > > > > remember there being an issue with that, but not sure what the fix is. > > > > > Any advice? > > > > > > > > > > > > > Configure gcc with --with-gnu-ld and --with-gnu-as. > > > > > > > > M. R. > > > > > > > > > > > > > > > > -- > > ICQ: #11122941 IRC: EFnet #PS2Dev > PS2-Anarchists Dev site > http://www.anarchists.co.uk/ > > |
|
From: now3d <n3...@an...> - 2001-09-09 12:26:58
|
check ps2dev logs, this topic was discused approx 12months ago in detail. there are over 400 members, so more stuff gets mentioned. see links below Joseph Paris wrote: > > What is AR2? Which cd-burning program did you use? A linux one, or a > windows one? > > Thanks, > Joe > ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
From: Joseph P. <pa...@mc...> - 2001-09-10 17:04:48
|
Great, i'll check that out... Has there been any progress on a unix port of the snsys binutils dists? What's the difference between IOP and the regular ee? Thanks, Joe On Sun, 9 Sep 2001, now3d wrote: > check ps2dev logs, this topic was discused approx 12months ago in > detail. > there are over 400 members, so more stuff gets mentioned. > see links below > > Joseph Paris wrote: > > > > What is AR2? Which cd-burning program did you use? A linux one, or a > > windows one? > > > > Thanks, > > Joe > > > > > ICQ: #11122941 IRC: EFnet #PS2Dev > PS2-Anarchists Dev site > http://www.anarchists.co.uk/ > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-10 18:15:44
|
* Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > Great, i'll check that out... Has there been any progress on a unix port > of the snsys binutils dists? What's the difference between IOP and the > regular ee? > Why wouldn't binutils and gcc compile normally under Unix? Clarify. The IOP stands for "I/O Processor" - it's the same CPU used in the original PSX and is used in the PS2 for "coordinating" actions between perhiperals, etc. as well as providing backwards compatibility with the PSX. The EE is the MIPS R5900 core and related coprocessors. M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-10 19:05:48
|
the ee-binutils from snsys, i believe was configured for a win32 build, and as such there doesn't seem to be an esy way to configure for linux. At least, i'm receiving errors on running configure alone. i.e. ./configure generates ./configure: command not found. It is in each sepereate directory... Thanks, Joe On Mon, 10 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > > > Great, i'll check that out... Has there been any progress on a unix port > > of the snsys binutils dists? What's the difference between IOP and the > > regular ee? > > > > Why wouldn't binutils and gcc compile normally under Unix? Clarify. > > The IOP stands for "I/O Processor" - it's the same CPU used in the original > PSX and is used in the PS2 for "coordinating" actions between perhiperals, > etc. as well as providing backwards compatibility with the PSX. > > The EE is the MIPS R5900 core and related coprocessors. > > M. R. > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-10 20:25:41
|
* Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > the ee-binutils from snsys, i believe was configured for a win32 build, > and as such there doesn't seem to be an esy way to configure for linux. > At least, i'm receiving errors on running configure alone. i.e. > ./configure generates ./configure: command not found. It is in each > sepereate directory... > Notice that the zip archives are in DOS CR/LF format. Use `unzip -a' to convert those files into the format that bash expects. Then `chmod +x' the configure scripts, and anything else bash bitches about. You may also want to make all files writeable as well. You still won't have much luck as there are key files missing in the toplevel directory. You'll have to copy those files from a binutils-2.9.1 and gcc-2.95.2 archive, just pay attention to the files that the individual configure's complain about. You'll also have to edit config.sub (once you copy it) and add the mipsel*r5900 and dvp entries so that your --target string will be properly recognized. Confused yet? Good. I'm going through this now to see what's all missing. But hey - at least now you know how to generate the ubiquitous "mpg" assembly instruction, eh? Have fun, M. R. |
|
From: M. R. B. <mr...@0x...> - 2001-09-10 20:43:29
|
* Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > the ee-binutils from snsys, i believe was configured for a win32 build, > and as such there doesn't seem to be an esy way to configure for linux. > At least, i'm receiving errors on running configure alone. i.e. > ./configure generates ./configure: command not found. It is in each > sepereate directory... > I guess the quick and dirty way to get things done is to do a diff against stock binutils-2.9.1 and gcc-2.95.2 and the ee/iop custom tools. Then you simply apply that patch against stock and you should be good to go - except for the toplevel config.sub. You still have to hand-edit this AFAICS. Without these modifications, binutils and gcc won't know what the hell a dvp or iop is :). When diff'ing, every directory except gcc belongs to binutils. M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-10 21:32:23
|
I think i hit a pretty frustrating part. I compiled the snsys ee-binutils code under linux which produced the as,gasp,ld,etc... I still can't compile vpu asm files... I configured with --target=mipsel-scei-elfl, which i thought was what the iop was doing... Is this way off base? Thanks, Joe On Mon, 10 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > > > the ee-binutils from snsys, i believe was configured for a win32 build, > > and as such there doesn't seem to be an esy way to configure for linux. > > At least, i'm receiving errors on running configure alone. i.e. > > ./configure generates ./configure: command not found. It is in each > > sepereate directory... > > > > I guess the quick and dirty way to get things done is to do a diff against > stock binutils-2.9.1 and gcc-2.95.2 and the ee/iop custom tools. Then you > simply apply that patch against stock and you should be good to go - except > for the toplevel config.sub. You still have to hand-edit this AFAICS. > Without these modifications, binutils and gcc won't know what the hell a dvp > or iop is :). > > When diff'ing, every directory except gcc belongs to binutils. > > M. R. > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-10 21:58:55
|
* Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > I think i hit a pretty frustrating part. I compiled the snsys ee-binutils > code under linux which produced the as,gasp,ld,etc... I still can't > compile vpu asm files... I configured with --target=mipsel-scei-elfl, > which i thought was what the iop was doing... Is this way off base? > Yes. The iop tools should be compiled with "mipsel-scei-elfl", the ee tools should be compiled with mipselr5900 or similar. How did you compile the tools .. can you supply configure/make lines please? M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-11 20:01:52
|
I put together a ps2-dvp-binutils package that one should be able to do a ./configure --target=dvp and have it produce the correct binutils... The build process may be a bit twichty, but i think i've resolved most of those problems.... This is built off the snsys ee-binutils source. If there is a need for it, i can send it. Can someone help explain why there needs to be so many different sets of binutils for ps2 dev? Is there a reasonable way to start combining these? --Joe On Mon, 10 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Mon, Sep 10, 2001: > > > I think i hit a pretty frustrating part. I compiled the snsys ee-binutils > > code under linux which produced the as,gasp,ld,etc... I still can't > > compile vpu asm files... I configured with --target=mipsel-scei-elfl, > > which i thought was what the iop was doing... Is this way off base? > > > > Yes. > > The iop tools should be compiled with "mipsel-scei-elfl", the ee tools > should be compiled with mipselr5900 or similar. > > How did you compile the tools .. can you supply configure/make lines > please? > > M. R. > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-11 20:26:10
|
* Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > I put together a ps2-dvp-binutils package that one should be able to do a > ./configure --target=dvp and have it produce the correct binutils... The > build process may be a bit twichty, but i think i've resolved most of > those problems.... This is built off the snsys ee-binutils source. If > there is a need for it, i can send it. > > Can someone help explain why there needs to be so many different sets of > binutils for ps2 dev? Is there a reasonable way to start combining these? > There doesn't need to be. You can combine the iop and ee/dvp patches into one binutils and gcc source that you can use to build all toolsets. AFAICT, you could even use the *same* compiler for the IOP and EE by using custom gcc specs and options. In a few days I'll be asking the binutils and gcc folks why these patches never made it in and if there is any objection to them being included into mainline binutils and gcc. But the patches do need to be cleaned up and rewritten (to an extent) for the current binutils and gcc stock (the patches are over 2 years old). If anyone else (Sony or Cygnus/Redhat) has any other insight into these tools I'd appreciate hearing them. M. R. |
|
From: Joseph P. <pa...@mc...> - 2001-09-11 20:31:25
|
Are the patch files built and ready to go? Or do they still have to be generated off what we have now? --Joe On Tue, 11 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > I put together a ps2-dvp-binutils package that one should be able to do a > > ./configure --target=dvp and have it produce the correct binutils... The > > build process may be a bit twichty, but i think i've resolved most of > > those problems.... This is built off the snsys ee-binutils source. If > > there is a need for it, i can send it. > > > > Can someone help explain why there needs to be so many different sets of > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > There doesn't need to be. You can combine the iop and ee/dvp patches into > one binutils and gcc source that you can use to build all toolsets. > AFAICT, you could even use the *same* compiler for the IOP and EE by using > custom gcc specs and options. > > In a few days I'll be asking the binutils and gcc folks why these patches > never made it in and if there is any objection to them being included into > mainline binutils and gcc. But the patches do need to be cleaned up and > rewritten (to an extent) for the current binutils and gcc stock (the > patches are over 2 years old). > > If anyone else (Sony or Cygnus/Redhat) has any other insight into these > tools I'd appreciate hearing them. > > M. R. > > |
|
From: M. R. B. <mr...@0x...> - 2001-09-11 20:39:40
|
* Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > Are the patch files built and ready to go? Or do they still have to be > generated off what we have now? > Um, did you read my last post? I've included it here just in case. M. R. > --Joe > > On Tue, 11 Sep 2001, M. R. Brown wrote: > > > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > > > I put together a ps2-dvp-binutils package that one should be able to do a > > > ./configure --target=dvp and have it produce the correct binutils... The > > > build process may be a bit twichty, but i think i've resolved most of > > > those problems.... This is built off the snsys ee-binutils source. If > > > there is a need for it, i can send it. > > > > > > Can someone help explain why there needs to be so many different sets of > > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > > > > There doesn't need to be. You can combine the iop and ee/dvp patches into > > one binutils and gcc source that you can use to build all toolsets. > > AFAICT, you could even use the *same* compiler for the IOP and EE by using > > custom gcc specs and options. > > > > In a few days I'll be asking the binutils and gcc folks why these patches > > never made it in and if there is any objection to them being included into > > mainline binutils and gcc. But the patches do need to be cleaned up and > > rewritten (to an extent) for the current binutils and gcc stock (the > > patches are over 2 years old). > > > > If anyone else (Sony or Cygnus/Redhat) has any other insight into these > > tools I'd appreciate hearing them. > > > > M. R. > > > > |
|
From: Joseph P. <pa...@mc...> - 2001-09-11 20:46:19
|
Right, could you send the patches then? I can't find them on the website. Or do i need to generate my own? I don't see them in either the dists or on the website. --Joe On Tue, 11 Sep 2001, M. R. Brown wrote: > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > Are the patch files built and ready to go? Or do they still have to be > > generated off what we have now? > > > > Um, did you read my last post? I've included it here just in case. > > M. R. > > > --Joe > > > > On Tue, 11 Sep 2001, M. R. Brown wrote: > > > > > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > > > > > I put together a ps2-dvp-binutils package that one should be able to do a > > > > ./configure --target=dvp and have it produce the correct binutils... The > > > > build process may be a bit twichty, but i think i've resolved most of > > > > those problems.... This is built off the snsys ee-binutils source. If > > > > there is a need for it, i can send it. > > > > > > > > Can someone help explain why there needs to be so many different sets of > > > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > > > > > > > There doesn't need to be. You can combine the iop and ee/dvp patches into > > > one binutils and gcc source that you can use to build all toolsets. > > > AFAICT, you could even use the *same* compiler for the IOP and EE by using > > > custom gcc specs and options. > > > > > > In a few days I'll be asking the binutils and gcc folks why these patches > > > never made it in and if there is any objection to them being included into > > > mainline binutils and gcc. But the patches do need to be cleaned up and > > > rewritten (to an extent) for the current binutils and gcc stock (the > > > patches are over 2 years old). > > > > > > If anyone else (Sony or Cygnus/Redhat) has any other insight into these > > > tools I'd appreciate hearing them. > > > > > > M. R. > > > > > > > > |
|
From: now3d <n3...@an...> - 2001-09-15 06:28:09
|
Hello It seems you are making good progress with the GNUPro sources released by snsys. However I think you must be unaware that you are repeating the work that other people have done before. the ps2dev.sourceforge.net site has the fixed unix sources for iop and ee. they have been there for some time. Also the ps...@to... list has been running for over 18 months or so, i sugest you join up, there are over 400 members so you have more chance of making progress quicker. Or at least CC it to both lists, because atm, no one gets this info about your work. I dont think there are >400 members on ps2hacking yet are there? On the subject of including the GNUPro patches for r5900, iop, dvp etc I believe it is an issue of owner permission. eg they wrote it for GNUPro, so the normal GNU tool chain may require the authorisation of the origional author. I sugest you ask about this. (apparently all GNUPro advancements get added into normal GNU after a while, but this has not happened with ps2 specific stuff yet) i sugest you email bin...@so... and enquire there. now3d for info on subscribing to ps2dev look on our site below "M. R. Brown" wrote: > > * Joseph Paris <pa...@mc...> on Tue, Sep 11, 2001: > > > I put together a ps2-dvp-binutils package that one should be able to do a > > ./configure --target=dvp and have it produce the correct binutils... The > > build process may be a bit twichty, but i think i've resolved most of > > those problems.... This is built off the snsys ee-binutils source. If > > there is a need for it, i can send it. > > > > Can someone help explain why there needs to be so many different sets of > > binutils for ps2 dev? Is there a reasonable way to start combining these? > > > > There doesn't need to be. You can combine the iop and ee/dvp patches into > one binutils and gcc source that you can use to build all toolsets. > AFAICT, you could even use the *same* compiler for the IOP and EE by using > custom gcc specs and options. > > In a few days I'll be asking the binutils and gcc folks why these patches > never made it in and if there is any objection to them being included into > mainline binutils and gcc. But the patches do need to be cleaned up and > rewritten (to an extent) for the current binutils and gcc stock (the > patches are over 2 years old). > > If anyone else (Sony or Cygnus/Redhat) has any other insight into these > tools I'd appreciate hearing them. > > M. R. -- ICQ: #11122941 IRC: EFnet #PS2Dev PS2-Anarchists Dev site http://www.anarchists.co.uk/ |
|
From: Alex R. <al...@sp...> - 2001-09-15 08:12:29
|
For whatever reason, GNOME seems to draw things incorrectly. For example, window titles are missing. Any ideas? +------------------------------------------------------------+ | Alexander M. Rosenberg <mailto:alexr@_spies.com> | | Nobody cares what I say. Remove the underscore to mail me. | |
|
From: M. R. B. <mr...@0x...> - 2001-09-15 20:40:35
|
* now3d <n3...@an...> on Sat, Sep 15, 2001: > Hello > It seems you are making good progress with the GNUPro sources released > by snsys. > > However I think you must be unaware that you are repeating the work that > other people have done before. > the ps2dev.sourceforge.net site has the fixed unix sources for iop and > ee. they have been there for some time. > Other people are trying to get these sources into the binutils and gcc mainline? If so, then yes, I am repeating someone's else "work", other than that I'm not doing anything to the sources except cleaning them up. If they're in binutils and gcc proper, then they're already build-ready :P. > Also the ps...@to... list has been running for over 18 months or > so, i sugest you join up, there are over 400 members so you have more > chance of making progress quicker. Or at least CC it to both lists, > because atm, no one gets this info about your work. I dont think there > are >400 members on ps2hacking yet are there? > Thanks for the info. > On the subject of including the GNUPro patches for r5900, iop, dvp etc I > believe it is an issue of owner permission. eg they wrote it for GNUPro, > so the normal GNU tool chain may require the authorisation of the > origional author. I sugest you ask about this. (apparently all GNUPro > advancements get added into normal GNU after a while, but this has not > happened with ps2 specific stuff yet) > Right, Cygnus wrote it for GNUPro for Sony. At the top of each Cygnus source file, is a FSF copyright statement, which means the FSF owns the sources. I seriously doubt that the FSF would withhold sources, so it seems to be an issue of Cygnus just not bothering to merge with the FSF binutils and gcc. Hopefully it's that simple, let me know if I'm missing something. > i sugest you email bin...@so... and enquire there. > I will as soon as I have more time to work on this. M. R. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X