Writing to /bin and /lib ?

[Martijn Verburg]

Hi Kelly,

Another example just came through (apologies for not getting you the
earlier details, my bad).  It looks like this is the stage when it's
building images (I see lots of references to the relative images/lib
images/unsigned type directories).  Eventually it starts with:

** NOTE the strange quotation marks, a left tick followed by the
straightened right single quote **

Updating images/sec-bin.zip
Images.gmk:179: warning overridding commands for target `/bin/rmiregistery'
Images.gmk:179: ignoring old commands for target `/bin/rmiregistery'
...
...
...
..
Images.gmk:616: warning: ignoring old commands for target `/release'
/bin/cp: cannot create regular file `/lib/security/java.security':
Permission denied
make[2]: *** [/lib/security/java.security] Error 1
make[1]: *** [images] Error 2
make: *** [images-only] Error 2

Cheers,
Martijn


On 13 February 2013 18:48, Kelly O'Hair <kelly.ohair at oracle.com> wrote:
> Can we get more details?
> Sounds like a make variable that holds a directory is not being defined, we should never try and write to /bin or /lib.
>
> -kto
>
> On Feb 13, 2013, at 10:39 AM, Martijn Verburg wrote:
>
>> Hi all,
>>
>> This might have already been covered (in that case my apologies).  I
>> noticed during recent builds of the tl forest that the make clean
>> install process expected to write to /bin (an rmi file of some sort)
>> and /lib - this surprises me a little - is that definitely the
>> intention?
>>
>> Apologies for the lack of details - context switching a little much tonight.
>>
>> Cheers,
>> Martijn
>