Hi,
> E: libclapack3: binary-or-shlib-defines-rpath
> usr/lib/x86_64-linux-gnu/libclapack.so.3.2.1
> /build/clapack-3.2.1+dfsg/obj-x86_64-linux-gnu/BLAS/SRC
>Is there any trick how I could tweak cmake files to prevent the
>inclusion of rpath or is the only chance to solve this to use
>
>
Hi Gert,
On Thu, May 26, 2016 at 04:27:25PM +0200, Gert Wollny wrote:
> ...
> Removing the file INCLUDE/f2c.h solves the problem, because then the
> ...
This tip saved my evening yesterday - thanks a lot. The only remaining
issue is now
E: libclapack3: binary-or-shlib-defines-rpath
Hello Andres,
> Once I have uploaded libf2c2 version 20130926-1 the build somehow
> stopped working again. I can not even reproduce things with a local
> rebuild.I always get something like:
>
> ...
> Start 76: xeigtstd_lse_in
> 76/76 Test #76: xeigtstd_lse_in
Hi Andreas,
>o what I'd like to know: What's the difference between building the
>code copy of libf2c comming with clapack (which can be proved by
>deactivating use_debian_packaged_f2c.patch) and using libf2c2. (Bonus
I would look at both build logs and gcc versions.
maybe some new gcc
Hi Gianfranco,
On Sun, May 22, 2016 at 06:48:36AM +, Gianfranco Costamagna wrote:
> ...
> I would say: remove the add_subdirectory (line 21)
> and then:
> 1) create a "FindF2C.cmake" file and use it as helper
> (that would be the best and upstreamable choice
> you can find some examples in
Sorry for replying to my own mail. I just noticed that the Debian
packaged libf2c really has no symbol i_len_trim. Will check what
version is packaged and how this can be fixed.
On Mon, May 23, 2016 at 12:08:08PM +0200, Andreas Tille wrote:
> Hi Gianfranco,
>
> your very helpful hints helped
http://ftp.kevag-telekom.de/mirrors/gentoo.org/rsync/sci-libs/clapack/files/clapack-3.2.1-noblasf2c.patch
seems that the i_len_trim.c file might be somewhere else, look at gentoo
packaging, they seem to have not
stripped it from the tarball I guess.
Does this helps?
G.
Il Lunedì 23 Maggio
Hi Gianfranco,
your very helpful hints helped me to get some steps forward. However,
its not finally done.
On Sun, May 22, 2016 at 06:48:36AM +, Gianfranco Costamagna wrote:
> >Another question is how I could link against the Debian packaged f2c
> >rather than building the one that comes
Hi,
>after the build issues in clapack[1] were solved and I was even able to
>create shared libraries I wonder how I can properly set a sensible
>SONAME. I tried to do this via SET_TARGET_PROPERTIES but failed.
this is what I did on ettercap
Hi again,
after the build issues in clapack[1] were solved and I was even able to
create shared libraries I wonder how I can properly set a sensible
SONAME. I tried to do this via SET_TARGET_PROPERTIES but failed.
Another question is how I could link against the Debian packaged f2c
rather than
On 05/16/2016 06:25 PM, Andreas Tille wrote:
>
> Would you mind commiting to Git what was building for you?
>
Hi Andreas,
I would love to, but I doubt it's possible. I tried something along the
lines of "ulimit -s unlimited && dh_auto_test" as an
override_dh_auto_test, but depending on the
Hi Danny,
On Mon, May 16, 2016 at 04:30:23PM +0200, Danny Edel wrote:
> Sorry for replying to my own email, but after compiling, the test suite
> crashed on the xeigtstz_* with Segmentation Fault errors.
No need to sorry,
> I debugged this a little bit and the reason was these tests use a lot
On 05/16/2016 01:50 PM, Danny Edel wrote:
> If you change it to "const char* const", the compiler is assured it's
> never going to point to anything else and does not emit the warning.
Sorry for replying to my own email, but after compiling, the test suite
crashed on the xeigtstz_* with
On 05/16/2016 11:07 AM, Andreas Tille wrote:
> /build/clapack-3.2.1/F2CLIBS/libf2c/arithchk.c:125:2: error: format not a
> string literal and no format arguments [-Werror=format-security]
> Cray1 = printf(emptyfmt) < 0 ? 0 : 4617762;
Hi Andreas,
you should have success with changing the type
Am Montag, den 16.05.2016, 10:16 + schrieb Gianfranco Costamagna:
> Hi Gert!
>
> >
> > I think, since in this case the (empty) format string passed to the
> > printf call is not user generated there is no security problem to
> > be exploited.
>
> yes, sure, but disabling this flag has a
* Gert Wollny , 2016-05-16, 12:02:
If Debian doesn't run on such an arch the test could most likely safely
be removed, i.e. remove all code from "ccheck" but the "return 0"
line.
This is what I would recommend. It's safe to assume that printf("")
always works on Debian.
Hi Gert!
>I think, since in this case the (empty) format string passed to the printf
>call is not user generated there is no security problem to be exploited.
yes, sure, but disabling this flag has a nasty side-effect, it is disabled in
the *whole* build, possibly
hiding more serious issues
Hello,
Am Montag, den 16.05.2016, 09:14 + schrieb Gianfranco Costamagna:
> Hi,
>
> > /build/clapack-3.2.1/F2CLIBS/libf2c/arithchk.c:125:2: error: format
> > not a string literal and no format arguments [-Werror=format-
> > security]
> > Cray1 = printf(emptyfmt) < 0 ? 0 : 4617762;
> > ^
>
Mattia Rizzolo:
> On Mon, May 16, 2016 at 11:11:54AM +0200, Sebastiaan Couwenberg wrote:
>> On 05/16/2016 11:07 AM, Andreas Tille wrote:
>>> When reading the code it seems to me that actually a test whether this
>>> code works or not is intended and thus fixing the format is not in the
>>>
On Mon, May 16, 2016 at 11:11:54AM +0200, Sebastiaan Couwenberg wrote:
> On 05/16/2016 11:07 AM, Andreas Tille wrote:
> > When reading the code it seems to me that actually a test whether this
> > code works or not is intended and thus fixing the format is not in the
> > intention of the authors.
Hi,
>/build/clapack-3.2.1/F2CLIBS/libf2c/arithchk.c:125:2: error: format not a
>string literal and no format arguments [-Werror=format-security]
> Cray1 = printf(emptyfmt) < 0 ? 0 : 4617762;
> ^
>cc1: some warnings being treated as errors
I would consider this an RC bug.
security wise the
On 05/16/2016 11:07 AM, Andreas Tille wrote:
> When reading the code it seems to me that actually a test whether this
> code works or not is intended and thus fixing the format is not in the
> intention of the authors. So I tried
>
> export DEB_BUILD_HARDENING_FORMAT:=0
> DPKG_EXPORT_BUILDFLAGS
Hi,
as a precondition for some package for Debian Med I intend to package
clapack[1]. Despite the discussion on Debian Science about the relation
of clapack and lapacke[2] I decided that it is less effort to have
clapack in addition since upstream of phast[3] (my final target) does
not intend to
23 matches
Mail list logo