date:20060219

build problem related to libtool?

2006-02-19 Thread Axel Wernicke


Hi list,

while trying to build the latest development version of GIMP on OS X  
I got some errors. I tried to solve them with the gimp developers,  
but they told me that my problem is rather related to libtool then to  
the gimp itself. That is why I'd like to ask for your help.

The command that crashes the make is:

mkdir .libs
gcc -g -O2 -Wall -o .libs/gimp-2.3 -Wl,-rpath -Wl,\$ORIGIN/../lib  
app_procs.o main.o batch.o errors.o sanity.o units.o  -L/opt/local/ 
lib gui/libappgui.a actions/libappactions.a dialogs/libappdialogs.a  
menus/libappmenus.a display/libappdisplay.a tools/libapptools.a  
widgets/libappwidgets.a pdb/libapppdb.a vectors/libappvectors.a plug- 
in/libappplug-in.a core/libappcore.a paint/libapppaint.a xcf/ 
libappxcf.a text/libapptext.a file/libappfile.a config/libappconfig.a  
paint-funcs/libapppaint-funcs.a composite/libappcomposite.a base/ 
libappbase.a ../libgimpwidgets/.libs/libgimpwidgets-2.0.dylib /opt/ 
local/var/db/dports/build/_Users_axelwernicke/work/gimp-2.3.7/ 
libgimpconfig/.libs/libgimpconfig-2.0.dylib -L/usr/X11R6/lib ../ 
libgimpmodule/.libs/libgimpmodule-2.0.dylib ../libgimpcolor/.libs/ 
libgimpcolor-2.0.dylib ../libgimpthumb/.libs/ 
libgimpthumb-2.0.dylib ../libgimpmath/.libs/libgimpmath-2.0.dylib ../ 
libgimpconfig/.libs/libgimpconfig-2.0.dylib /opt/local/var/db/dports/ 
build/_Users_axelwernicke/work/gimp-2.3.7/libgimpbase/.libs/ 
libgimpbase-2.0.dylib /opt/local/var/db/dports/build/ 
_Users_axelwernicke/work/gimp-2.3.7/libgimpcolor/.libs/ 
libgimpcolor-2.0.dylib /opt/local/var/db/dports/build/ 
_Users_axelwernicke/work/gimp-2.3.7/libgimpmath/.libs/ 
libgimpmath-2.0.dylib ../libgimpbase/.libs/libgimpbase-2.0.dylib ../ 
regexrepl/libregex.a /opt/local/lib/libgtk-x11-2.0.dylib /opt/local/ 
lib/libgdk-x11-2.0.dylib /opt/local/lib/libatk-1.0.dylib /opt/local/ 
lib/libgdk_pixbuf-2.0.dylib /opt/local/lib/libtiff.dylib /opt/local/ 
lib/libjpeg.dylib /opt/local/lib/libpangocairo-1.0.dylib /opt/local/ 
lib/libcairo.dylib /opt/local/lib/libXrender.dylib -lX11 -lpng12 /opt/ 
local/lib/libart_lgpl_2.dylib /opt/local/lib/libpangoft2-1.0.dylib / 
opt/local/lib/libpango-1.0.dylib -lm /opt/local/lib/ 
libgobject-2.0.dylib /opt/local/lib/libgmodule-2.0.dylib /opt/local/ 
lib/libfontconfig.dylib /opt/local/lib/libexpat.dylib /opt/local/lib/ 
libfreetype.dylib -lz /opt/local/lib/libgthread-2.0.dylib /opt/local/ 
lib/libglib-2.0.dylib /opt/local/lib/libintl.dylib /opt/local/lib/ 
libiconv.dylib -lc

/usr/bin/ld: unknown flag: -rpath
collect2: ld returned 1 exit status
make[3]: *** [gimp-2.3] Error 1
make[2]: *** [all-recursive] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

The complete log of the build can be found at http://wernicke- 
online.net/temp/gimp2.3.7_build.log.
I'm running OS X on PPC with gcc 4.0.1. Unfortunately I can't figure  
out which version of libtool is used. Isn't there something like a  
libtool -v?


