On Sun, 10 Jun 2007 17:19:43 +0900
Yasufumi Haga <[EMAIL PROTECTED]> wrote:

| On Sun, 10 Jun 2007 13:11:25 +0900
| Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote:
| 
| | On Sun, 10 Jun 2007 11:13:00 +0900 Yasufumi Haga <[EMAIL PROTECTED]>
| | babbled:
| | 
| | my guess is the AC_PATH_XTRA macros shipped with your distro don't cover the
| | locations x can be installed - like /usr/X11R6/... but your distro puts them
| | there. you could set CFLAGS and LDFLAGS to ass -I/usr/X11R6/include and
| | -L/usr/X11R6/lib to each. since you have things installed in :"non-standard
| | places" its often needed to do this. since xorg's move to use /usr instead
| | of /usr/X11R6 by default things are getting less friendly to
| | supporting /usr/X11R6 "out of the box" without extra env vars.
| 
| But I compiled imlib2 before compiling evas last night. configure.in of 
imlib2 has  AC_PATH_XTRA, too:
|   $ pwd
|   /home/fumi/src/e17/e17/libs/imlib2  
|   $ grep -i AC_PATH_XTRA *
|   configure.in:  AC_PATH_XTRA
| 
| and imlib2 was built normally. The config.log file created by autogen.sh of 
imlib2 has these lines:
|   configure:20130: checking for X
|   configure:20360: result: libraries /usr/X11R6/lib, headers 
/usr/X11R6/include
| 
| I wonder if it didn't mean AC_PATH_XTRA functioned correctly.
| AC_PATH_XTRA seems to be used by Eterm and E16, too.
| If AC_PATH_XTRA really doesn't cover "/usr/X11R6/lib", is it possible to 
build imlib2, Eterm, and E16 normally?

I added "AC_MSG_WARN(>>>>> $X_LIBS / $X_CFLAGS <<<<<)" to configure.in
after AC_PATH_XTRA macro of each of evas, imlib2, and e16, and run those 
autogen.sh files again
at the same time to know what value the macro returns. Here are what I modified 
in each configure.in:

1) evas :
if test "x$have_evas_software_x11" = "xyes"; then
  AC_PATH_XTRA
  AC_MSG_WARN(>>>>> $X_LIBS / $X_CFLAGS <<<<<)
  AC_CHECK_HEADER(X11/X.h,
    [
      AC_MSG_WARN(>>>>> $X_LIBS / $X_CFLAGS <<<<<)
      AC_DEFINE(BUILD_ENGINE_SOFTWARE_X11, 1, [Software X11 Rendering Backend])
      x_dir=${x_dir:-/usr/X11R6}
      x_cflags=${x_cflags:--I${x_includes:-$x_dir/include}}
      x_libs="${x_libs:--L${x_libraries:-$x_dir/lib}} -lX11 -lXext"
    ],
    [
      AC_MSG_RESULT(disabling software X11 engine)
      have_evas_software_x11="no"
    ]
  )
fi
AM_CONDITIONAL(BUILD_ENGINE_SOFTWARE_X11, test "x$have_evas_software_x11" = "xye
s")

2) imlib2
if test "x$have_x" = "xyes"; then
  AC_PATH_XTRA
  AC_MSG_WARN(>>>>> $X_LIBS / $X_CFLAGS <<<<<)
  x_dir=${x_dir:-/usr/X11R6}
  x_cflags=${x_cflags:--I${x_includes:-$x_dir/include}}
  x_libs="${x_libs:--L${x_libraries:-$x_dir/lib}} -lX11 -lXext"
  AM_CONDITIONAL(BUILD_X11, true)

3) e16
AC_PATH_X
AC_PATH_XTRA
AC_MSG_WARN(>>>>> $X_LIBS / $X_CFLAGS <<<<<)

AC_CHECK_HEADERS(alloca.h locale.h stdarg.h wctype.h)

And the results are:
1) evas
checking for IceConnectionNumber in -lICE... no
configure: WARNING: >>>>>  -LNONE /  -INONE <<<<<
checking for X11/X.h... (cached) yes
configure: WARNING: >>>>>  -LNONE /  -INONE <<<<<
checking whether software 16bit x11 backend is to be built... no

2) imlib2
checking for IceConnectionNumber in -lICE... yes
configure: WARNING: >>>>>  -L/usr/X11R6/lib /  -I/usr/X11R6/include <<<<<
checking for dlopen in -ldl... yes

3) e16
checking for IceConnectionNumber in -lICE... yes
configure: WARNING: >>>>>  -L/usr/X11R6/lib /  -I/usr/X11R6/include <<<<<
checking alloca.h usability... yes

According to the results above, it looks like somehow AC_PATH_XTRA macro didn't
work correctly in evas. I wonder why...

