G-Series OSS:*** RLD ERROR ***: Unresolved Text Symbol

[lyates]

All of a sudden, I'm getting the following messages from several calls to things like "ls, cat, mv, etc" using /usr/local/bin:

*** RLD ERROR ***: Unresolved Text Symbol stat64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol fopen64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol lstat64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol open64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol lseek64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol ftruncate64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol readdir64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol fstat64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol stat64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol fopen64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol lstat64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol open64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol lseek64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol ftruncate64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol readdir64 in file /usr/local/bin/ls.
*** RLD ERROR ***: Unresolved Text Symbol fstat64 in file /usr/local/bin/ls.
bash: /usr/local/bin/ls: Invalid function argument


Anybody know why?
I tried re-installing floss-personality for nsr, but no joy.

Thanks!
-Larry

[dimandja]

I don't know anything about floss, but this looks like a library has
been moved or is inaccessible, or maybe the makefile is the wrong
version.

Jojo would have a better handle on this.

[lyates]

Found this in KnowledgeBase:

Rate this content
Title: OSH fails with multiple errors for 64 bit function calls.
Document ID: mmr_ns-gcsc22669-1
Submitted Date: Tue Jan 02 15:23:10 GMT 2007
Last Modified Date: Fri Sep 07 12:57:46 GMT 2007


Title: OSH fails with multiple errors for 64 bit function calls.
Object Name: mmr_ns-gcsc22669
Document Type: Support Information--Knowledge Centered Support
Original owner: NonStop Client Server
Disclosure level: Public
Version state: published
Environment
FACT:T8628
FACT:OSS SYSTEM UTILS
FACT:See Solution ID: mmr_ns-gcsc19910 if this error is returned by
java.
Questions/Symptoms
SYMPTOM:OSH fails with multiple errors for 64 bit function calls.
SYMPTOM:*** RLD ERROR ***: Unresolved Text Symbol stat64 in file /bin/
sh
SYMPTOM:*** RLD ERROR ***: Unresolved Text Symbol fstat64 in file /bin/
sh
SYMPTOM:*** RLD ERROR ***: Unresolved Text Symbol readdir64 in file /
bin/sh
SYMPTOM:*** RLD ERROR ***: Unresolved Text Symbol lstat64 in file /bin/
sh
SYMPTOM:*** RLD ERROR ***: Unresolved Text Symbol open64 in file /bin/
sh
SYMPTOM:*** RLD ERROR ***: Unresolved Text Symbol lseek64 in file /bin/
sh
SYMPTOM:osh[12]: unable to run /bin/sh, error (4022, 74, 0):
unrecognized error
Cause
CAUSE:OSS SPR installed for support of 64 bit IO functions but the
underlying Guardian release need to support the 64 bit IO functions is
not installed.
Answer/Solution
FIX:Fix: If multiple SYSNNs exist boot from the one that includes the
64 bit IO functions. This can be confirmed by editing SYSNN.CONFLIST
and searching for "stat64".
FIX:Fix: If there isn't a SYSNN with the 64 bit functions available
you will need to either fall back to the previous OSS SYSTEM UTILS
release or build an OS that will support for these functions.
© Copyright 2011 Hewlett-Packard Development Company, L.P.

[lyates]

The problem is the OS level of the machine is LESS that the build
level of all of the packages in the floss-personality file for TNS/R.

Unless there is a better solution, I would need to re-compile ALL of
the packages in the floss-personality file to omit the 64 bit function
calls.
Attempting to re-compile all the packages (about 25 packages) in the
nsr floss personality on an older machine would take a very long time.

On older machines, a configure/make/install for a single package can
take days...

The README_FLOSS file states:
This package was built for NSK G06.29 or H06.08 or later.

Does anyone have FLOSS packages for TNS/R built for NSK G06.26?

Is there a master build file for the TNS/R that I can use to build a
floss-personality file using switches to cross-compile all the
packages on an TNS/E?

Hopefully Yours,
-Larry

[Joachim Schmitz]

lyates wrote:
> On Mar 22, 11:14 am, dimandja <demou...@yahoo.com> wrote:
>> I don't know anything about floss, but this looks like a library has
>> been moved or is inaccessible, or maybe the makefile is the wrong
>> version.
>>
>> Jojo would have a better handle on this.

Sorry, I can't fix anything here, Larry's G06.27 system is just way to old
to cope with the needs ot the pre-build packages.

> The problem is the OS level of the machine is LESS that the build
> level of all of the packages in the floss-personality file for TNS/R.
>
> Unless there is a better solution, I would need to re-compile ALL of
> the packages in the floss-personality file to omit the 64 bit function
> calls.
> Attempting to re-compile all the packages (about 25 packages) in the
> nsr floss personality on an older machine would take a very long time.
>
> On older machines, a configure/make/install for a single package can
> take days...

yes, unfortunatly

> The README_FLOSS file states:
> This package was built for NSK G06.29 or H06.08 or later.

More correct: build on, not for, but if it uses APIs that we not available
earlied, you won't be able to run them on earlier release.

> Does anyone have FLOSS packages for TNS/R built for NSK G06.26?

I don't anymore, sorry, Would have to be packages build before 2007.

> Is there a master build file for the TNS/R that I can use to build a

part of the floss packages is a Makefile.floss, which is sort of a master
plan to build the packages

> floss-personality file using switches to cross-compile all the
> packages on an TNS/E?

Hmm, there is some preliminary cross-compile support in floss-1.3. But not
really finished/working and still very rough at the edges...

Bye, Jojo