Greetings,

lexA

---
Live is like a chocolate box, you never know what you wanna get...
GPG Signatur auf http://wernicke-online.net/Impressum/ prüfen



PGP.sig
Description: Signierter Teil der Nachricht
___
http://lists.gnu.org/mailman/listinfo/libtool

Re: Setting environment variable in libtool wrapper?

2006-02-19 Thread Geoffrey Hutchison


Hi,

This may sound like a strange request, but for my project, libtool is  
used to generate the shared libs and binaries using automake. We also  
generate a series of plugins as shared modules (with -module). We  
have our own dlopen routines, so we don't use libltdl.


In particular, our loader routines will check an environment variable  
for a list of directories to search. This enables us to easily load  
the modules from the build directory.


What I'd really like to do is to set this environment variable inside  
the libtool wrapper generated for each binary. The default value can  
easily be determined at ./configure time.


Any suggestions? The documentation wasn't too helpful, and I did  
think about possible autoconf/automake tricks. But automake doesn't  
let you easily insert an "export ${VAR}" into a target AFAICT, and  
I'd rather do it at build/execution time rather than configure-time.


Thanks very much in advance,
-Geoff


___
http://lists.gnu.org/mailman/listinfo/libtool

Error 77, No acceptable C compiler found in the path

2006-02-19 Thread Bita Vafaei


Hello,

I have installed garnome-2.12.2.1 on my machine that has Fedora core4
(2.6.14-1.1656_FC4smp). I get Error 77 on bootstrap/libtool/ directory
saying checking for c compiler default output ...configure can not
create executables.

Can you help me?

Below is config.log :

This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by libtool configure 1.5.20, which was
generated by GNU Autoconf 2.59.  Invocation command line was

  $ ./configure 

## - ##
## Platform. ##
## - ##

hostname = localhost.localdomain
uname -m = i686
uname -r = 2.6.14-1.1656_FC4smp
uname -s = Linux
uname -v = #1 SMP Thu Jan 5 22:24:06 EST 2006

/usr/bin/uname -p = unknown
/bin/uname -X = unknown

/bin/arch  = i686
/usr/bin/arch -k   = unknown
/usr/convex/getsysinfo = unknown
hostinfo   = unknown
/bin/machine   = unknown
/usr/bin/oslevel   = unknown
/bin/universe  = unknown

PATH: /usr/kerberos/sbin
PATH: /usr/lib/globus/bin
PATH: /usr/lib/globus/sbin
PATH: /usr/kerberos/bin
PATH: /usr/local/bin
PATH: /usr/bin
PATH: /bin
PATH: /usr/X11R6/bin
PATH: /home/Bita/bin


## --- ##
## Core tests. ##
## --- ##

