Re: [Cooker] perl5/man/ weirdness on alpha

2000-09-16 Thread Pixel
Stefan van der Eijk [EMAIL PROTECTED] writes: Problem solved I guess... ;-) Apache (one of the packages affected) just succesfuly compiled on my alpha! ok, good news :)

Re: [Cooker] perl5/man/ weirdness on alpha

2000-09-15 Thread Stefan van der Eijk
Pixel wrote: Stefan van der Eijk [EMAIL PROTECTED] writes: INSTALLMAN3DIR = /usr///lib/perl5/man/man3 it means the rpm macros are not uptodate for alpha... These rpm macro's? diff macros /usr/lib/rpm/macros oups, it must be the perl that is buggy in that case. try:

Re: [Cooker] perl5/man/ weirdness on alpha

2000-09-11 Thread Pixel
Stefan van der Eijk [EMAIL PROTECTED] writes: INSTALLMAN3DIR = /usr///lib/perl5/man/man3 it means the rpm macros are not uptodate for alpha...

Re: [Cooker] perl5/man/ weirdness on alpha

2000-09-11 Thread Stefan van der Eijk
INSTALLMAN3DIR = /usr///lib/perl5/man/man3 it means the rpm macros are not uptodate for alpha... These rpm macro's? diff macros /usr/lib/rpm/macros 222c222 %_archi386 --- %_archalpha 427,429c427,429 %_host

Re: [Cooker] perl5/man/ weirdness on alpha

2000-09-11 Thread Pixel
Stefan van der Eijk [EMAIL PROTECTED] writes: INSTALLMAN3DIR = /usr///lib/perl5/man/man3 it means the rpm macros are not uptodate for alpha... These rpm macro's? diff macros /usr/lib/rpm/macros oups, it must be the perl that is buggy in that case. try: eval "`perl

Re: [Cooker] perl5/man/ weirdness on alpha

2000-09-11 Thread Stefan van der Eijk
INSTALLMAN3DIR = /usr///lib/perl5/man/man3 it means the rpm macros are not uptodate for alpha... These rpm macro's? diff macros /usr/lib/rpm/macros oups, it must be the perl that is buggy in that case. try: eval "`perl -V:installarchlib`"; echo $installarchlib alpha: [stefan@alpha

Re: [Cooker] perl5/man/ weirdness on alpha

2000-09-11 Thread Pixel
Stefan van der Eijk [EMAIL PROTECTED] writes: INSTALLMAN3DIR = /usr///lib/perl5/man/man3 it means the rpm macros are not uptodate for alpha... These rpm macro's? diff macros /usr/lib/rpm/macros oups, it must be the perl that is buggy in that case. try: eval "`perl