Foomatic Compile fails

CrimsonBane · n00b Joined: 30 Mar 2003 Posts: 11

Hi, I am have the problem with foomatic compile failing on both 2.0.0 and 2.0.2 versions. I get the following error

Writing Makefile for Foomatic
==> Your Makefile has been rebuilt. <==
==> Please rerun the make command. <==
false
make: *** [Makefile] Error 1

!!! ERROR: net-print/foomatic-2.0.0 failed.
!!! Function perl-module_src_compile, Line 34, Exitcode 2
!!! compilation failed

I emerged the later version like one post said but it didn't help either. I also tried the -cups option in the make file and that did nothing. Any suggestions?

X-SoCiaL · Posted: Fri Jul 11, 2003 10:48 pm Post subject:

Got the same error
_________________
~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~
: Would I do it if I couldnt do it with a computer?
~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~'¨'~

kamilian · Posted: Sun Jul 13, 2003 5:54 am Post subject:

I believe I had that same error a while ago, and while I don't know what fixed it, I'll try and recall what I did between it not compiling and it compiling.

I started off wanting to emerge something like xfree or kdebase. Seeing as I had the cups USE flag set it needed Cups and Foomatic. When I did the first emerge xfree or emerge kdebase (or whatever pacakage I was installing) it failed at emerge foomatic. I started to manually install each package that did not have foomatic as a dependancy and then tried to compile foomatic again for the sake of it, and it compiled.

I never caught which package it was that helped as I didn't expect emerge foomatic to work, but after manually emerging everything I needed that didn't depend on foomatic, it worked.

Perhaps that can help someone narrow it down as to why it compiled after emerging a number of packages that Foomatic din't depend on.

As a side note, I was using a Portage tree snapshot from 29/06/2003.
_________________
May contain traces of nuts.

rafael · Apprentice Joined: 22 Jul 2002 Posts: 267

Mmmmmh... I have the same problem... help?

Jeremie · n00b Joined: 25 Jun 2003 Posts: 11

It has something to do with a file from perl having a modification time in the future. Try adjusting your date. It worked for me.

rafael · Apprentice Joined: 22 Jul 2002 Posts: 267

Oh... that worked!
yeay hurray!