[Wouter Verhelst] > it's usually safe to trust the compiler to know what will be > fastest.
I agree. > Why have them in the first place? If you just remove them all, that > will surely fix the issue. To me it is more a question of how to be sure all of them are removed in a way that get insserv working. For that, I would like someone with m68k access to come up with a patch, thus making sure the patch actually solve the problem on m68k. Because of this, I hope you or someone else with m68k machines can provide a tested patch. >> What is the value of sizeof(regex_t) on m68k? What is the alignment >> calculated for the struct? > > sizeof(regex_t) is 30 on m68k, so I guess that's also what the > calculated alignment is. Now I am confused. The error complained that the alignment wasn't on 2-byte boundaries, if I understood it correctly. 30 is divisable by 2, and thus aligning on 30 byte boundaries should also be on 2-byte boundaries. How did it end up not being on 2-byte boundaries? What did I misunderstand? Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
