Re: logrotate 3.7-2 and m68k
On Mon, Aug 02, 2004 at 11:51:17PM +0200, Wouter Verhelst wrote:
> On Mon, Aug 02, 2004 at 06:25:20PM +0100, Paul Martin wrote:
> > On Mon, Aug 02, 2004 at 01:43:00PM +0200, Jeroen van Wolffelaar wrote:
> > > gcc-3.0 isn't available in sid/sarge on m68k. Suppose that your package
> > > FTBFS's on m68k in sarge (I'm not saying it does, but it could easily be
> > > the case as at least the buildd that tried it failed to build it), then
> > > the security team has a real problem in case logrotate needs a security
> > > update some time in the future.
> > It is a FTBFS on sarge/m68k at the moment, but purely due to an
> > internal compiler error. I'm assuming that gcc-3.4 will be able to
> > compile it, but that's not currently in the sid chroot on crest, so I
> > wasn't able to test.
> I'm preparing to perform a build with gcc-3.4 on another m68k host,
> running unstable; I'll follow up with the results ASAP.
Hm. It didn't build, but that's probably because it doesn't use whatever
I specify as CC:
cc -Wall -D_GNU_SOURCE -DLinux -DVERSION=\"3.7\" -Wall -g -O2
-D_FILE_OFFSET_BITS=64 -c -o config.o config.c
config.c: In function `readConfigFile':
config.c:1052: internal compiler error: in add_insn_before, at
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bug reporting instructions, see
make: *** [config.o] Fout 1
make: Leaving directory
make: *** [build-stamp] Fout 2
That should start with `gcc-3.4' instead of just `cc', and yes, I've set
CC. How do I make the logrotate build system use the right compiler?
smog | bricks
AIR -- mud -- FIRE
soda water | tequila
-- with thanks to fortune