|
From: | Phil Holmes |
Subject: | Re: GUB problem |
Date: | Wed, 24 Aug 2016 14:54:13 +0100 |
To: <address@hidden> Cc: <address@hidden>; <address@hidden> Sent: Wednesday, August 24, 2016 2:37 PM Subject: Re: GUB problem
Apologies for the delay in replying. I knew it would take me a little time to gather the information you needed, so had to wait for some free time. Responses are below.Thank you very much. I suspect that environment variable ABI problem. Have you ever mounted the disk to 64 bit OS? Have you changed virtualization software? GUB's basic document https://github.com/gperciva/gub/blob/master/web/basics.html says ``` <h3>SHARING DIRECTORIES</h3> GUB uses an ABI environment variable to work around some build bugs in some packages. This variable is not checked by the environment-changed function, so problems will probably occur if you share your GUB build directory between a 32-bit and 64-bit OS. If you change your operating system, delete the target/ directory of GUB before trying to build it again.
I think this is quite a difficult one to answer.My main machine was (IIRC) 64 bit originally - that's partly why I used a VM for GUB, since GUB used not to work in a 64 bit environment. When I upgraded from Ubuntu 10.04, via 12 to 14.04, the machine became 32 bit, since I selected that option because it seemed that the 64 bit was not deigned for Intel CPUs. I think I may have misunderstood that, but whatever the reason, I now run a 32 bit main machine. As part of the move to Ubuntu 14, I needed to upgrade the Oracle VM software, but did not change the VM spec at all. So I think the answer is that the actual VM disk has never seen a 64 bit environment, but has run within a 64 bit environment.
--Phil Holmes
[Prev in Thread] | Current Thread | [Next in Thread] |