sh openpkg.sh -t | tar xvf -
Then changed the following line in openpkg.spec:
<< line 765: LIBS="$LDFLAGS -lz -lbz2 -lbeecrypt"
>> line 765: LIBS="$LDFLAGS -lz -lbz2 -lbeecrypt -lgen"
and then issued ./openpkg.boot --prefix .... and I have now been thanked for flying openpkg. I believe what happened is the configure script for rpm detected libgen.h has a basename function, so it added that to the system.h header to be included. But when the config script sample program was compiled it failed to link because -lgen was left off, so it tried to compile the misc/basename.c file included with rpm. This of course causes a multiple declaration error for basename and fails.
Next on my list is to try on my O2 because I think I have more/different errors on that box for some reason. Then I will finish up by trying the openpkg in CURRENT. There are many packages that need tweaked to work on IRIX, but if the bootstrap works we should have a better change at ironing those problems out. FYI, one of the first big problems you will run in to is perl, more on that later.
Later.
-doug
On 8/13/05, Ralf S. Engelschall <[EMAIL PROTECTED]> wrote:
On Wed, Aug 10, 2005, Doug Summers wrote:
> Doug Henry wrote:
> >This error is very common under irix:
> >
> >/usr/freeware/bin/gcc -DHAVE_CONFIG_H -I. -I. -I.. -I. -I.. -I../popt
> >-DOPENPKG -DOPENPKG_IRIX -I/tmp/openpkg- 2.4.2/zlib-1.2.3
> >-I/tmp/openpkg-2.4.2/bzip2-1.0.3 -I/tmp/openpkg-2.4.2/beecrypt-4.1.2
> >-DOPENPKG -DOPENPKG_IRIX -I/tmp/openpkg-2.4.2/zlib-1.2.3
> >-I/tmp/openpkg-2.4.2/bzip2-1.0.3 -I/tmp/openpkg- 2.4.2/beecrypt-4.1.2 -O2
> >-D_GNU_SOURCE -D_REENTRANT -MT fts.lo -MD -MP -MF .deps/fts.Tpo -c fts.c
> >-o fts.o
> >fts.c: In function `Fts_open':
> >fts.c:181: error: invalid type argument of `unary *'
> >fts.c:222: error: invalid type argument of `unary *'
> >fts.c:231: error: invalid type argument of `unary *'
> >fts.c: In function `Fts_close':
> >fts.c:371: error: invalid type argument of `unary *'
> >fts.c: In function `Fts_read':
> >fts.c:545: error: invalid type argument of `unary *'
> >fts.c:568: error: invalid type argument of `unary *'
> >fts.c: In function `Fts_set':
> > fts.c:595: error: invalid type argument of `unary *'
> >fts.c: In function `Fts_children':
> >fts.c:611: error: invalid type argument of `unary *'
> >fts.c:624: error: invalid type argument of `unary *'
> >fts.c: In function `fts_build':
> >fts.c:825: error: invalid type argument of `unary *'
> >fts.c:849: error: invalid type argument of `unary *'
> >fts.c: In function `fts_stat':
> >fts.c:987: error: invalid type argument of `unary *'
> >fts.c: In function `fts_palloc':
> >fts.c:1152: error: invalid type argument of `unary *'
> >fts.c: In function `fts_safe_changedir':
> >fts.c:1227: error: invalid type argument of `unary *'
> >fts.c:1238: error: invalid type argument of `unary *'
> >make[2]: *** [fts.lo] Error 1
> >make[2]: Leaving directory `/tmp/openpkg- 2.4.2/rpm-4.2.1/rpmio'
> >make[1]: *** [all-recursive] Error 1
> >make[1]: Leaving directory `/tmp/openpkg-2.4.2/rpm-4.2.1'
> >make: *** [all] Error 2
> >+ exit 2
> >runscript:ERROR: script returned non-null value
> >
>
> >>> snip <<<
>
> This is very similar to what happened to me on AIX. Ralph had to tweak
> something within the rpm code to get past this.
Yes, although RPM is rather portable, it unfortunately has some very bad
pieces of C code (especially in this fts.c!) which have #ifdef sections
for all particular platforms. So, for each platform (class) one has to
add code there. I really hate RPM 4.2 for this (and hope it is gone in
RPM 4.4)...
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
The OpenPKG Project www.openpkg.org
User Communication List openpkg-users@openpkg.org
