> I'll add a README to libf2c package. Providing dummy packages
> depending on the compiler is difficult. Which compiler should we
> depend on? Making libg2c0-3.2 and libg2c0-3.3 packages looks ugly.
Mm, yes compiler transitions are ugly aren't they.
I think you've found the right solution, I didn'
I'll add a README to libf2c package. Providing dummy packages
depending on the compiler is difficult. Which compiler should we
depend on? Making libg2c0-3.2 and libg2c0-3.3 packages looks ugly.
The same issue arises with the ObjC compiler.
Hello Matthias,
thanks for your rapid response.
> Install g77-3.2, which contains this symlink.
we installed this by chance. However I made the symlink as well,
before actually trying the to build again. So it seemed to me that
adding the symlink to /usr/lib fixed things.
I didn't try building af
Vincent McIntyre writes:
> Package: libg2c0
> Version: 1:3.2.3-0pre5
> Severity: normal
>
> Hi,
> we are trying to build a large software suite with gcc-3.2.
> The linker cannot link in libg2c when we give just -llibg2c.
> This is resolved by placing a symlink:
> cd /usr/lib; ln -s libg2c.so.0 l
Package: libg2c0
Version: 1:3.2.3-0pre5
Severity: normal
Hi,
we are trying to build a large software suite with gcc-3.2.
The linker cannot link in libg2c when we give just -llibg2c.
This is resolved by placing a symlink:
cd /usr/lib; ln -s libg2c.so.0 libg2c.so
It's unclear to me if this is a p
5 matches
Mail list logo
