Martin Michlmayr <[EMAIL PROTECTED]> writes: > * Ben Pfaff <[EMAIL PROTECTED]> [2006-03-15 12:13]: >> This appears to be a bug in the GCC_STACK_PROTECT_CC macro. It >> assumes that if a compile with -fstack-protector succeeds, then >> it can use it. > >> I think that using AC_TRY_LINK in place of AC_TRY_COMPILE (within >> GCC_STACK_PROTECT_CC) might solve the problem. I haven't tried >> it though. > > I edited aclocal.m4 and susbstited AC_TRY_COMPILE with AC_TRY_LINK > within GCC_STACK_PROTECT_CC. This didn't change anything, though. > Was this the correct change or do I need to regenerate some files (and > how?) after editing this .m4 file?
Well, aclocal.m4 is itself supposed to be a generated file (generated by "aclocal") but I don't see the proper sources for it anywhere in Debian. Perhaps the package maintainer has never needed to regenerate it, or perhaps I don't know where to look. After updating aclocal.m4, you'd need to run `autoconf'. It seems like the Makefile should do that for you, but it couldn't hurt to do it by hand, I guess. Does that make any difference? -- Ben Pfaff email: [EMAIL PROTECTED] web: http://benpfaff.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
