[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#610291: marked as done (libgfortran: /usr/bin/ld: cannot find -lgfortran)

Your message dated Tue, 20 Dec 2011 14:29:06 +0100
with message-id <4EF08DA2.20701@debian.org>
and subject line Re: Bug#610291: libgfortran: /usr/bin/ld: cannot find -lgfortran
has caused the Debian Bug report #610291,
regarding libgfortran: /usr/bin/ld: cannot find -lgfortran
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
610291: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=610291
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libgfortran3
Version: 4.4.5-10
Severity: normal
File: libgfortran


Thanks for maintaining libgfortran3.

I use it.

I happened to notice that building some R packages
from their source code elicited an error about
not being able to find gfortran's library.

Here's one way that I found tne bug.

    $ R
    > install.package("amap")
    gfortran   -fpic  -O3 -pipe  -g -c pop.f -o pop.o
    g++ -shared -o amap.so acprob.o burt.o diss.o distance.o distance_T.o hclust.o hclust_T.o kmeans.o pop.o -lpthread -lgfortran -lm -L/usr/lib/R/lib -lR
    /usr/bin/ld: cannot find -lgfortran
    collect2: ld returned 1 exit status
    make: *** [amap.so] Error 1
    ERROR: compilation failed for package 'amap'

The other way was

    > install.package("kernlab")

I fixed them by doing

    $ ln -s /usr/lib/libgfortran.so.3.0.0 /usr/lib/libgfortran.so

If possible, maybe the libgfortran3 package should
create a similar symbolic link.

Thanks,
Kingsley

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash

Versions of packages libgfortran3 depends on:
ii  gcc-4.4-base                  4.4.5-10   The GNU Compiler Collection (base 
ii  libc6                         2.11.2-7   Embedded GNU C Library: Shared lib

libgfortran3 recommends no packages.

libgfortran3 suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
On 01/17/2011 10:44 PM, Kingsley G. Morse Jr. wrote:
> On 01/17/11 13:07, Matthias Klose wrote:
>> On 17.01.2011 08:19, Kingsley G. Morse Jr. wrote:
>>> Package: libgfortran3
>>> Version: 4.4.5-10
>>> Severity: normal
>>> File: libgfortran
>>>
>>>
>>> Thanks for maintaining libgfortran3.
>>>
>>> I use it.
>>>
>>> I happened to notice that building some R packages
>> >from their source code elicited an error about
>>> not being able to find gfortran's library.
>>>
>>> Here's one way that I found tne bug.
>>>
>>>     $ R
>>>     >  install.package("amap")
>>>     gfortran   -fpic  -O3 -pipe  -g -c pop.f -o pop.o
>>>     g++ -shared -o amap.so acprob.o burt.o diss.o distance.o distance_T.o 
>>>     hclust.o hclust_T.o kmeans.o pop.o -lpthread -lgfortran -lm 
>>>     -L/usr/lib/R/lib -lR
>>>     /usr/bin/ld: cannot find -lgfortran
>>>     collect2: ld returned 1 exit status
>>>     make: *** [amap.so] Error 1
>>>     ERROR: compilation failed for package 'amap'
>>>
>>> The other way was
>>>
>>>     >  install.package("kernlab")
>>>
>>> I fixed them by doing
>>>
>>>     $ ln -s /usr/lib/libgfortran.so.3.0.0 /usr/lib/libgfortran.so
>>>
>>> If possible, maybe the libgfortran3 package should
>>> create a similar symbolic link.
>>
>> No, the link is present. which g++ do you use?
>>
>>   which g++
>>   g++ --print-file-name libgfortran.so
> 
> Hi Matthias,
> 
> Thank you for replying quickly.
> 
> I typed the two commands in your email.
> 
> Here's what happened:
> 
>     $ which g++
>     /usr/bin/g++
>     $ ls -l /usr/bin/g++
>     lrwxrwxrwx 1 root root 7 2009-03-22 10:49 /usr/bin/g++ -> g++-4.3
> 
>     $ g++ --print-file-name libgfortran.so
>     /usr/lib/gcc/i486-linux-gnu/4.3.3/../../../../lib/libgfortran.so
> 
> Then I removed the symbolic link for
> /usr/lib/libgfortran.so that fixed my problem, and
> ran g++ again.
> 
>     $ rm /usr/lib/libgfortran.so
>     $ g++ --print-file-name libgfortran.so
>     libgfortran.so
> 
> Does that help?

no. checked on squeeze, that the symlink does exist, in
/usr/lib/gcc/i486-linux-gnu/4.3, as dpkg -L gfortran-4.3 shows.b

the build system does find the library, so I assume a local issue. closing this
report. if you can reproduce it in a fresh installation, or new chroot feel free
to reopen.

--- End Message ---
Reply to: