I am wondering how much speed you gain installing i686 instead of i586 packages. I now my AMD-K6-2 500Mhz refuses to run i686 packages but i586 work fine for me (when I do uname -a linux tells me I run a i586 and rpm is smart enough to deny installation of any i686.rpm). So maybe i686 packages only work on certain systems. If you gain a lot of speed from your i686 it is woth the trouble but if it is only a few percent maybe it is a good idea to stick with i586 packages. Maybe those "invalid character 45" errors you got are causing all the trouble. >From all my experiments with linux I learned one thing: Playing with glibc = playing with fire (since a lot of application are using glibc). But if you fixed your problem I am still intrested to hear from you what it was. Marcus ----- Original Message ----- From: "Bill Piety" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, October 03, 2000 5:01 AM Subject: Re: [expert] giving up (for now) compiling packages > Praedor Tempus wrote: > > > OK, I am tired of a near unusable system because of the problems > > building packages on Mandrake 7.2beta so I am going with i586.rpms, > > except for those that I KNOW built properly for i686. > > > > I have replaced my glibc build - it built, but with a bunch of > > "invalid character 45" errors that make me a bit nervous about > > the integrity of the resultant i686.rpms. I have replaced a > > lot of things with the i586.rpms. One thing that I cannot > > get to work, no matter what, is the menu package. It installs > > fine (menu-2.1.5-28mdk OR menu-2.1.5-30mdk) but crash bigtime > > whenever "update-menus" is called. > > > > EVERY time something tries to make use of "update-menus" upon > > install results in segfault (core dump). Every time. It did > > this with the src build I compiled. It does it with each > > binary rpm I try. > > > > Does anyone have a functional 7.2beta menu rpm? > > > > I have gone back and made sure to RE-install the other rpms > > that are listed as dependencies for menu to no avail. > > It doesn't work. > > > > praedor > > > > Don't envy the loops you've been jumping thru with this. There was a 'bug' > > of a > > sort in glibc-2.1.3 concerning 'invalid character 45' errors and, for > example, 'full-config-sysdirs'. Essentially, each instance needed to be > converted to full_config_sysdirs. Do you have the offending output? There was > a patch out for glibc specifically directed > toward the invalid character 45 problem. > > ---------------------------------------------------------------------------- ---- > Keep in touch with http://mandrakeforum.com: > Subscribe the "[EMAIL PROTECTED]" mailing list. >
Keep in touch with http://mandrakeforum.com: Subscribe the "[EMAIL PROTECTED]" mailing list.
