After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 681076 - "gnet" optional dependancy? autogen.sh crashes
"gnet" optional dependancy? autogen.sh crashes
Status: RESOLVED NOTABUG
Product: gcompris
Classification: Other
Component: general
unspecified
Other Linux
: Normal minor
: ---
Assigned To: Bruno Coudoin
Rami Aubourg-Kaires
Depends on:
Blocks:
 
 
Reported: 2012-08-02 14:57 UTC by Peter Albrecht
Modified: 2012-08-03 07:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Peter Albrecht 2012-08-02 14:57:21 UTC 
I just cloned https://github.com/bdoin/GCompris to my local machine (gentoo linux) and wanted to compile.

But "sh autogen.sh" tells me:
---------------------------- 8< ----------------------------
[...]
checking for AUDIO... yes
checking wether we build with GNET (if not, networking will be disabled)... yes
checking for GNET... no
configure: error: *** GNET not found!
---------------------------- >8 ----------------------------
and exits with "$? = 1".

It is correct, I have not installed gnet. But I read "if not, networking will be disabled" as: "Having gnet not installed, you can compile GCompris, but networking will not work".

That would be exactly what I want. But I can't compile, since autogen.sh terminates with an error.

---------------------------------
As a workaround I simply will install gnet, but I think this might be a bug in autogen.sh.
Comment 1 Peter Albrecht 2012-08-02 14:58:45 UTC 
This bug might be spare, if gnet will be removed completely. See bug #593656
Comment 2 Bruno Coudoin 2012-08-02 17:00:56 UTC 
You must use the command:
sh configure --disable-gnet
Comment 3 Peter Albrecht 2012-08-02 21:14:24 UTC 
Thanks for the reply!

So I run the following?

 1. sh configure --disable-gnet
 2. sh autogen.sh
 3. make

Or does "configure" replace "autogen"?
Comment 4 Peter Albrecht 2012-08-03 07:18:06 UTC 
I found the answer myself:

Running "sh autogen.sh" prints:
-------------------- 8< --------------------
**Warning**: I am going to run `configure' with no arguments.
If you wish to pass any to it, please specify them on the
`autogen.sh' command line.
-------------------- >8 --------------------