Re: gobolinux-users Digest, Vol 140, Issue 5

On Sun, Mar 5, 2017 at 10:20 PM, Stéphane Aulery <[email protected]> wrote:

> Le 06/03/2017 à 01:24, Lucas C. Villa Real a écrit :
>
>> On Sun, Mar 5, 2017 at 8:23 PM, Stéphane Aulery <[email protected]
>> <mailto:[email protected]>> wrote:
>>
>>     Le 06/03/2017 à 00:15, sali a écrit :
>>
>>
>>         The Program is still there.
>>         Only the symlinks are removed.
>>         What I did was: make one symlink
>>         from
>>         /Programs/GMP/6.1.1/lib/libgmp.so.10.3.1
>>         to
>>         /System/Index/lib/libgmp.so.10
>>         'by hand'.
>>         That should be enough.
>>
>>
>>     Thanks. Lucs gave me a commanl which worked well :
>>
>>     SymlinkProgram -c overwrite GMP 6.1.2
>>
>>
>> Great to know!
>>
>>
>>     After that I could compile GMP and GCC. Just after the compilation
>>     of GCC it proposed me to compiler Linux. I did it. No compilation
>>     problem but now the configuration of the linux console passed to the
>>     kernel which makes the definition is rough.
>>
>>     Did you have the same problem?
>>
>>
>> I'm not sure I understand your last sentence.
>>
>
> Sorry, my english is awfull.
>

So is mine, no worries. I wish I had taken my French lessons more seriously
in the past so we could get past language slips :)


> Are you talking about the
>
>> "menuconfig" interface that's shown when you Compile Linux? If that's
>> what you mean, then it's safe to click on "Exit" without making any
>> changes; the kernel should be built just fine afterwards. Or do you need
>> some clarification about the arguments passed by GRUB to boot the new
>> kernel?
>>
>
> I think that arguments passed to GRUB for the new kernel have been altered
> during compilation / installation. I could check that.


If you have an EFI system (which you can tell based on the presence of
/sys/firmware/efi/), then "Compile Linux" attempts to update the GRUB
application that is loaded at boot time. If for some reason it failed to
update it, then you will be left with a file at
/System/Kernel/Boot/BOOTX64.EFI. Once you mount your EFI System Partition
and replace the its BOOTX64.EFI file under /BOOT/EFI with the one under
/S/K/Boot, the updated kernel will be recognized on the next boot.

The patch release (016.01) that we're working on should fix issues with the
auto-mounting of the EFI System Partition so that kernel updates go more
smoothly.

Merci,
Lucas

_______________________________________________
gobolinux-users mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users