[opensuse-buildservice] linking with X11 in OBS
Hi, I am trying to compile a Tcl/Tk extension that uses X11. I can successfully compile it on my local machine (direct - not in a local OBS) and it compiles just fine. I use the same commands I see in the OBS log. Oddly, when the application is being linked in OBS, it complains about some missing functions that I really think should be resolved. Especially since the same command works on my system. For example: gcc -DPACKAGE_NAME=\"TkXext\" -DPACKAGE_TARNAME=\"tkxext\" - DPACKAGE_VERSION=\"3.6.13\" -DPACKAGE_STRING=\"TkXext\ 3.6.13\" - DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DBUILD_TkXext=/\*\*/ - DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 - DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 - DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 - DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 - DMODULE_SCOPE=extern\ __attribute__\(\(__visibility__\(\"hidden\"\)\)\) - DHAVE_NO_SEH=1 -DEXCEPTION_DISPOSITION=int -DHAVE_CAST_TO_UNION=1 - D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 - DHAVE_OPEN64=1 -DHAVE_LSEEK64=1 -DHAVE_TYPE_OFF64_T=1 -DUSE_TCL_STUBS=1 - DUSE_TK_STUBS=1 -DPIC -I"/usr/include" -I"/usr/include" -pipe -O2 -fomit- frame-pointer -DNDEBUG -Wall -fPIC -lX11 -L/usr/lib -ltclstub8.5 -L/usr/lib -ltkstub8.5 -lXext -lXtst `echo ./unix/TkXext.record.c` -o txerecord [ 74s] ./unix/TkXext.record.c: In function 'main': [ 74s] ./unix/TkXext.record.c:131:9: warning: variable 'w' set but not used [-Wunused-but-set-variable] [ 74s] /tmp/ccofzMaU.o: In function `.L30': [ 74s] TkXext.record.c:(.text+0x26a): undefined reference to `XkbKeycodeToKeysym' [ 74s] /tmp/ccofzMaU.o: In function `.L27': [ 74s] TkXext.record.c:(.text+0x289): undefined reference to `XRecordFreeData' [ 74s] /tmp/ccofzMaU.o: In function `main': [ 74s] TkXext.record.c:(.text.startup+0x3a): undefined reference to `XOpenDisplay' [ 74s] TkXext.record.c:(.text.startup+0x54): undefined reference to `XSynchronize' [ 74s] TkXext.record.c:(.text.startup+0x6c): undefined reference to `XRecordQueryVersion' [ 74s] TkXext.record.c:(.text.startup+0x79): undefined reference to `XRecordAllocRange' [ 74s] TkXext.record.c:(.text.startup+0xbd): undefined reference to `XRecordCreateContext' [ 74s] TkXext.record.c:(.text.startup+0xcd): undefined reference to `XOpenDisplay' [ 74s] TkXext.record.c:(.text.startup+0xdb): undefined reference to `XFlush' [ 74s] TkXext.record.c:(.text.startup+0xe3): undefined reference to `XFlush' [ 74s] TkXext.record.c:(.text.startup+0x101): undefined reference to `XRecordEnableContext' Shouldn't XOpenDisplay and the others have been resolved by -lX11 My spec file says: BuildRequires: xorg-x11-devel tcl tcl-devel tk-devel libXext-devel which I would think would cover it. I am not getting a message that a library cannot be found. It you are curious, the extension is: https://build.opensuse.org/package/show/home:rogeroberholtzer/TkXext -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Mar 10, 2014 at 01:25:48PM +0100, Roger Oberholtzer wrote:
Hi,
I am trying to compile a Tcl/Tk extension that uses X11. I can successfully compile it on my local machine (direct - not in a local OBS) and it compiles just fine. I use the same commands I see in the OBS log. Oddly, when the application is being linked in OBS, it complains about some missing functions that I really think should be resolved. Especially since the same command works on my system.
The order on the linker line is important, libraries need to come rightmost. Ciao, Marcus
For example:
gcc -DPACKAGE_NAME=\"TkXext\" -DPACKAGE_TARNAME=\"tkxext\" - DPACKAGE_VERSION=\"3.6.13\" -DPACKAGE_STRING=\"TkXext\ 3.6.13\" - DPACKAGE_BUGREPORT=\"\" -DPACKAGE_URL=\"\" -DBUILD_TkXext=/\*\*/ - DSTDC_HEADERS=1 -DHAVE_SYS_TYPES_H=1 -DHAVE_SYS_STAT_H=1 -DHAVE_STDLIB_H=1 - DHAVE_STRING_H=1 -DHAVE_MEMORY_H=1 -DHAVE_STRINGS_H=1 -DHAVE_INTTYPES_H=1 - DHAVE_STDINT_H=1 -DHAVE_UNISTD_H=1 -DHAVE_LIMITS_H=1 -DHAVE_SYS_PARAM_H=1 - DUSE_THREAD_ALLOC=1 -D_REENTRANT=1 -D_THREAD_SAFE=1 -DTCL_THREADS=1 - DMODULE_SCOPE=extern\ __attribute__\(\(__visibility__\(\"hidden\"\)\)\) - DHAVE_NO_SEH=1 -DEXCEPTION_DISPOSITION=int -DHAVE_CAST_TO_UNION=1 - D_LARGEFILE64_SOURCE=1 -DTCL_WIDE_INT_TYPE=long\ long -DHAVE_STRUCT_STAT64=1 - DHAVE_OPEN64=1 -DHAVE_LSEEK64=1 -DHAVE_TYPE_OFF64_T=1 -DUSE_TCL_STUBS=1 - DUSE_TK_STUBS=1 -DPIC -I"/usr/include" -I"/usr/include" -pipe -O2 -fomit- frame-pointer -DNDEBUG -Wall -fPIC -lX11 -L/usr/lib -ltclstub8.5 -L/usr/lib -ltkstub8.5 -lXext -lXtst `echo ./unix/TkXext.record.c` -o txerecord
[ 74s] ./unix/TkXext.record.c: In function 'main': [ 74s] ./unix/TkXext.record.c:131:9: warning: variable 'w' set but not used [-Wunused-but-set-variable] [ 74s] /tmp/ccofzMaU.o: In function `.L30': [ 74s] TkXext.record.c:(.text+0x26a): undefined reference to `XkbKeycodeToKeysym' [ 74s] /tmp/ccofzMaU.o: In function `.L27': [ 74s] TkXext.record.c:(.text+0x289): undefined reference to `XRecordFreeData' [ 74s] /tmp/ccofzMaU.o: In function `main': [ 74s] TkXext.record.c:(.text.startup+0x3a): undefined reference to `XOpenDisplay' [ 74s] TkXext.record.c:(.text.startup+0x54): undefined reference to `XSynchronize' [ 74s] TkXext.record.c:(.text.startup+0x6c): undefined reference to `XRecordQueryVersion' [ 74s] TkXext.record.c:(.text.startup+0x79): undefined reference to `XRecordAllocRange' [ 74s] TkXext.record.c:(.text.startup+0xbd): undefined reference to `XRecordCreateContext' [ 74s] TkXext.record.c:(.text.startup+0xcd): undefined reference to `XOpenDisplay' [ 74s] TkXext.record.c:(.text.startup+0xdb): undefined reference to `XFlush' [ 74s] TkXext.record.c:(.text.startup+0xe3): undefined reference to `XFlush' [ 74s] TkXext.record.c:(.text.startup+0x101): undefined reference to `XRecordEnableContext'
Shouldn't XOpenDisplay and the others have been resolved by -lX11
My spec file says:
BuildRequires: xorg-x11-devel tcl tcl-devel tk-devel libXext-devel
which I would think would cover it. I am not getting a message that a library cannot be found.
It you are curious, the extension is:
https://build.opensuse.org/package/show/home:rogeroberholtzer/TkXext
-- Yours sincerely,
Roger Oberholtzer
Ramböll RST / Systems
Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________
Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
-- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Monday, March 10, 2014 01:36:55 PM Marcus Meissner wrote:
On Mon, Mar 10, 2014 at 01:25:48PM +0100, Roger Oberholtzer wrote:
Hi,
I am trying to compile a Tcl/Tk extension that uses X11. I can successfully compile it on my local machine (direct - not in a local OBS) and it compiles just fine. I use the same commands I see in the OBS log. Oddly, when the application is being linked in OBS, it complains about some missing functions that I really think should be resolved. Especially since the same command works on my system.
The order on the linker line is important, libraries need to come rightmost.
That was my first thought. I did not really want to fiddle with the configure stuff to change this unless there was no other option. But I guess I will. I am still curious why the EXACT same (cut and paste from OBS Log-> command line) command works on my system. The order of the libs was the same. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Mar 10, 2014 at 01:45:46PM +0100, Roger Oberholtzer wrote:
On Monday, March 10, 2014 01:36:55 PM Marcus Meissner wrote:
On Mon, Mar 10, 2014 at 01:25:48PM +0100, Roger Oberholtzer wrote:
Hi,
I am trying to compile a Tcl/Tk extension that uses X11. I can successfully compile it on my local machine (direct - not in a local OBS) and it compiles just fine. I use the same commands I see in the OBS log. Oddly, when the application is being linked in OBS, it complains about some missing functions that I really think should be resolved. Especially since the same command works on my system.
The order on the linker line is important, libraries need to come rightmost.
That was my first thought. I did not really want to fiddle with the configure stuff to change this unless there was no other option. But I guess I will.
I am still curious why the EXACT same (cut and paste from OBS Log-> command line) command works on my system. The order of the libs was the same.
The build system builds with --as-needed by default, your local system probably not. Ciao, Marcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Monday 2014-03-10 13:49, Marcus Meissner wrote:
I am still curious why the EXACT same (cut and paste from OBS Log-> command line) command works on my system. The order of the libs was the same.
The build system builds with --as-needed by default, your local system probably not.
That raises the question why our local systems default to --no-as-needed, when the rpms for BS and local should be the same, and there is no as.needed directive in /etc/rpm or /usr/lib/rpm visible.. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Mon, Mar 10, 2014 at 02:39:44PM +0100, Jan Engelhardt wrote:
On Monday 2014-03-10 13:49, Marcus Meissner wrote:
I am still curious why the EXACT same (cut and paste from OBS Log-> command line) command works on my system. The order of the libs was the same.
The build system builds with --as-needed by default, your local system probably not.
That raises the question why our local systems default to --no-as-needed, when the rpms for BS and local should be the same, and there is no as.needed directive in /etc/rpm or /usr/lib/rpm visible..
Good question. binutils-build-as-needed.diff + if (getenv ("SUSE_ASNEEDED") && atoi(getenv ("SUSE_ASNEEDED")) > 0) + input_flags.add_DT_NEEDED_for_regular = TRUE; so basically we can either set SUSE_ASNEEDED=1 in some environemnt script, or adjust the patch to do = TRUE when no SUSE_ASNEEDED is present,. Ciao, MArcus -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 10.03.2014 14:46, Marcus Meissner wrote:
On Mon, Mar 10, 2014 at 02:39:44PM +0100, Jan Engelhardt wrote:
On Monday 2014-03-10 13:49, Marcus Meissner wrote:
I am still curious why the EXACT same (cut and paste from OBS Log-> command line) command works on my system. The order of the libs was the same.
The build system builds with --as-needed by default, your local system probably not.
That raises the question why our local systems default to --no-as-needed, when the rpms for BS and local should be the same, and there is no as.needed directive in /etc/rpm or /usr/lib/rpm visible..
Good question.
binutils-build-as-needed.diff + if (getenv ("SUSE_ASNEEDED") && atoi(getenv ("SUSE_ASNEEDED")) > 0) + input_flags.add_DT_NEEDED_for_regular = TRUE;
so basically we can either set SUSE_ASNEEDED=1 in some environemnt script, or adjust the patch to do = TRUE when no SUSE_ASNEEDED is present,.
If you want as-needed as default everywhere, you should convince upstream binutils developers. Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Monday 2014-03-10 14:46, Marcus Meissner wrote:
The build system builds with --as-needed by default, your local system probably not.
That raises the question why our local systems default to --no-as-needed, when the rpms for BS and local should be the same, and there is no as.needed directive in /etc/rpm or /usr/lib/rpm visible..
Good question.
And the answer is: $ grep -r NEEDED . ./profile.d/suse-buildsystem.sh:export SUSE_ASNEEDED=1 $ rpm -qf /etc/profile.d/suse-buildsystem.sh post-build-checks-1.0-119.1.2.noarch So whenever someone happens to have PBC installed, the behavior of ld suddenly changes. I would say that is "spooky action at a distance", or the antithesis to "principle of least surprise". It would be good to have SUSE_ASNEEDED -- whichever value (unset|1) it will attain -- to be consistent across both the default system and the build setup. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
Am 10.03.2014 20:04, schrieb Jan Engelhardt:
So whenever someone happens to have PBC installed, the behavior of ld suddenly changes. I would say that is "spooky action at a distance",
Actually I used to block post-build-checks and other build tools from FTP repo to avoid people even trying - but people want them to use other tools to build our packages, so they are there. But still the chances that random people install random packages and wonder about random bugs are slim enough to warrant the behaviour.
or the antithesis to "principle of least surprise". It would be good to have SUSE_ASNEEDED -- whichever value (unset|1) it will attain -- to be consistent across both the default system and the build setup.
It's a feature that our packages default to as-needed to avoid unnecessary dependencies. And it's a feature that our binutils behave like everyone else's binutils if you compile your own software. And I agree these features don't go together without problems - but we live with the current problem long enough not to question the solution. Greetings, Stephan -- Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die ganze Welt an Arsch offen hat, oder grad deswegn. -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday 2014-03-11 08:00, Stephan Kulow wrote:
or the antithesis to "principle of least surprise". It would be good to have SUSE_ASNEEDED -- whichever value (unset|1) it will attain -- to be consistent across both the default system and the build setup.
It's a feature that our packages default to as-needed to avoid unnecessary dependencies.
Heh, but there's more to it than just _that_ :) It also flagged software packages which failed to adhere to object file ordering on the linker line, something that is required _anyway_ if not using the GNU linkers. So people were taught a lesson, and they learned. So I guess what I would want normal everyone in non-build chroot to have is order enforcement rather than as-needed. (I'll leave it at that.) -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Tuesday, March 11, 2014 09:56:48 AM Jan Engelhardt wrote:
On Tuesday 2014-03-11 08:00, Stephan Kulow wrote:
or the antithesis to "principle of least surprise". It would be good to have SUSE_ASNEEDED -- whichever value (unset|1) it will attain -- to be consistent across both the default system and the build setup.
It's a feature that our packages default to as-needed to avoid unnecessary dependencies.
Heh, but there's more to it than just _that_ :)
It also flagged software packages which failed to adhere to object file ordering on the linker line, something that is required _anyway_ if not using the GNU linkers. So people were taught a lesson, and they learned. So I guess what I would want normal everyone in non-build chroot to have is order enforcement rather than as-needed. (I'll leave it at that.)
libA uses something in libB, which uses something in libA. You might argue bad design. But that does happen. I have done silly things like: -lA -lB -lA But that is not pretty. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On 10.03.2014 14:39, Jan Engelhardt wrote:
On Monday 2014-03-10 13:49, Marcus Meissner wrote:
I am still curious why the EXACT same (cut and paste from OBS Log-> command line) command works on my system. The order of the libs was the same.
The build system builds with --as-needed by default, your local system probably not.
That raises the question why our local systems default to --no-as-needed, when the rpms for BS and local should be the same, and there is no as.needed directive in /etc/rpm or /usr/lib/rpm visible..
Of course a local osc will default to as-needed too, but outside of rpm build environments, binutils will behave like upstream. /etc/profile.d/suse-buildsystem.sh:export SUSE_ASNEEDED=1 Greetings, Stephan -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Monday, March 10, 2014 01:49:21 PM Marcus Meissner wrote:
The build system builds with --as-needed by default, your local system probably not.
As the local system is openSUSE out-of-the-box, how it acts is known. Why OBS does not act the same as an oS release in this respect is mysterious. No way in OBS (via web) to get the same behavior as in an openSUSE release? -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 13. März 2014, 11:16:00 wrote Roger Oberholtzer:
On Monday, March 10, 2014 01:49:21 PM Marcus Meissner wrote:
The build system builds with --as-needed by default, your local system probably not.
As the local system is openSUSE out-of-the-box, how it acts is known. Why OBS does not act the same as an oS release in this respect is mysterious.
No way in OBS (via web) to get the same behavior as in an openSUSE release?
OBS itself has nothing to do with that. If you install the same package on your system you get the same behaviour. It is just not installed by default. -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thursday, March 13, 2014 11:19:08 AM Adrian Schröter wrote:
On Donnerstag, 13. März 2014, 11:16:00 wrote Roger Oberholtzer:
On Monday, March 10, 2014 01:49:21 PM Marcus Meissner wrote:
The build system builds with --as-needed by default, your local system probably not.
As the local system is openSUSE out-of-the-box, how it acts is known. Why OBS does not act the same as an oS release in this respect is mysterious.
No way in OBS (via web) to get the same behavior as in an openSUSE release?
OBS itself has nothing to do with that. If you install the same package on your system you get the same behaviour.
It is just not installed by default.
I did miss something. What package would I install in OBS to get ld to act as it does on my openSUSE release? -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Donnerstag, 13. März 2014, 11:28:40 wrote Roger Oberholtzer:
On Thursday, March 13, 2014 11:19:08 AM Adrian Schröter wrote:
On Donnerstag, 13. März 2014, 11:16:00 wrote Roger Oberholtzer:
On Monday, March 10, 2014 01:49:21 PM Marcus Meissner wrote:
The build system builds with --as-needed by default, your local system probably not.
As the local system is openSUSE out-of-the-box, how it acts is known. Why OBS does not act the same as an oS release in this respect is mysterious.
No way in OBS (via web) to get the same behavior as in an openSUSE release?
OBS itself has nothing to do with that. If you install the same package on your system you get the same behaviour.
It is just not installed by default.
I did miss something. What package would I install in OBS to get ld to act as it does on my openSUSE release?
the other way around, when you install post-build-checks on your openSUSE installation, you would build rpms using as-needed by default as well. Of course, you could overwrite also the installation of that package inside of OBS, but it is there for a reason :) -- Adrian Schroeter email: adrian@suse.de SUSE LINUX GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) Maxfeldstraße 5 90409 Nürnberg Germany -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
On Thursday, March 13, 2014 11:35:09 AM Adrian Schröter wrote:
I did miss something. What package would I install in OBS to get ld to act as it does on my openSUSE release?
the other way around, when you install
post-build-checks
on your openSUSE installation, you would build rpms using as-needed by default as well.
OK.
Of course, you could overwrite also the installation of that package inside of OBS, but it is there for a reason :)
The package I am trying to build has an unnecessarily complex configure script. I think they have copied various ones and cobbled together something Satanic. I know I just need to dive in and change this. But I think the libs to link with are not generated in a straight forward manner. -- Yours sincerely, Roger Oberholtzer Ramböll RST / Systems Office: Int +46 10-615 60 20 Mobile: Int +46 70-815 1696 roger.oberholtzer@ramboll.se ________________________________________ Ramböll Sverige AB Krukmakargatan 21 P.O. Box 17009 SE-104 62 Stockholm, Sweden www.rambollrst.se -- To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-buildservice+owner@opensuse.org
participants (5)
-
Adrian Schröter -
Jan Engelhardt -
Marcus Meissner -
Roger Oberholtzer -
Stephan Kulow