Page 3 of 3

Re: problem with imgboot trying to boot for the first time

Posted: Mon Sep 09, 2013 5:02 pm
by andymc
oscar wrote:I found that norelro.patch looks for 'liblic' folder in /src/lib, but this folder doesn't exist. The only folder that lefts in the /src/lib folder is 'libc'.
After modifying norelro.patch with the path to libc (insted of liblic), it worked but one error appeared:

Code: Select all

Hunk #1 FAILED at 47.
1 out of 1 hunk FAILED -- saving rejects to file src/lib/libc/Makefile.rej
Now I will built it and I will try to run it on VirtualBox. I'm using a source code that I just have extracted from the zipped source code. Let's see what happens :geek:
Oh yeah, sorry, the public distribution doesn't have 'liblic'. That section of the patch should just be deleted (there's no need to patch the Makefile for 'libc').
oscar wrote:Good news Andy! :dance:

Now all works weel until the Visopsys desktop appears :D
Good :-)
oscar wrote:But... a new error appears, this time related to the process login :geek:

I attach an image in this post so that you can read it :)
Huh. Does that happen every time?

Re: problem with imgboot trying to boot for the first time

Posted: Tue Sep 17, 2013 4:25 pm
by oscar
Hi Andy,

Sorry for the late reply. Yes, it always happen... I guess maybe it's because of that 'liblic' that I don't need to rename to 'libc' in your Makefile as actually we don't need to make any change to it :roll: . I will try it and when I have the result I will tell you :geek:

See you soon! :D

Re: problem with imgboot trying to boot for the first time

Posted: Tue Sep 17, 2013 6:47 pm
by oscar
Yes! It worked, no more problems! :dance:

What I have done is just what you have said about deleting the part related to liblic, instead of what I done before (renaming it to 'libc').
Doing this, the system runs without any error :D

I attach the norelro.patch that finally worked here.

Have a nice day! ;)

Re: problem with imgboot trying to boot for the first time

Posted: Wed Sep 18, 2013 6:25 pm
by andymc
Great news, thanks for letting us know.

Keep us informed about your development progress :-)