The server and admin binarys are built and installed just fine however. The ./comfigure script has the following non fatal "error". configure: WARNING: Client build has been requested, but GL is not fully available (missing gl.h) ... disabling client generation No client binary (/usr/bin/bzflag?) is built or installed.
fix your opengl situation. Since you didn't include nearly enough information for us to help you though, you're on your own at this point.
(In reply to comment #1) > fix your opengl situation. Excuse me for not having a clue where gl.h comes from. > Since you didn't include nearly enough information for us to help you though, > you're on your own at this point. Excuse my assumption that the games developers would know what a configure script was and might acutally read the one included with this package. Excuse me for filing this bug.
why are you getting snippy ? you didnt really give us any information other than 'it failed' so how are we supposed to diagnosis the problem when it works just fine on our machines ? telling us a package 'is broken' when we have no problems with it is not helpful
(In reply to comment #3) > why are you getting snippy ? I was just returning the apathy. I did like the point that my opengl situation was the problem, although I don't see how that helps to fix a broken ebuild. If I get time(I probably won't) I will patch the configure script or ebuild add it to my overlay update this bug for someone who will care to see. > you didnt really give us any information other > than 'it failed' so how are we supposed to diagnosis the problem when it works > just fine on our machines ? You've missread the summary or maybe I've miswriten it, I was aweful brief. The `emerge bzflag` operation is "successful" but did not produce the client binary. Some of the binarys are built and installed(the server and the admin tool). But the client is not, because of the checking done with the configure script. ./configure --with-client produces a non fatal error. Perhaps I should have filed this bug upstream. > telling us a package 'is broken' when we have no > problems with it is not helpful It's only "broken" for me on this specific machine.