> >
> >
> > I built an rpm from source. As I'm building on and for an AMD K6, I said,
> > "--target=k6."
> >
> > I duly created /u02/summer/redhat/RPMSi586-pc-linux-gnu/k6/fetchmail-5.5.1-
> 1.k6
> > rpm, but find I can't install it:
> >
> > [root@dugite /root]# rpm --upgrade /u02/summer/redhat/RPMSi586-pc-linux-gn
> u/k6
> > /fetchmail-5.5
> > 1-1.k6.rpm
> > package fetchmail-5.5.1-1 is for a different architecture
> >
> > unless I specify --ignorearch
> >
> > What must I do to avoid having to specify this option each time?
> >
> >
>
> Unless the package has special assembler instructions like Mesa you
> shouldn't. In a K6/2 (notice this is not a plain K6) code compiled
> for K6 is slower that code you let alone ie compiled for 386.
>
Jean
Are you sure about this? I'm using gcc 2.95 which has special options for the
K6 family.
Checks...
Umm
We're both wrong. I have a fetchmail src.rpm to hand; it's trouble-free and
doesn't take long to build, so I did this:
rpm --rebuild --target k6 /u03/tobuild/fetchmail-5.5.0-1.src.rpm
and rpm ran gcc thus:
gcc -DHAVE_CONFIG_H -c -I. -I. -O2 socket.c
so it's compiling for i386
All I get is an rpm I can't install;-((
Wrote: /u02/summer/redhat/RPMSi686-pc-linux-gnu/k6/fetchmail-5.5.0-1.k6.rpm
Now..
It doesn't make sense to me that gcc should produce worse code for the K6 (it
IS a K6-II) if I tell it to compile for one than if I don't, but I will
compile something and check it out iff
1) I can coax rpm to build properly for the K6
2) I can coax rpm to install for it.
Any clues about how I do it?
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