configure:1583: checking for a BSD-compatible install
configure:1638: result: /usr/bin/install -c
configure:1649: checking whether build environment is sane
configure:1692: result: yes
configure:1757: checking for gawk
configure:1773: found /usr/bin/gawk
configure:1783: result: gawk
configure:1793: checking whether make sets $(MAKE)
configure:1813: result: yes
configure:2073: checking for gcc
configure:2102: result: no
configure:2153: checking for cc
configure:2182: result: no
configure:2195: checking for cc
configure:2241: result: no
configure:2294: checking for cl
configure:2323: result: no
configure:2337: error: no acceptable C compiler found in $PATH
See `config.log' for more details.

##  ##
## Cache variables. ##
##  ##

ac_cv_env_CC_set=
ac_cv_env_CC_value=
ac_cv_env_CFLAGS_set=
ac_cv_env_CFLAGS_value=
ac_cv_env_CPPFLAGS_set=
ac_cv_env_CPPFLAGS_value=
ac_cv_env_CPP_set=
ac_cv_env_CPP_value=
ac_cv_env_CXXCPP_set=
ac_cv_env_CXXCPP_value=
ac_cv_env_CXXFLAGS_set=
ac_cv_env_CXXFLAGS_value=
ac_cv_env_CXX_set=
ac_cv_env_CXX_value=
ac_cv_env_F77_set=
ac_cv_env_F77_value=
ac_cv_env_FFLAGS_set=
ac_cv_env_FFLAGS_value=
ac_cv_env_LDFLAGS_set=
ac_cv_env_LDFLAGS_value=
ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_install='/usr/bin/install -c'
ac_cv_prog_AWK=gawk
ac_cv_prog_make_make_set=yes

## - ##
## Output variables. ##
## - ##

ACINCLUDE_M4_LIST='./acinclude.m4 ./cdemo/acinclude.m4 ./pdemo/acinclude.m4 
./demo/acinclude.m4 ./depdemo/acinclude.m4 ./mdemo/acinclude.m4 
./mdemo2/acinclude.m4 ./tagdemo/acinclude.m4 ./f77demo/acinclude.m4'
ACLOCAL='${SHELL} 
/home/Bita/garnome-2.12.2.1/bootstrap/libtool/download/libtool-1.5.20/missing 
--run aclocal-1.9'
AMDEPBACKSLASH=''
AMDEP_FALSE=''
AMDEP_TRUE=''
AMTAR='${SHELL} 
/home/Bita/garnome-2.12.2.1/bootstrap/libtool/download/libtool-1.5.20/missing 
--run tar'
AR=''
AS=''
AUTOCONF='${SHELL} 
/home/Bita/garnome-2.12.2.1/bootstrap/libtool/download/libtool-1.5.20/missing 
--run autoconf'
AUTOHEADER='${SHELL} 
/home/Bita/garnome-2.12.2.1/bootstrap/libtool/download/libtool-1.5.20/missing 
--run autoheader'
AUTOMAKE='${SHELL} 
/home/Bita/garnome-2.12.2.1/bootstrap/libtool/download/libtool-1.5.20/missing 
--run automake-1.9'
AWK='gawk'
CC=''
CCDEPMODE=''
CFLAGS=''
CONF_SUBDIRS='cdemo pdemo demo depdemo mdemo mdemo2 tagdemo f77demo'
CPP=''
CPPFLAGS=''
CXX=''
CXXCPP=''
CXXDEPMODE=''
CXXFLAGS=''
CYGPATH_W='echo'
DEFS=''
DEPDIR=''
DIST_MAKEFILE_LIST='cdemo/Makefile pdemo/Makefile demo/Makefile
depdemo/Makefile mdemo/Makefile mdemo2/Makefile tagdemo/Makefile
f77demo/Makefile '
DLLTOOL=''
ECHO='echo'
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EGREP=''
EXEEXT=''
F77=''
FFLAGS=''
GCJ=''
GCJFLAGS=''
HAVE_CXX_FALSE=''
HAVE_CXX_TRUE=''
HAVE_F77_FALSE=''
HAVE_F77_TRUE=''
HAVE_GCJ_FALSE=''
HAVE_GCJ_TRUE=''
HAVE_RC_FALSE=''
HAVE_RC_TRUE=''
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
INSTALL_STRIP_PROGRAM='${SHELL} $(install_sh) -c -s'
LD=''
LDFLAGS=''
LIBOBJS=''
LIBS=''
LIBTOOL=''
LN_S=''
LTLIBOBJS=''
MAKEINFO='${SHELL} 
/home/Bita/garnome-2.12.2.1/bootstrap/libtool/download/libtool-1.5.20/missing 
--run makeinfo'
NM=''
OBJDUMP=''
OBJEXT=''
PACKAGE='libtool'
PACKAGE_BUGREPORT='bug-libtool@gnu.org'
PACKAGE_NAME='libtool'
PACKAGE_STRING='libtool 1.5.20'
PACKAGE_TARNAME='libtool'
PACKAGE_VERSION='1.5.20'
PATH_SEPARATOR=':'
RANLIB=''
RC=''
SET_MAKE=''
SHELL='/bin/sh'
STRIP=''
TIMESTAMP=''
VERSION='1.5.20'
ac_ct_AR=''
ac_ct_AS=''
ac_ct_CC=''
ac_ct_CXX=''
ac_ct_DLLTOOL=''
ac_ct_F77=''
ac_ct_GCJ=''
ac_ct_OBJDUMP=''
ac_ct_RAN

Re: Setting environment variable in libtool wrapper?

2006-02-19 Thread Ralf Wildenhues

Hi Geoff,

* Geoffrey Hutchison wrote on Sat, Feb 18, 2006 at 11:07:57PM CET:
> 
> This may sound like a strange request, but for my project, libtool is  
> used to generate the shared libs and binaries using automake. We also  
> generate a series of plugins as shared modules (with -module). We  
> have our own dlopen routines, so we don't use libltdl.
> 
> In particular, our loader routines will check an environment variable  
> for a list of directories to search. This enables us to easily load  
> the modules from the build directory.

Would it also load modules without specifying a directory?  IOW: would
adjusting the uninstalled program's DT_RPATH (or equivalent) or
LD_LIBRARY_PATH (or equivalent) be sufficient, too?

> What I'd really like to do is to set this environment variable inside  
> the libtool wrapper generated for each binary. The default value can  
> easily be determined at ./configure time.

If above would suffice, that would be good.  I plan to add functionality
(post 2.0) anyway to specify
- add this directory to the list of uninstalled directories to be
  searched by the link editor
- add this directory to the list of uninstalled directories to be
  searched by the runtime linker and module loader

With those two new flags, it would be possible to seamlessly support
mixing of libtool libraries and non-libtool libraries in one build, as
well as libltdl modules and non-libltdl modules.  I think.  GCC needs
the former, for example.

I can't really offer you anything better at the moment, sorry.

Cheers,
Ralf


___
http://lists.gnu.org/mailman/listinfo/libtool

Re: Error 77, No acceptable C compiler found in the path

2006-02-19 Thread Ralf Wildenhues

Hi,

* Bita Vafaei wrote on Sun, Feb 19, 2006 at 03:42:52AM CET:
> 
> I have installed garnome-2.12.2.1 on my machine that has Fedora core4
> (2.6.14-1.1656_FC4smp). I get Error 77 on bootstrap/libtool/ directory
> saying checking for c compiler default output ...configure can not
> create executables.
> 
> Can you help me?

Yes.  It would be great if you installed a compiler.  GCC[1] has quite
good ones at the moment, and Fedora Core 4 even has them prepackaged
nicely.  I guess
  yum install gcc
should get you going.  If you need compilers for C++ or other languages,
install them, too, please (g++, gfortran etc).

Cheers,
Ralf

[1] http://gcc.gnu.org/


___
Bug-libtool mailing list
Bug-libtool@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-libtool

Re: build problem related to libtool?

2006-02-19 Thread Peter O'Gorman


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Axel Wernicke wrote:
| Hi list,
|
| while trying to build the latest development version of GIMP on OS X  I
| got some errors. I tried to solve them with the gimp developers,  but
| they told me that my problem is rather related to libtool then to  the
| gimp itself. That is why I'd like to ask for your help.
| The command that crashes the make is:

| /usr/bin/ld: unknown flag: -rpath
| collect2: ld returned 1 exit status
| make[3]: *** [gimp-2.3] Error 1
| make[2]: *** [all-recursive] Error 1
| make[1]: *** [all-recursive] Error 1
| make: *** [all] Error 2
|
| The complete log of the build can be found at http://wernicke-
| online.net/temp/gimp2.3.7_build.log.
| I'm running OS X on PPC with gcc 4.0.1. Unfortunately I can't figure
| out which version of libtool is used. Isn't there something like a
| libtool -v?

The libtool is in the build directory. Use `./libtool --version'. I'd be
interested in seeing the config.log too. Please gzip and attach. Thanks.

