Ralf S. Engelschall wrote:
On Tue, Oct 16, 2007, Douglas S. Summers wrote:

Getting this building the latest OpenPKG (using GCC):

depbase=`echo strerror.o | sed 's|[^/]*$|.deps/&|;s|\.o$||'`; \
        if /openpkg/bin/cc -std=gnu99 -DHAVE_CONFIG_H -I. -I. -I.. -g -O2
-MT strerror.o -MD -MP -MF "$depbase.Tpo" -c -o strerror.o strerror.c; \
        then mv -f "$depbase.Tpo" "$depbase.Po"; else rm -f "$depbase.Tpo";
exit 1; fi
strerror.c: In function 'rpl_strerror':
strerror.c:32: error: 'CHAR_BIT' undeclared (first use in this function)
strerror.c:32: error: (Each undeclared identifier is reported only once
strerror.c:32: error: for each function it appears in.)
make[3]: *** [strerror.o] Error 1
make[3]: Leaving directory `/openpkg/RPM/TMP/openpkg-20071015/tar-1.19/lib'
make[2]: *** [all] Error 2
make[2]: Leaving directory `/openpkg/RPM/TMP/openpkg-20071015/tar-1.19/lib'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/openpkg/RPM/TMP/openpkg-20071015/tar-1.19'
make: *** [all] Error 2

I have no problems building on Solaris 9. I'm trying a build now with Sun's
compiler.

CHAR_BIT is usually provided by <limits.h> on a POSIX system. But it
could be defined to 8 as a fallback definition for AIX. I've applied
such a workaround to the "tar" package now. Please retry, perhaps this
already fixes the issue for you. But it could be that it still fails as
the lib/system.h header (into which I hacked in the workaround) might be
not included in all places where CHAR_BIT is used in the Tar sources...

I'm getting ready to try this but you seemed to have applied fixes for AIX, not Solaris.
______________________________________________________________________
OpenPKG                                             http://openpkg.org
User Communication List                      [email protected]

Reply via email to