Jan Damborsky wrote:
> Dave Miner wrote:
>>
>> I'm slightly confused why this fix is correct, as the actual path for 
>> these libraries would appear to be /usr/lib/sparcv9, not /usr/lib/64. 
>> Are we relying on some side-effect of the file resolution method 
>> working here?
>
> Looking at dir structure, /usr/lib/64 is symlink to /usr/lib/sparcv9:
>
> # uname -a
> SunOS opensolaris 5.11 snv_128 sun4u sparc SUNW,Sun-Fire-V210 Solaris
> # ls -ld /usr/lib/64
> lrwxrwxrwx 1 root root 7 Nov 23 06:08 /usr/lib/64 -> sparcv9
>
> Perhaps the same dir and file structure should be carried into microroot,
> e.g. libraries would go into /usr/lib/sparcv9/ and /usr/lib/64 would
> be created as symlink.

Clay,

I tried to create 128 Sparc AI image and confirmed that following lines
added to ai_sparc_image.xml took care of that:

...
<base_include type="file">usr/lib/sparcv9/libast.so.1</base_include>
<base_include type="file">usr/lib/sparcv9/libcmd.so.1</base_include>
<base_include type="file">usr/lib/sparcv9/libshell.so.1</base_include>
<base_include type="file">usr/lib/64</base_include>
...

Sparc installation of 128 is in progress now.

Jan


Reply via email to