Re: question about CFLAGS modifiers to ./configure
Thanks for your help, I have the ideas quite much clearer now. It seems that libgnashserver depends on libgnashasobjs, and at the same time libgnashasobjs depends on libgnashserver too, which is something quite wierd. Is there a nice solution for this? I guess the right thing should be to tell upstream to unify the libraries into one, is there any other solution I can handle? Greetings and thanks, Miry --- Bernhard R. Link [EMAIL PROTECTED] escribió: This looks like the prime example of a error -Wl,-z,syms is there to catch. The library libgnashhashserver needs symbols from the library libgnashhasobjs, but does not link against this library. Without -Wl,-z,syms the linker supposes that this might be callbacks to the main program, and most programs using this lib link properly because they most likely also link against libgnashhasobjs. And if people realize they cannot link against libgnashhashserver without that lib they tend to not realize the error in hashserver but just adding linkining to hashobj (which might be an additional error, as linking against libs you do not need directly is an error, but in the common cases both errors do not show up and it just works so people do not suspect any bad). To fix this try to add something like (untested): libgnashhashserver_la_LIBADD = libgnashhashobjs.la __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about CFLAGS modifiers to ./configure
On Mon, Apr 03, 2006 at 10:33:21PM +0200, Miriam Ruiz wrote: Thanks for your help, I have the ideas quite much clearer now. It seems that libgnashserver depends on libgnashasobjs, and at the same time libgnashasobjs depends on libgnashserver too, which is something quite wierd. Is there a nice solution for this? I guess the right thing should be to tell upstream to unify the libraries into one, is there any other solution I can handle? Unifying the libs is the only way to do this cleanly, AFAIK. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: question about CFLAGS modifiers to ./configure
On Fri, Mar 31, 2006 at 08:41:22AM +0200, Miriam Ruiz wrote: --- Steve Langasek [EMAIL PROTECTED] escribió: This is discussed in policy 10.2. If your libraries are failing to link when using -z,defs, that's a bug in those libraries; anything that references symbols from other libraries on the system needs to link against those libraries. Thanks, I have no clue why the linker gives errors then. I'll send the reference to this conversation to upstream as I'm not sure to be able to fix that myself properly. It might be helpful to you (and others) if you posted the full error messages here as well, and provided a link to a source package. Odds are good that your upstream won't understand the error message any better than you do. :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: question about CFLAGS modifiers to ./configure
--- Steve Langasek [EMAIL PROTECTED] escribió: On Fri, Mar 31, 2006 at 08:41:22AM +0200, Miriam Ruiz wrote: --- Steve Langasek [EMAIL PROTECTED] escribió: This is discussed in policy 10.2. If your libraries are failing to link when using -z,defs, that's a bug in those libraries; anything that references symbols from other libraries on the system needs to link against those libraries. Thanks, I have no clue why the linker gives errors then. I'll send the reference to this conversation to upstream as I'm not sure to be able to fix that myself properly. It might be helpful to you (and others) if you posted the full error messages here as well, and provided a link to a source package. Odds are good that your upstream won't understand the error message any better than you do. :) My home connection is down so I can only read and write mail from work. My home server obviously is offline so I don't have it easy to put my packages available. The program is gnash ( http://bugs.debian.org/347352 ) and the problem is that, when linking the libraries, it gives unresolved symbols. I've managed to compile libbase and libgeometry adding AM_LDFLAGS to Makefile.am: libbase/Makefile.am: AM_LDFLAGS = $(OPENGL_LIBS) $(SDL_LIBS) $(LIBZ) $(JPEG_LIBS) libgeometry/Makefile.am: AM_LDFLAGS = $(OPENGL_LIBS) $(SDL_LIBS) -L../libbase -lgnashbase But I'm having serious problems with some of the other components. I can post the full error message if you might think it's interesting. I can also send my latest version of the debian/ directory to the bug report. I hope to have my home connection fixed soon (it's been about 3 weeks and 5 different technicians coming home to see it since it doesn't work). Any suggestion on how to make my packages available with only web access? Greetings and thanks, Miry __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about CFLAGS modifiers to ./configure
It seems that the linker options: -Wl,-z,defs are neccesary (for policy), but if you don't add this linker flags, it compiles and builds without problems. With them, it's hell. I've managed to compile libbase and libgeometry adding AM_LDFLAGS to Makefile.am: libbase/Makefile.am: AM_LDFLAGS = $(OPENGL_LIBS) $(SDL_LIBS) $(LIBZ) $(JPEG_LIBS) libgeometry/Makefile.am: AM_LDFLAGS = $(OPENGL_LIBS) $(SDL_LIBS) -L../libbase -lgnashbase But I'm having serious problems with some of the other components. I'm attaching the latest snapshot of my debian directory, as well as the .build file resulting from trying to build it. I'm getting tons of undefined references, some of which I don't seem to be able to get rid of. The source is not yet available as a tgz, as it is still under development in the CVS. To get it, you need to: export CVS_RSH=ssh cvs -z3 -d:pserver:[EMAIL PROTECTED]:/sources/gnash co gnash as described in http://www.gnu.org/software/gnash/ I've emailed upstream about it. Greetings, Miry __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com debian.tar.bz2 Description: pat1628936378 gnash_0.0.20060328-1_i386.build.bz2 Description: 2767681692-gnash_0.0.20060328-1_i386.build.bz2
Re: question about CFLAGS modifiers to ./configure
* Miriam Ruiz [EMAIL PROTECTED] [060331 10:38]: I'm attaching the latest snapshot of my debian directory, as well as the .build file resulting from trying to build it. I'm getting tons of undefined references, some of which I don't seem to be able to get rid of. This looks like the prime example of a error -Wl,-z,syms is there to catch. The library libgnashhashserver needs symbols from the library libgnashhasobjs, but does not link against this library. Without -Wl,-z,syms the linker supposes that this might be callbacks to the main program, and most programs using this lib link properly because they most likely also link against libgnashhasobjs. And if people realize they cannot link against libgnashhashserver without that lib they tend to not realize the error in hashserver but just adding linkining to hashobj (which might be an additional error, as linking against libs you do not need directly is an error, but in the common cases both errors do not show up and it just works so people do not suspect any bad). To fix this try to add something like (untested): libgnashhashserver_la_LIBADD = libgnashhashobjs.la Another problem your build log shows: grep -n rpath ../gnash_0.0.20060328-1_i386.build: 194:checking for rpath... yes [...] 591: [...] -Wl,--rpath -Wl,/home/inniyah/gnash/gnash/libbase/.libs [...] [...] 748: [...] -Wl,--rpath -Wl,/home/inniyah/gnash/gnash/libbase/.libs -Wl,--rpath -Wl,/home/inniyah/gnash/gnash/libgeometry/.libs [...] If your build finishes, you should make sure that either these rpaths are no longer there, or that those file are relinked later without those rpaths (libtool sometimes do funny things and might link things multiple times, the important part is that the libraries you finaly ship do not include any rpaths). Hochachtungsvoll, Bernhard R. Link -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about CFLAGS modifiers to ./configure
Bernhard R. Link wrote: Another problem your build log shows: grep -n rpath ../gnash_0.0.20060328-1_i386.build: 194:checking for rpath... yes [...] 591: [...] -Wl,--rpath -Wl,/home/inniyah/gnash/gnash/libbase/.libs [...] [...] 748: [...] -Wl,--rpath -Wl,/home/inniyah/gnash/gnash/libbase/.libs -Wl,--rpath -Wl,/home/inniyah/gnash/gnash/libgeometry/.libs [...] You probably can solve this by passing --disable-rpath to ./configure. -- Felipe Sateler -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
question about CFLAGS modifiers to ./configure
Hi, DebHelper uses by default (in the pre-made templates) -Wl,-z,defs in CFLAGS when running ./configure CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --host=$(DEB_HOST_GNU_TYPE) ... I'm packaging a program (with some libraries in it) that won't compile with them unless you explicitly modify Makefile.am files and add the libraries (already included in the package but not installed in time of compilation), which is not done by default. without those options it compiles and install cleanly without problem with upstream's building system. Is it important to keep them? Could someone possibly explain to me what they mean? Lots of thanks!!! Miry __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about CFLAGS modifiers to ./configure
On Thu, Mar 30, 2006 at 06:23:38PM +0200, Miriam Ruiz wrote: Hi, DebHelper uses by default (in the pre-made templates) -Wl,-z,defs in CFLAGS when running ./configure CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --host=$(DEB_HOST_GNU_TYPE) ... I'm packaging a program (with some libraries in it) that won't compile with them unless you explicitly modify Makefile.am files and add the libraries (already included in the package but not installed in time of compilation), which is not done by default. without those options it compiles and install cleanly without problem with upstream's building system. Are you talking about the combination of CFLAGS foo above, and libraries build and used by the package? man ld explains -z defs: Disallows undefined symbols in object files. Undefined symbols in shared libraries are still allowed. Note that some ./configure scripts recommend to be called with CFLAGS transposed, as in: ./configure --host=$(...) CFLAGS=$(CFLAGS) Note also that -O2 should be used only if DEB_BUILD_OPTIONS!~noopt. What is the command, and error, when you try to use the libs, and those options? Is it important to keep them? Could someone possibly explain to me what they mean? You will probably have to use the examples from dh_shlibdeps to get proper dependencies on the shared libraries in that package, used by any binaries it creates. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about CFLAGS modifiers to ./configure
I demand that Miriam Ruiz may or may not have written... DebHelper uses by default (in the pre-made templates) -Wl,-z,defs in CFLAGS when running ./configure CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --host=$(DEB_HOST_GNU_TYPE) ... -Wl,-z,defs in CFLAGS causes warnings about unused linker flags. It belongs in LDFLAGS. [snip] -- | Darren Salt| linux or ds at | nr. Ashington, | Toon | RISC OS, Linux | youmustbejoking,demon,co,uk | Northumberland | Army | + At least 4000 million too many people. POPULATION LEVEL IS UNSUSTAINABLE. Power corrupts, and absolute power corrupts absolutely. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about CFLAGS modifiers to ./configure
On Thu, Mar 30, 2006 at 08:23:38PM +0100, Darren Salt wrote: I demand that Miriam Ruiz may or may not have written... DebHelper uses by default (in the pre-made templates) -Wl,-z,defs in CFLAGS when running ./configure CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --host=$(DEB_HOST_GNU_TYPE) ... -Wl,-z,defs in CFLAGS causes warnings about unused linker flags. It belongs in LDFLAGS. Good point :) This is #338990. Justin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: question about CFLAGS modifiers to ./configure
On Thu, Mar 30, 2006 at 06:23:38PM +0200, Miriam Ruiz wrote: DebHelper uses by default (in the pre-made templates) -Wl,-z,defs in CFLAGS when running ./configure CFLAGS=-Wall -g -O2 -Wl,-z,defs ./configure --host=$(DEB_HOST_GNU_TYPE) ... I'm packaging a program (with some libraries in it) that won't compile with them unless you explicitly modify Makefile.am files and add the libraries (already included in the package but not installed in time of compilation), which is not done by default. without those options it compiles and install cleanly without problem with upstream's building system. Is it important to keep them? Could someone possibly explain to me what they mean? This is discussed in policy 10.2. If your libraries are failing to link when using -z,defs, that's a bug in those libraries; anything that references symbols from other libraries on the system needs to link against those libraries. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ signature.asc Description: Digital signature
Re: question about CFLAGS modifiers to ./configure
--- Steve Langasek [EMAIL PROTECTED] escribió: This is discussed in policy 10.2. If your libraries are failing to link when using -z,defs, that's a bug in those libraries; anything that references symbols from other libraries on the system needs to link against those libraries. Thanks, I have no clue why the linker gives errors then. I'll send the reference to this conversation to upstream as I'm not sure to be able to fix that myself properly. Greetings, Miry __ LLama Gratis a cualquier PC del Mundo. Llamadas a fijos y móviles desde 1 céntimo por minuto. http://es.voice.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
