This shows you the differences between two versions of the page.
Next revision Both sides next revision | |||
build:problems_with_compiling [2010/04/16 06:40] j.m created |
build:problems_with_compiling [2010/04/17 08:23] j.m |
||
---|---|---|---|
Line 13: | Line 13: | ||
One of two things happened. | One of two things happened. | ||
- | - You need to provide the **--with-newfaad** switch for ./configure <code>./configure --with-jsapi-include=xxxx --with-newfaad</code> This is needed for the linux distribution of Gentoo and Ubuntu. | + | - You need to provide the **<nowiki>--</nowiki>with-newfaad** switch for ./configure <code>./configure --with-jsapi-include=xxxx <nowiki>--</nowiki>with-newfaad</code> This is needed for the linux distribution of Gentoo and Ubuntu. |
- | - You do not need to give the --with-newfaad switch for ./configure. The solution is try the ./configure command without it **--with-newfaad**. | + | - You do not need to give the <nowiki>--</nowiki>with-newfaad switch for ./configure. The solution is try the ./configure command without it **<nowiki>--</nowiki>with-newfaad**. |
===== cputest or MM_MMX, MM_MMXEXT, MM_SSE, MM_SSE2, MM_3DNOW, MM_3DNOWEXT errors ===== | ===== cputest or MM_MMX, MM_MMXEXT, MM_SSE, MM_SSE2, MM_3DNOW, MM_3DNOWEXT errors ===== | ||
Line 22: | Line 22: | ||
===== gtkxxx fail ===== | ===== gtkxxx fail ===== | ||
- | If the ./configure command fails with the message saying "Cannot open gtkxxx", it usually means that pkg-config/gtk+/glib is not installed or configured properly. | + | If the ./configure command fails with the message saying "Cannot open gtkxxx", it usually means that pkg-config/GTK+/GLib is not installed or configured properly. |
You should make sure that you have pkg-config, pkg-config-dev, libgtk-dev, and glib-dev (or libglib-dev) packages properly installed so that you can compile with them. | You should make sure that you have pkg-config, pkg-config-dev, libgtk-dev, and glib-dev (or libglib-dev) packages properly installed so that you can compile with them. | ||
Line 42: | Line 42: | ||
If you have trouble with jsapi, one of two things has happened. | If you have trouble with jsapi, one of two things has happened. | ||
- | - If it had trouble finding jsapi.h, the solution is simple. <code>./configure --with-jsapi-include=xxxx [[--with-newfaad|for gentoo or ubuntu]]</code> Using the 'locate jsapi.h' command will usually find the directory you need with the jsapi.h file. Replace the xxxx is the directory where jsapi.h is. | + | - If it had trouble finding jsapi.h, the solution is simple. <code>./configure <nowiki>--</nowiki>with-jsapi-include=xxxx [[<nowiki>--</nowiki>with-newfaad|for gentoo or ubuntu]]</code> Using the 'locate jsapi.h' command will usually find the directory you need with the jsapi.h file. Replace the xxxx is the directory where jsapi.h is. |
- If there was a problem locating the library, the trouble could be several things. | - If there was a problem locating the library, the trouble could be several things. | ||
* One probability is the libjs.so, libsmjs.so, and other necessary libraries are not in the standard path. You can either add them to your path value or you can put symlinks /usr/lib to the libraries themselves. | * One probability is the libjs.so, libsmjs.so, and other necessary libraries are not in the standard path. You can either add them to your path value or you can put symlinks /usr/lib to the libraries themselves. |