| | > Hello Massimo, Raster
| | > Thanks for your replies.
| | > Sorry, this mail is a bit long.
| | > 
| | > On Sun, 10 Jun 2007 09:01:44 +0900
| | > Yasufumi Haga <[EMAIL PROTECTED]> wrote:
| | > 
| | > | Hello Massimo
| | > | 
| | > | On Sat, 09 Jun 2007 17:02:42 +0200
| | > | Massimo Maiurana <[EMAIL PROTECTED]> wrote:
| | > | 
| | > | | Yasufumi Haga, il 09/06/2007 15:51, scrisse:
| | > | | > Hi all
| | > | | > 
| | > | | > I'm trying to compile evas which I checked out just now, 
| | > | | > but it's complaining that ld can't find "-lX11" :
| | > | | 
| | > | | [EMAIL PROTECTED]:/usr/X11R6/lib# ldconfig -p | grep libX11
| | > | |         libX11.so.6 (libc6) => /usr/X11R6/lib/libX11.so.6
| | > | |         libX11.so (libc6) => /usr/X11R6/lib/libX11.so
| | > | | 
| | > | | can you see the same output from ldconfig?
| | > | 
| | > | Yes, here's my result:
| | > | 
| | > | $ sudo /sbin/ldconfig -p | grep libX11
| | > |         libX11.so.6 (libc6) => /usr/X11R6/lib/libX11.so.6
| | > |         libX11.so (libc6) => /usr/X11R6/lib/libX11.so
| | > | 
| | > | $ slocate libX11
| | > | warning: slocate: warning: database /var/lib/slocate/slocate.db' is more
| | > | than 8 days old warning: Please make sure the daily cron job is enabled
| | > | in /etc/updatedb.conf /usr/X11R6/lib/libX11.so.6
| | > | /usr/X11R6/lib/libX11.a
| | > | /usr/X11R6/lib/libX11.so.6.2
| | > | /usr/X11R6/lib/libX11.so
| | > | 
| | > | In fact I'm using the distribution upgraded on April 13 this year, but
| | > | after upgrading it, I checked out e17 tree from the CVS and built it
| | > | successfully on May 13. Also I posted an update of the ja.po file for 
the
| | > | e17 I built to E-Intl ML on that day. Now I'm using the e17 built at 
that
| | > | time. It's very nice! 
| | > | 
| | > | | maybe you upgraded your X installation and now libraries are on a
| | > | | different path?
| | > | 
| | > | So, In that sense, I haven't changed my distribution including X since I
| | > | built e17 last time. I wonder why...
| | > 
| | > I think I found something.
| | > Here's a piece of config.log created by autogen.sh in evas tree I checked 
out
| | > today: autogen.sh seems to be unable to find my X11 library.
| | > 
| | > 
| | > configure:24138: checking X11/X.h usability
| | > configure:24150: gcc -c -g  conftest.c >&5
| | > configure:24156: $? = 0
| | > configure:24160: test -z 
| | >                          || test ! -s conftest.err
| | > configure:24163: $? = 0
| | > configure:24166: test -s conftest.o
| | > configure:24169: $? = 0
| | > configure:24179: result: yes
| | > configure:24183: checking X11/X.h presence
| | > configure:24193: gcc -E  conftest.c
| | > configure:24199: $? = 0
| | > configure:24219: result: yes
| | > configure:24254: checking for X11/X.h
| | > configure:24261: result: yes
| | > configure:24274: checking whether software x11 backend is to be built
| | > configure:24292: result: yes
| | > configure:24466: gcc -o conftest -g   conftest.c   -LNONE -lX11 >&5
| | > /usr/bin/ld: cannot find -lX11
| | > collect2: ld returned 1 exit status
| | > configure:24472: $? = 1
| | > configure: failed program was:
| | > | /* confdefs.h.  */
| | > | 
| | > | #define PACKAGE_NAME ""
| | > | #define PACKAGE_TARNAME ""
| | > | #define PACKAGE_VERSION ""
| | > | #define PACKAGE_STRING ""
| | > | #define PACKAGE_BUGREPORT ""
| | > | #define PACKAGE "evas"
| | > | #define VERSION "0.9.9.038"
| | > | #define STDC_HEADERS 1
| | > | #define HAVE_SYS_TYPES_H 1
| | > | #define HAVE_SYS_STAT_H 1
| | > | #define HAVE_STDLIB_H 1
| | > | #define HAVE_STRING_H 1
| | > | #define HAVE_MEMORY_H 1
| | > | #define HAVE_STRINGS_H 1
| | > | #define HAVE_INTTYPES_H 1
| | > | #define HAVE_STDINT_H 1
| | > | #define HAVE_UNISTD_H 1
| | > | #define HAVE_DLFCN_H 1
| | > | #ifdef __cplusplus
| | > | extern "C" void std::exit (int) throw (); using std::exit;
| | > | #endif
| | > | #define HAVE_ALLOCA_H 1
| | > | #define HAVE_ALLOCA 1
| | > | #define MODULE_ARCH "linux-gnu-i686"
| | > | #define HAVE_FONTCONFIG 1
| | > | #define HAVE_DLADDR 1
| | > | #define HAVE_FNMATCH 1
| | > | /* end confdefs.h.  */
| | > | 
| | > | /* Override any gcc2 internal prototype to avoid an error.  */
| | > | #ifdef __cplusplus
| | > | extern "C"
| | > | #endif
| | > | /* We use char because int might match the return type of a gcc2
| | > |    builtin and then its argument prototype would still apply.  */
| | > | char XOpenDisplay ();
| | > | int
| | > | main ()
| | > | {
| | > | XOpenDisplay ();
| | > |   ;
| | > |   return 0;
| | > | }
| | > 
| | > I built e16 three days ago (last Wednesday), and It finished without any
| | > error. In addition, I tried compiling Eterm 0.9.4 again just now and it's
| | > finished with no error. 
| 
| Regards.
| --Yasufumi
| 
| -------------------------------------------------------------------------
| This SF.net email is sponsored by DB2 Express
| Download DB2 Express C - the FREE version of DB2 express and take
| control of your XML. No limits. Just data. Click to get it now.
| http://sourceforge.net/powerbar/db2/
| _______________________________________________
| enlightenment-users mailing list
| enlightenment-users@lists.sourceforge.net
| https://lists.sourceforge.net/lists/listinfo/enlightenment-users

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to