Dear Debian Developers!
In the application I am taking part in, I am trying to create a
configuration script to be able to provide two deliverables:
dynamically-linked executable and statically-linked.
The first problem I faced is that it is difficult to explore what should
be the list of librari
On 19.11.2010 22:51, Russ Allbery wrote:
> Dmitry Katsubo writes:
>
>> The first problem I faced is that it is difficult to explore what should
>> be the list of libraries for static linking (as I have to provide the
>> list of libraries which are direct dependencies
Dear developers,
I have the question concerning the following dh_shlibdeps warning, which
is triggered for library that is compiled witn OpenMP support:
>dh_shlibdeps
> dpkg-shlibdeps: warning: symbol GOMP_critical_start used by
> debian/libosra0/usr/lib/libosra.so.0.0.10308 found in none of
On 31.03.2011 18:20, Cyril Brulebois wrote:
> you may want to check through objdump -x $foo.so|grep NEEDED; ldd
> shows recursive dependencies.
>
> KiBi.
KiBi, thanks for the hint. It turned out that libgomp is not listed as
direct dependency of my library. Does it mean I have to put "gcc-4.4"
in
On 31.03.2011 22:16, Jakub Wilk wrote:
>> You do need -lgomp.
>
> You normally don't (need to) link to gomp explicitly. My wild guess is:
> Dmitry used -fopenmp while compiling *.o, but not when linking the
> shared library.
Exactly! Thank you, Jakub, for nice guess.
AC_OPENMP() macro documentati
On 31.03.2011 22:16, Jakub Wilk wrote:
>> You do need -lgomp.
>
> You normally don't (need to) link to gomp explicitly. My wild guess is:
> Dmitry used -fopenmp while compiling *.o, but not when linking the
> shared library.
Exactly! Thank you, Jakub, for nice guess.
AC_OPENMP() macro documentati
Dear Debian developers,
When trying to create a package that includes the library, I am reported
the following error by lintian:
E: libosra1: shlib-with-non-pic-code usr/lib/libosra.so
I understand what the problem is about, but I would like to know which
*functions* in resulting .so are not com
On 24/12/2014 23:25, Mike Hommey wrote:
> Install the elfutils package and use eu-findtextrel, it's sometimes
> wrong, but it should get you started. The manual way to do this is to
> crossreference the output of readelf -r with the symbol table and
> readelf -l.
Thanks, Mike, that helped a lot.
ith an incomplete programming interface instead of a CLI.
>
>
> Best regards,
> Antonio.
>
> -- Forwarded message --
> From: Dmitry Katsubo
> Date: 2015-01-10 15:39 GMT+01:00
> Subject: Re: Bug#774164: libocrad-dev: libocrad.a contains non-reallocatable
>
Dear Debian developers,
Hopefully you can easily help me with my confusion.
I would like to collect / keep core dumps in the system. For that I use
systemd-coredump package which is configured as following:
=== cut /etc/systemd/coredump.conf ===
[Coredump]
Storage=external
MaxUse=5G
=== cut ===
Dear Debian developers,
I wonder if somebody knows what are the plans for packaging kernels
3.18.x and 4.2.x? 3.18 was released long time ago, and I think it is
mature. 4.2.x would be nice to play with. I have searched here:
> https://packages.debian.org/search?suite=all&searchon=names&keywords=k
On 23/10/2015 22:43, James Cowgill wrote:
> Hi,
>
> On Wed, 2015-10-21 at 12:35 +0200, Dmitry Katsubo wrote:
>> Dear Debian developers,
>>
>> I wonder if somebody knows what are the plans for packaging
>> kernels 3.18.x and 4.2.x? 3.18 was released long time ago,
On 24/10/2015 14:56, James Cowgill wrote:
> On Sat, 2015-10-24 at 01:02 +0200, Dmitry Katsubo wrote:
>> On 23/10/2015 22:43, James Cowgill wrote:
>>> If you specifically want 3.18, you can download it from
>>> snapshot.debian.org. http://snapshot.debian.org/package/lin
On 2015-10-25 07:11, Adam Borowski wrote:
> On Sat, Oct 24, 2015 at 10:59:47PM +0100, Simon McVittie wrote:
>> On 24/10/15 22:17, Dmitry Katsubo wrote:
>>> I would be happy to. However it does not allow me to use the latest
>>> kernel from 3.x branch (3.16 is now 1
On 27/10/2015 10:31, Ian Campbell wrote:
>> Hm, kernel.org says that 3.18 is the long-term support kernel.
>
> I'm afraid that LTS from kernel.org != stable support from Debian.
>
> Debian typically picks a single kernel version for a stable release and
> supports it for the lifetime of that rele
15 matches
Mail list logo