Peter
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Darwin)

iQCVAwUBQ/hBu7iDAg3OZTLPAQLAfQP/Une79Z+MzaNSF3wM6I+j6VftrYPl4KoV
MrUYPT7xZtbm/infYzkT5kpr9hcVfHHhTJP2VHcjfCWQhj4m3HHLOUggjQxLe97/
HCy2nVNnY0bHjsHQHuvTlnFpd18tyNjdYV8qYrWx9xH8OHEZrNRM0hfdf6GELSFP
m4ENjm7+q1w=
=2le9
-END PGP SIGNATURE-


___
http://lists.gnu.org/mailman/listinfo/libtool

Re: build problem related to libtool?

2006-02-19 Thread Peter O'Gorman


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Peter O'Gorman wrote:
| Axel Wernicke wrote:
| | Hi list,
| |
| | while trying to build the latest development version of GIMP on OS X  I
| | got some errors. I tried to solve them with the gimp developers,  but
| | they told me that my problem is rather related to libtool then to  the
| | gimp itself. That is why I'd like to ask for your help.
| | The command that crashes the make is:

|
| The libtool is in the build directory. Use `./libtool --version'. I'd be
| interested in seeing the config.log too. Please gzip and attach. Thanks.

hah, I should read properly before replying. I didn't notice that you had
put up a full build log. I see:

/bin/sh ../libtool --tag=CC --mode=link gcc  -g -O2 -Wall  -L/opt/local/lib
- -o gimp-2.3  -Wl,-rpath '-Wl,$ORIGIN/../lib'

I am downloading the gimp sources now to see where this is coming from.

Thanks,
Peter
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Darwin)

iQCVAwUBQ/hJU7iDAg3OZTLPAQJ4vQQAr3x8Fq7oammyJlNaUJYoupqDw7o8F/6Z
L47xkhzjwhAoqnLhfl62Gf6XN56e2XNfGzA6pF28bjgl5rZXq3uHCCxQiQ6KzElT
KlyA5tnYyhiJOn9DkCEAio0f1EKhKekcclyK5oy2UuIwSQW0Mu70qBSTKfDSrbt7
wdHW9EG3zsU=
=DMi0
-END PGP SIGNATURE-


___
http://lists.gnu.org/mailman/listinfo/libtool

Re: build problem related to libtool?

2006-02-19 Thread Peter O'Gorman


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Peter O'Gorman wrote:
| Axel Wernicke wrote:
| | Hi list,
| |
| | while trying to build the latest development version of GIMP on OS X  I
| | got some errors. I tried to solve them with the gimp developers,  but
| | they told me that my problem is rather related to libtool then to  the
| | gimp itself. That is why I'd like to ask for your help.
| | The command that crashes the make is:

The problem is here:


I think they want to check for gnu binutils to use -rpath $ORIGIN/../lib,
but I'm not sure. Right now they try to do this for OS != windows. Ick!

To make an app relocatable on Mac OS X, you have to do more work than this.
You need to link your libraries with an install_name (soname) of
@executable_path/../lib/libfoo.dylib, by far the easiest thing to do to make
apps relocatable is to build as normal with -Wl,-headerpad_max_install_names
~ in LDFLAGS, then you can fix things to have the @executable_path/ bit after
build using install_name_tool(1).

Not libtool's fault, sorry, now you've got to go back to the gimp developers.

Peter
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Darwin)

iQCVAwUBQ/hNsLiDAg3OZTLPAQL9KgP/YYbXiH/ntdWFSPYOhYje3ZCjE8WHHRKL
2bRPn+wqEcihOWDa2tg19x0dxKWfJ2NCbtWNPLjn8zutdbR1sUx/odg0U1cjE9jH
vQEAt0/FqOQmGRo2QSNkFjxbJRF2nuF7R5VQaG7NTy6h019Ra2K7X3ubh772LNRP
xnfVEtLkPE0=
=BAJD
-END PGP SIGNATURE-


___
http://lists.gnu.org/mailman/listinfo/libtool

Re: build problem related to libtool?

2006-02-19 Thread Axel Wernicke



Am 19.02.2006 um 11:32 schrieb Peter O'Gorman:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


I am downloading the gimp sources now to see where this is coming  
from.


I have a Portfile as well as an info file for fink here if that would  
be some help?




Thanks,
Peter
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.0 (Darwin)

iQCVAwUBQ/hJU7iDAg3OZTLPAQJ4vQQAr3x8Fq7oammyJlNaUJYoupqDw7o8F/6Z
L47xkhzjwhAoqnLhfl62Gf6XN56e2XNfGzA6pF28bjgl5rZXq3uHCCxQiQ6KzElT
KlyA5tnYyhiJOn9DkCEAio0f1EKhKekcclyK5oy2UuIwSQW0Mu70qBSTKfDSrbt7
wdHW9EG3zsU=
=DMi0
-END PGP SIGNATURE-



---
Live is like a chocolate box, you never know what you wanna get...
GPG Signatur auf http://wernicke-online.net/Impressum/ prüfen



PGP.sig
Description: Signierter Teil der Nachricht
___
http://lists.gnu.org/mailman/listinfo/libtool

Re: build problem related to libtool?

2006-02-19 Thread Axel Wernicke


Hi,

Am 19.02.2006 um 11:51 schrieb Peter O'Gorman:


-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Peter O'Gorman wrote:
| Axel Wernicke wrote:
| | Hi list,
| |
| | while trying to build the latest development version of GIMP on  
OS X  I
| | got some errors. I tried to solve them with the gimp  
developers,  but
| | they told me that my problem is rather related to libtool then  
to  the

| | gimp itself. That is why I'd like to ask for your help.
| | The command that crashes the make is:

The problem is here:


I think they want to check for gnu binutils to use -rpath  
$ORIGIN/../lib,
but I'm not sure. Right now they try to do this for OS != windows.  
Ick!


To make an app relocatable on Mac OS X, you have to do more work  
than this.

You need to link your libraries with an install_name (soname) of
@executable_path/../lib/libfoo.dylib, by far the easiest thing to  
do to make
apps relocatable is to build as normal with -Wl,- 
headerpad_max_install_names
~ in LDFLAGS, then you can fix things to have the @executable_path/  
bit after

build using install_name_tool(1).

Not libtool's fault, sorry, now you've got to go back to the gimp  
developers.




Thanks a lot for the analysis. That was really fast done. Now lets  
see what the GIMP people say :)


Greetings,

Axel

---
Live is like a chocolate box, you never know what you wanna get...
GPG Signatur auf http://wernicke-online.net/Impressum/ prüfen



PGP.sig
Description: Signierter Teil der Nachricht
___
http://lists.gnu.org/mailman/listinfo/libtool

Re: libtool (alpha)

2006-02-19 Thread Ralf Wildenhues

Hi Julien,

Ralf Wildenhues  gmx.de> writes:
> * Julien Lecomte wrote on Wed, Feb 15, 2006 at 04:51:54AM CET:
> > 
> > I've installed the libtool alpha cvs build under MinGW.
> > Configuration and install was made under mSys (after replacing 
> > config.{guess,sub}):
> > 
> > ../alpha/configure --prefix=/usr
> > make
> > 
> > Of note:  I configured and installed under mSys because under MinGW it 
> > fails (undefined reference to `lt_libltdl_LTX_preloaded_symbols')
> 
> Weird.  I haven't tested MinGW a while, but last time it worked fine.
> Need to look into this.  I have never tested MSYS, though.

Tested that now, with the stable MinGW/MSYS that I've had installed for
several months now.  Worked fine.  Except for two known issues, all tests
pass, too.

So, how can I reproduce the failure you have seen?  Versions, configure flags,
config.log (packed), make output?

Cheers,
Ralf



___
http://lists.gnu.org/mailman/listinfo/libtool

build problem related to libtool?

Re: Setting environment variable in libtool wrapper?

Error 77, No acceptable C compiler found in the path

Re: Setting environment variable in libtool wrapper?

Re: Error 77, No acceptable C compiler found in the path

Re: build problem related to libtool?

Re: build problem related to libtool?

Re: build problem related to libtool?

Re: build problem related to libtool?

Re: build problem related to libtool?

Re: libtool (alpha)

11 matches

Site Navigation

Mail list logo

Footer information