RPM multiarch/multilib Q (x864_64 vs sparc64 lands)

[Chris Kloiber]

On Mon, 2004-05-10 at 03:39, Balint Cristian wrote:
> Hi !
> 
> 	I would like to Q and clarify for me how multilib/multiarch work.
> 
> As I experience practicaly, if I have x86_64 glibc instaled on an amd64 for e.g
> i take rpm -ivh glibc*i686 and no problem rpm "decide" to not conflict with x86_64 and install smoothly inteligently,
> guessing that ppc/ppc64 too works in the same way (dont have the hw to play)
> 
> If I do "yum list | grep glibc-" I will see clearly it is there booth i686 and x86_64.
> 
> 	I have problems doing this on sparc/sparc64 lands in a FC2T3 enviroment (wich maintained for myself):
> 
> I allready have glibc-2.3.3-25.sparc.rpm installed but I want 64 bit ones too:
> ------------------------------------------//////////-------------------------->
> [root at sun RPMS]# rpm -ivh sparc64/glibc-2.3.3-25.sparc64.rpm
> Preparing...                ########################################### [100%]
>         package glibc-2.3.3-25 is already installed
>         file /sbin/ldconfig from install of glibc-2.3.3-25 conflicts with file from package glibc-2.3.3-25
>         file /sbin/sln from install of glibc-2.3.3-25 conflicts with file from package glibc-2.3.3-25
>         file /usr/sbin/glibc_post_upgrade from install of glibc-2.3.3-25 conflicts with file from package glibc-2.3.3-25
>         file /usr/sbin/iconvconfig from install of glibc-2.3.3-25 conflicts with file from package glibc-2.3.3-25
> -----------------------------------------/////////-------------------------------------->
> 
> I know is little bit I am maybe offtopic because FC not suport yet sparcs:
> 
> 	It is clear that not work in case of sparc64/sparc, but again the Q: this multilib is done from sort of rpmrc script or some other macro file
> or must see rpm sourcecode whats happening there ? Maybe someone lead me to exact source of problem.
> 
> 	Any hint/suggestion is welcome !
> 
> as Obs,i was using rpm-4.3.1-0.1 to be no doubt.

What you ask is far beyond my skills, but if you feel you're up to it
grab the source and see what it's doing for amd64 and ppc64 and try to
adapt it to sparc64. Bonus points for not breaking amd64 and ppc64 in
the process. You could also ask the Aurora Linux (sparc) people, as they
probably already face these issues.

-- 
Chris Kloiber