digitalmars.D.learn - Problem this names of shared libraries
- mezozoysky (20/20) Jun 26 2012 Hello!
- mezozoysky (1/1) Jun 26 2012 Oh... sorry for typos.
- Jacob Carlborg (4/21) Jun 26 2012 As far as I know -L is just piped through to the linker.
- mezozoysky (3/36) Jul 03 2012 Yes, I know it. Does it means that I have problem with ld instead
- Tobias Pankrath (2/41) Jul 03 2012 You could try to build with -c and link by hand to check this.
- Johannes Pfau (5/19) Jul 04 2012 It seems linux distributions lately put these symlinks into
- mezozoysky (1/1) Jul 08 2012 Thank You, Tobias & Johannes. I'll check it.
Hello! I'm not sure if this is the right thread for this question. If you know in which thread this question should be, please point me to it. I've see a strange things using dmd 2.059 with my debian/testing os. Linker returns an error, when I link external shared libraries to my code. I ran the following: $ dmd -ofbin/example ./src/example/main.o -L-lGL -L-lGLU -L-ldl & I've got: /usr/bin/ld: cannot find -lGL /usr/bin/ld: cannot find -lGLU collect2: ld returned 1 exit status --- errorlevel 1 this occurs until I have libGL.so.1 & libGLU.so.1 in /usr/lib, but since I've created symlinks libGL.so & libGLU.so in the same directory, it links ok. What is this: dmd bug? OS or ld misconfiguration? something else? Please tell me if I'm doing something wrong.
Jun 26 2012
On 2012-06-26 10:45, mezozoysky wrote:Hello! I'm not sure if this is the right thread for this question. If you know in which thread this question should be, please point me to it. I've see a strange things using dmd 2.059 with my debian/testing os. Linker returns an error, when I link external shared libraries to my code. I ran the following: $ dmd -ofbin/example ./src/example/main.o -L-lGL -L-lGLU -L-ldl & I've got: /usr/bin/ld: cannot find -lGL /usr/bin/ld: cannot find -lGLU collect2: ld returned 1 exit status --- errorlevel 1 this occurs until I have libGL.so.1 & libGLU.so.1 in /usr/lib, but since I've created symlinks libGL.so & libGLU.so in the same directory, it links ok. What is this: dmd bug? OS or ld misconfiguration? something else? Please tell me if I'm doing something wrong.As far as I know -L is just piped through to the linker. -- /Jacob Carlborg
Jun 26 2012
On Tuesday, 26 June 2012 at 10:23:32 UTC, Jacob Carlborg wrote:On 2012-06-26 10:45, mezozoysky wrote:Yes, I know it. Does it means that I have problem with ld instead of dmd piping?Hello! I'm not sure if this is the right thread for this question. If you know in which thread this question should be, please point me to it. I've see a strange things using dmd 2.059 with my debian/testing os. Linker returns an error, when I link external shared libraries to my code. I ran the following: $ dmd -ofbin/example ./src/example/main.o -L-lGL -L-lGLU -L-ldl & I've got: /usr/bin/ld: cannot find -lGL /usr/bin/ld: cannot find -lGLU collect2: ld returned 1 exit status --- errorlevel 1 this occurs until I have libGL.so.1 & libGLU.so.1 in /usr/lib, but since I've created symlinks libGL.so & libGLU.so in the same directory, it links ok. What is this: dmd bug? OS or ld misconfiguration? something else? Please tell me if I'm doing something wrong.As far as I know -L is just piped through to the linker.
Jul 03 2012
On Wednesday, 4 July 2012 at 05:15:20 UTC, mezozoysky wrote:On Tuesday, 26 June 2012 at 10:23:32 UTC, Jacob Carlborg wrote:You could try to build with -c and link by hand to check this.On 2012-06-26 10:45, mezozoysky wrote:Yes, I know it. Does it means that I have problem with ld instead of dmd piping?Hello! I'm not sure if this is the right thread for this question. If you know in which thread this question should be, please point me to it. I've see a strange things using dmd 2.059 with my debian/testing os. Linker returns an error, when I link external shared libraries to my code. I ran the following: $ dmd -ofbin/example ./src/example/main.o -L-lGL -L-lGLU -L-ldl & I've got: /usr/bin/ld: cannot find -lGL /usr/bin/ld: cannot find -lGLU collect2: ld returned 1 exit status --- errorlevel 1 this occurs until I have libGL.so.1 & libGLU.so.1 in /usr/lib, but since I've created symlinks libGL.so & libGLU.so in the same directory, it links ok. What is this: dmd bug? OS or ld misconfiguration? something else? Please tell me if I'm doing something wrong.As far as I know -L is just piped through to the linker.
Jul 03 2012
Am Wed, 04 Jul 2012 07:15:18 +0200 schrieb "mezozoysky" <neferegio gmail.com>:On Tuesday, 26 June 2012 at 10:23:32 UTC, Jacob Carlborg wrote:It seems linux distributions lately put these symlinks into their *-dev packages (the packages also containing the c headers). You could try to install libglu1-mesa-dev and libgl-mesa-devOn 2012-06-26 10:45, mezozoysky wrote:Yes, I know it. Does it means that I have problem with ld instead of dmd piping?What is this: dmd bug? OS or ld misconfiguration? something else? Please tell me if I'm doing something wrong.As far as I know -L is just piped through to the linker.
Jul 04 2012