Homebrew [Tutorial] Setting up Pegaswitch and Preparing for Homebrew

  • Thread starter Thread starter iAqua
  • Start date Start date
  • Views Views 151,893
  • Replies Replies 368
  • Likes Likes 44
For anyone else experiencing this error

Makefile:58: recipe for target 'build/test/test_malloc.nro.so' failed
make: *** [build/test/test_malloc.nro.so] Error 127

I found the solution. I was in fact missing lld even when I thought it was installed. To be on the safe side make sure that you compile and install LLD from source. For some reason the upstream package didn't seem to install it. You can follow these instructions to build and install LLD manually. http://lld.llvm.org/
 
  • Like
Reactions: machinoman
i agree with you but honestly I followed a tut already posted. In the days to come I imagine there will be a need for a dedicated tut though. The thing that puzzles me though is I remember it going fairly painless. I suppose I will need a test box to see what's causing issues. So far I am able to do the flog time trigger and the hello world nro posted without issue so I can confirm working but no clue on what causes issues. I know I generally have my firewall off and never needed to add any ports to my router...when I get home I will check my windows build#

build 15063.726 64bit Windows 10 Home
 
Last edited by ,
  • Like
Reactions: ShadowOne333
For anyone else experiencing this error

Makefile:58: recipe for target 'build/test/test_malloc.nro.so' failed
make: *** [build/test/test_malloc.nro.so] Error 127

I found the solution. I was in fact missing lld even when I thought it was installed. To be on the safe side make sure that you compile and install LLD from source. For some reason the upstream package didn't seem to install it. You can follow these instructions to build and install LLD manually. http://lld.llvm.org/

i just saw you post this and its 24% installed, glad to know it will help!

EDIT: I ran into one more snag after this for not installing lz4 correctly. I resolved it by doing this:

sudo apt install python-pip
pip install lz4

If this was mentioned elsewhere, sorry. I am lazy to look around and lz4 was too short to search.
 
Last edited by machinoman,
No answer ?

PegaSwitch works with any version below 3.0.1, I believe. Rohan (through PegaSwitch) only works with 3.0.0. In my opinion, there really are no downsides to upgrading to 3.0.0, using Pokken. People say if they wait, lower firmwares may also have an exploit, but I don't understand this notion. Lower firmwares are compatible with less games, and an exploit already exists for 3.0.0. I cannot think of a reason to stay below 3.0.0, besides waiting for Pokken's price to go down. Some even prefer to stay at 1.0.0, but I think that is mostly for show. I cannot think of a single device that is best exploited at its launch version.
 
If anyone is having issues installing the package "lz4" via Pip.
Make sure you have the python-dev package installed.

Code:
sudo apt-get install python-dev
 
So, apparently my main issue is I'm so used to working as root/su that when I got to the git clone for pegaswitch it was going in the wrong location.

Running the commands as a normal user and everything worked fine.

I ended up just throwing together a dedicated Ubuntu machine before figuring out the su mistake.
 
  • Like
Reactions: Masterwin
I had problems entering the bash alias so made an alias file.

gedit ~/.bash_aliases

enter this line and save

alias pegaswitch='cd ~/pegaswitch; sudo node start.js'
 
What ever happened to this hacking shit working on any firmware, UP TO 3.0...? I'm not rebuying Pokken, which is a shite game, when the earlier firmwares are exploitable as well...

Why don't you rent it? Sign up for a free 30 day GameFly, update, return game, done.

Just did this myself and I'm all set. Membership cancelled, no $$ spent.
 
Why don't you rent it? Sign up for a free 30 day GameFly, update, return game, done.

Just did this myself and I'm all set. Membership cancelled, no $$ spent.
Can't check my mailbox. I can't get mail. I mean, if it's on redbox, sure. I'll check and see. But why is it 3.0 only when other firmwares are vulnerable?
 

Site & Scene News

Popular threads in this forum