Jump to content
RealModScene
cjd166

Libxenon toolchain install?

Recommended Posts

Hello,

I am trying to install the libxenon toolchain following the guide on free60 resulting in error. The build fails making gcc first pass in GCC/doc I have tried this on Ubuntu and debian... I have downgraded to texinfo 4.8 on debian hoping it would help but still fails with error while making GCC... I can upload log shortly but the error can be easily replicated by installing debian or Ubuntu and simply following the guide on free60..

Thanks

Cjd

Share this post


Link to post
Share on other sites

It has to do with using newer versions of GCC... i think you need 4.7 or older to actually compile the toolchain properly...

I created a VM image back when i was actively working on the project, it can be found here:  https://mega.nz/#!3k4UFayA!CDkEvw_vwntt2xdPvJTWsyKzi80dgj67WelkfPZadD4 the username/password is likely "libxenon", but it might be something else...

Share this post


Link to post
Share on other sites

Thank you so much. I will try with 4.7 but will most likely make use the VM image.... Thank you swizzy

Cjd

Great that it's ova as well!!!!

Share this post


Link to post
Share on other sites

can't login to my account

Debian GNU/Linux  7 XeLLCompiler tty1

Login incorrect

 please help me! 

Thanks

Share this post


Link to post
Share on other sites

Wow..... Linux hacking 101. lol. I am assuming you are running this in a virtual machine, but if not the process is basically the same.

 

So..... you will need to edit the /etc/shadow file. to do this you will need a livecd of some sort This is dumbed down a bit, but a little googling and you should figure it out.

This process requires root access, hince the livecd.

1.) boot off the live CD

2.)Mount the root partition of the virtual HDD, should be /dev/sdaX(Where X is the partition number

3.) create a new password hash "openssl passwd -1 

4.) copy the hash that is produced.

5.) replace the hash for root in /MountPoint/etc/shadow

should look something like this:

	root:$1$SI4dvHLr$lLh8jESjtJ0jrHJIQtQJz1:17243:0:::::
	

 

Fair warning, the example hash here is a blank password, and not an actual password I would use, sorry to those hackers out there who would try to use it to access my stuff.

6.) Then save and exit.

7.) Unmount the partition

8. reboot without live cd, and login with new password

Share this post


Link to post
Share on other sites

Or you can just tell grub to dump you into a recovery terminal... with that you can just use passwd instead of going the manual way :)

Share this post


Link to post
Share on other sites
13 hours ago, Swizzy said:

Or you can just tell grub to dump you into a recovery terminal... with that you can just use passwd instead of going the manual way :)

True, assuming grub is set up to allow you to access the recovery terminal. I actually remove that option from all of my builds, as I never use it, then I add a password, so people cant modify the kernel cmd line. And since I didnt set up that enviornment, I didnt know if there was a recovery console option, so my solution was more of a will work every time solution. ;) There are other ways to do that also, such as chroot, but I figured editing a txt file was easier then walking someone through the chroot process, and then having to reset the environment.... You get the idea. ;)

Share this post


Link to post
Share on other sites

The VM image i provided largely contain defaults for everything, security wasn't something i cared about when i made it as it was something i only used when working on libxenon stuff... and since it was a virtual machine very little damage could be done if somehow someone got into it while i had it running without me noticing...

Share this post


Link to post
Share on other sites
On 2/22/2017 at 1:40 PM, Swizzy said:

It has to do with using newer versions of GCC... i think you need 4.7 or older to actually compile the toolchain properly...

I created a VM image back when i was actively working on the project, it can be found here:  https://mega.nz/#!3k4UFayA!CDkEvw_vwntt2xdPvJTWsyKzi80dgj67WelkfPZadD4 the username/password is likely "libxenon", but it might be something else...

Look sorry for bumping this, but its been a nightmare trying to build the toolchain. I came across the VM you uploaded hoping that it would be the solution to my problems, but the password/username isn't libxenon. I'm completely lost at this point.

Share this post


Link to post
Share on other sites
On 7/16/2018 at 6:07 AM, ocas said:

Look sorry for bumping this, but its been a nightmare trying to build the toolchain. I came across the VM you uploaded hoping that it would be the solution to my problems, but the password/username isn't libxenon. I'm completely lost at this point.

There are plenty of ways of getting past that, here's a link that might help you: http://www.debianadmin.com/how-to-reset-debian-root-password.html

Share this post


Link to post
Share on other sites
On 4/29/2019 at 1:46 AM, ThatRGHGuy said:

I'm using a virtual machine and don't understand. the file you provided is locked with a username and password, what you said does not work. That link to reset also does nothing for me. Can you upload a newer version that has the password removed? or at least provide one with a working username and password. 

 

- I can shift left click all day long and nothing happens. When I go to enter the password from username and pas, on the pasword side it doesnt let em type anything until I press enter again, and doing that causes a invalid login message.

 

EDIT: Nevermind I figured it out, the username is Xell, I however changed the pass to 1 lmao. Anyways that VM doesnt do anything for me considering theres no GUI, just shows as a terminal (Not linux savvy) so maybe that's the way that version is supposed to be, I also have no idea how to replace the files in that version of linux to use my custom xell reloaded.. Even if I figured that out, I would have no idea how to even get the files off it..

 

I have tried using Unbunta and Linux Mint and neither can build the libxenon toolchain, both repeat as a Permission Denied error message...

 

I was using Live CD's if that matters.. 

You need to be running as root to install all the required software to compile the toolchain, when you boot into a live CD you don't login as root, you login as a default user in most cases.

"sudo -i" usually works to get you running as root

Share this post


Link to post
Share on other sites
On 7/16/2018 at 6:07 AM, ocas said:

Look sorry for bumping this, but its been a nightmare trying to build the toolchain. I came across the VM you uploaded hoping that it would be the solution to my problems, but the password/username isn't libxenon. I'm completely lost at this point.

So, after downloading it and checking, i figured out what the username/password is... easy...

Username: xell
Password: password

  • Haha 2

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...