forums.ps2dev.org

It looks like it was finally introduced today. As expected, the Canadian DMCA is big, complicated, and a close model of the U.S. Digital Millennium Copyright Act (Industry Canada provides a large number of fact sheets here). I'll have much more to say once I've had a careful read, but these are my f...

hlide wrote:I see you insert a 0 to uint8, so I guess you like to have types of same length as possible. :)

It pleases my eye when I see things line up nicely. :)

When it comes to C, if it isn't defined specifically in the standard then you should be very careful. That's what we call 'undefined behavior' and there's no reason to count on it being the same on every system, or even on every execution. Usually I create a types.h file, with defines for things lik...

http://en.wikipedia.org/wiki/C_variable_types_and_declarations There is some confusion in novice C programmers as to how big these types are. The standard is specifically vague in this area: * A short int must not be larger than an int. * An int must not be larger than a long int. * A short int must...

In the meantime, I've committed the 'make -r' and heap size changes.

Perhaps not, if only one person was sending it. The problem is that when thousands of people send the same piece of text with no more effort used than clicking a button. That kind of response can be easily discounted and ignored. By all means, write your own response and send it to your appropriate ...

If it was being passed tomorrow, it would be far too late to change things now. Yes, they're possibly introducing new legislation tomorrow. This is the first step in a long process before passing. If it is anything close to what the rumors say it will be, there's very little chance it would make it ...

Isn't this the kind of stuff autoconf and automake are supposed to deal with anyway?

## Install the required packages.
sudo apt-get install build-essential autoconf automake bison flex \
libncurses5-dev libreadline-dev libusb-dev texinfo

That's from the readme-ubuntu.txt in psptoolchain, and should be fairly applicable to ps2toolchain too.

Easy enough to add that change, the only problem I can see is if someone uses the old method (-1), it'll give them 1K less than before the change.

If that's acceptable, I have the patch made and can commit it anytime.

So if its working fine under OSX and Linux, are there any complaints before I submit it to the repository?

Ok, good. Thanks. :)

So it compiles, but does it run? :) -r, --no-builtin-rules Eliminate use of the built-in implicit rules. Also clear out the default list of suffixes for suffix rules. If that doesn't break anything then we can add it to all builds, otherwise a check would be fine. Can someone test building it on a n...

Uh, so what was the problem and what was the fix? :)

Is there a way to strip out the unused parts of the archive after it has been linked in?

Thanks for doing the hard work, I had been meaning to get around to it for a long time now. :)

Seems to build and work fine under Ubuntu, so I've committed the changes to psptoolchain and psplinkusb.

...and that would be why the whole-archive option isn't used. :)

Good to know.

This should work too, but be sure to strip the binary afterwards if you want to get rid of unused code.

You need to put the libraries at the end of the line. The linker parses the command line and makes a list of what functions it needs as it adds each object file. When it reaches a library it will link only the functions it knows it needs. If you add more object files after the library it doesn't go ...

Can you post the actual error message? It is usually a lot easier to help out when we can see that.

It sounds like you may be linking in libraries in the wrong order.

Try:

fopen("host:someFile","r");

Is there anything to split off? Where's that ps3sdk anyway? :)

I was worried about Oobles when there wasn't an April fools joke on the site.

Glad to see you're still alive. :)

That wouldn't work. Building the toolchain is a process that has to happen in a particular order. You wouldn't be able to build gcc if you haven't already built and installed binutils. I'll take a look at adding libx-dev to the depends check and see if it helps any. I didn't look into why insight ha...

You can use the environment variable $PSPDEV to set the destination directory:
Is that what you need?

The ps3toolchain, which is used for otheros development, has support for newlib but it doesn't have an OS added yet. This means there's no startup code, which is why it can't find crt*.o. You can find some startup code in the otheros demo. As for Ubuntu: danpeori@yggdrasil:~$ apt-cache search ppu- p...

As long as it is a legal method of information gathering and isn't used for piracy, I have no problems. Other moderators may have stricter guidelines but that's the basic test I use.

They shouldn't conflict, they install into different directories.

Backups = bad.

Why not burn a copy of ps2link and see if it will boot? Then you'll be all set up for development:

http://ps2dev.org/ps2/Loaders/PS2_side_boot_loaders/

Grabbing the one with the iso may be easiest for you.