> On Jan 22, 2020, at 11:56, Andreas Tille wrote:
>
> Control: tags -1 help
>
> I have fixed Python2->Python3 migration as well as the FTBFS with
> pbseqlib 5.3.3+dfsg-1 issue in Git[1]. Unfortunately there is another
> build issue in the C++ code which I have no idea how to fix:
>
>
> ...
>
Control: tags -1 help
I have fixed Python2->Python3 migration as well as the FTBFS with
pbseqlib 5.3.3+dfsg-1 issue in Git[1]. Unfortunately there is another
build issue in the C++ code which I have no idea how to fix:
...
g++ -g -O2 -fdebug-prefix-map=/build/pbdagcon-0.3+git20180411.c14c422+ds
Am Montag, den 03.09.2018, 09:18 +0200 schrieb Andreas Tille:
> Hi,
>
> I'm trying to build the latest version of jellyfish which I pushed to
> Salsa[1]. Unfortunately I'm running into
You can just catch by reference
catch(MergeError& e)
This is the better approach anyway:
https://blog.kna
Hi,
I'm trying to build the latest version of jellyfish which I pushed to
Salsa[1]. Unfortunately I'm running into
g++ -DHAVE_CONFIG_H -I. -Wall -Wnon-virtual-dtor -I. -I./include -Wdate-time
-D_FORTIFY_SOURCE=2 -Werror -std=c++11 -g -O2
-fdebug-prefix-map=/build/jellyfish-2.2.10=. -fstac
On Sat, Aug 18, 2018 at 09:18:58AM +0800, Paul Wise wrote:
> On Fri, Aug 17, 2018 at 10:44 PM, Andrey Rahmatullin wrote:
>
> > Looks like the project code was updated for s/HITS_DB/DAZZ_DB/ but the
> > DAZZ_DB submodule snapshot was not updated. Ask the upstream.
>
> This sounds like an embedded
On Fri, Aug 17, 2018 at 10:44 PM, Andrey Rahmatullin wrote:
> Looks like the project code was updated for s/HITS_DB/DAZZ_DB/ but the
> DAZZ_DB submodule snapshot was not updated. Ask the upstream.
This sounds like an embedded code copy, you might want to talk to
upstream to find out and get it re
On Fri, Aug 17, 2018 at 01:16:25PM +0200, Andreas Tille wrote:
> DazAlnProvider.hpp:122:5: error: 'DAZZ_DB' does not name a type
> DAZZ_DB db_;
> ^~~
Looks like the project code was updated for s/HITS_DB/DAZZ_DB/ but the
DAZZ_DB submodule snapshot was not updated. Ask the upstream.
-
Hi,
I've updated pbdagcon[1] to latest upstream commit. Unfortunately the
build fails with:
...
g++ -g -O2 -fdebug-prefix-map=/build/pbdagcon-0.3+git20180411.c14c422+ds=.
-fstack-protector-strong -Wformat -Werror=format-security -O3 -std=c++11 -Wall
-Wuninitialized -pedantic -Wdate-time -D_FO
Hi,
An unsigned integer cannot be negative. Try deleting the violating line
patternset.cpp:188 or even the whole surrounding if statement.
Best,
Fabian
On 09.07.2018 13:11, Andreas Tille wrote:
> patternset.cpp:188:23: error: call of overloaded 'abs(uint32_t&)' is ambiguous
>size = std::abs(
On 09.07.2018 13:11, Andreas Tille wrote:
Hi,
Hello,
[snip]
patternset.cpp:188:23: error: call of overloaded 'abs(uint32_t&)' is ambiguous
size = std::abs(size);
^
There is no abs function which takes uint32_t as parameter, so it does
not know which one it shou
On Mon, Jul 09, 2018 at 01:11:34PM +0200, Andreas Tille wrote:
> patternset.cpp: In member function 'void patternset::CheckParams()':
> patternset.cpp:187:10: warning: comparison of unsigned expression < 0 is
> always false [-Wtype-limits]
> if(size < 0){
> ~^~~
> patternset.cpp:188:23:
Hi,
I take the freedom to ask for some C++ help for the new version of
spaced[1]:
...
g++ -DHAVE_CONFIG_H -I. -I.. -Wall -Wextra -std=c++11 -Wno-char-subscripts
-Wdate-time -D_FORTIFY_SOURCE=2 -fopenmp -g -O2
-fdebug-prefix-map=/build/spaced-1.2.0-201605+dfsg=. -fstack-protector-strong
Hi Juhani,
On Wed, Jan 31, 2018 at 07:35:47PM +0200, Juhani Numminen wrote:
>
> The compilation succeeds if I modify the patch not to define DEV_INFOS:
>
> $ git diff -U0
> diff --git a/debian/patches/dev.patch b/debian/patches/dev.patch
> index 02869a1..415ebda 100644
> --- a/debian/patches/dev
Andreas Tille kirjoitti 31.01.2018 klo 14:49:
> Hi,
>
> I stumbled upon unfinished packaging for packjpg in collab-maint SVN[1].
> I intended to save the current packaging state to Git before SVN will be
> closed down and consiered pkg-phototools a better place than
> collab-maint. So I updated t
Hi,
I stumbled upon unfinished packaging for packjpg in collab-maint SVN[1].
I intended to save the current packaging state to Git before SVN will be
closed down and consiered pkg-phototools a better place than
collab-maint. So I updated the packaging to latest upstream and pushed
the packaging t
Am Montag, den 04.12.2017, 21:53 +0100 schrieb Andreas Tille:
> Hi Gert,
>
> thanks for your hint.
>
> On Mon, Dec 04, 2017 at 07:32:42PM +0100, Gert Wollny wrote:
> >
> > make_pair doesn't require the explicite type specification, i.e.
> > the
> > following should work:
> >
> > - return make_
Hi Gert,
thanks for your hint.
On Mon, Dec 04, 2017 at 07:32:42PM +0100, Gert Wollny wrote:
>
> make_pair doesn't require the explicite type specification, i.e. the
> following should work:
>
> - return make_pair(eigvals, eigvecs);
> + return make_pair(eigvals, eigvecs);
This worked at that v
Am Montag, den 04.12.2017, 17:52 +0100 schrieb Andreas Tille:
> Hi,
>
> I intend to package lamarc[1] and hit the following C++ issue:
>
> ...
> g++ -DHAVE_CONFIG_H -I. -I./config -Wdate-time -D_FORTIFY_SOURCE=2
> -DLAMARC_COMPILE_LINUX -DNDEBUG -Wall -Wextra -Wno-
> unused -I ./co
Hi,
I intend to package lamarc[1] and hit the following C++ issue:
...
g++ -DHAVE_CONFIG_H -I. -I./config -Wdate-time -D_FORTIFY_SOURCE=2
-DLAMARC_COMPILE_LINUX -DNDEBUG -Wall -Wextra -Wno-unused -I
./config -I ./config -I ./src/bayeslike -I ./ src/control -I ./src/conversion
Le 27/11/2017 à 00:39, Alexis Murzeau a écrit :
> Hi,
>
> Le 26/11/2017 à 22:01, Fabian Klötzl a écrit :
>> Ho,
>>
>> On 26.11.2017 19:32, Walter Landry wrote:
>>> Andreas Tille wrote:
Unfortunately I've hit another issue:
...
classifier.h:428:54: error: the value of 'rank' is
Hi,
Le 26/11/2017 à 22:01, Fabian Klötzl a écrit :
> Ho,
>
> On 26.11.2017 19:32, Walter Landry wrote:
>> Andreas Tille wrote:
>>> Unfortunately I've hit another issue:
>>>
>>> ...
>>> classifier.h:428:54: error: the value of 'rank' is not usable in a constant
>>> expression
>>>
Ho,
On 26.11.2017 19:32, Walter Landry wrote:
> Andreas Tille wrote:
>> Unfortunately I've hit another issue:
>>
>> ...
>> classifier.h:428:54: error: the value of 'rank' is not usable in a constant
>> expression
>> while((uint8_t)_hitMap[i].rank < rank) {
>>
Andreas Tille wrote:
> Hi,
>
> On Sat, Nov 25, 2017 at 01:39:03PM -0800, Walter Landry wrote:
>> > In file included from centrifuge_build.cpp:27:0:
>> > bt2_idx.h: In static member function 'static std::pair*,
>> > Ebwt*> Ebwt::fromStrings(const
>> > EList >&, bool, int, int, bool,
>> > in
Hi,
On Sat, Nov 25, 2017 at 01:39:03PM -0800, Walter Landry wrote:
> > In file included from centrifuge_build.cpp:27:0:
> > bt2_idx.h: In static member function 'static std::pair*,
> > Ebwt*> Ebwt::fromStrings(const
> > EList >&, bool, int, int, bool,
> > int32_t, int32_t, int32_t, const st
Andreas Tille wrote:
> Hi,
>
> I started packaging centrifuge[1] and hit a build error which
> is most probably caused by gcc-7 incompatibility:
>
> ...
> In file included from centrifuge_build.cpp:27:0:
> bt2_idx.h: In static member function 'static std::pair*,
> Ebwt*> Ebwt::fromStrings(const
Le 25/11/2017 à 21:56, Andreas Tille a écrit :
> Hi,
>
> I started packaging centrifuge[1] and hit a build error which
> is most probably caused by gcc-7 incompatibility:
>
> ...
> In file included from centrifuge_build.cpp:27:0:
> bt2_idx.h: In static member function 'static std::pair*,
> Ebwt*
Hi,
I started packaging centrifuge[1] and hit a build error which
is most probably caused by gcc-7 incompatibility:
...
In file included from centrifuge_build.cpp:27:0:
bt2_idx.h: In static member function 'static std::pair*,
Ebwt*> Ebwt::fromStrings(const
EList >&, bool, int, int, bool, in
Hi Andreas,
Andreas Tille kirjoitti 21.10.2017 klo 09:22:
Hi Juhani,
thanks a lot for your help.
I'm happy to help you.
On Fri, Oct 20, 2017 at 08:41:35PM +0300, Juhani Numminen wrote:
I think that's the build system sorted, even though the compilation still
fails. Now you probably need t
Hi Juhani,
thanks a lot for your help.
On Fri, Oct 20, 2017 at 08:41:35PM +0300, Juhani Numminen wrote:
>
> I think that's the build system sorted, even though the compilation still
> fails. Now you probably need to add some includes.
I was able to add the said includes but somehow this project
Hi Andreas,
Andreas Tille kirjoitti 20.10.2017 klo 18:41:
Hi Juhani,
On Fri, Oct 20, 2017 at 06:14:02PM +0300, Juhani Numminen wrote:
-TARGET_LINK_LIBRARIES( qtbeads ${QT_LIBRARIES} ...
+TARGET_LINK_LIBRARIES( qtbeads Qt::Widgets ...>> I can't see that
line in the patch at
[1] https://anon
Hi Juhani,
On Fri, Oct 20, 2017 at 06:14:02PM +0300, Juhani Numminen wrote:
> > I think I fixed this by removing the code copy of CImg.h and using the
> > Debian packaged version instead. But the QDebug issue came back and
> > may be I need another trick to tweak src/qtbeads/CMakeLists.txt that
>
Andreas Tille kirjoitti 20.10.2017 klo 15:29:
> Hi again,
>
> On Fri, Oct 20, 2017 at 11:55:22AM +0200, Wout B wrote:
>> It looks like the initial #include was actually correct and
that
>> it indeed doesn't find it somehow. Manually adding Qt5::Core and
>> Qt5::Widgets to target_link_libraries
Hi again,
On Fri, Oct 20, 2017 at 11:55:22AM +0200, Wout B wrote:
> It looks like the initial #include was actually correct and that
> it indeed doesn't find it somehow. Manually adding Qt5::Core and
> Qt5::Widgets to target_link_libraries seems to work though.
I can confirm that this helps - th
On Thu, Oct 5, 2017 at 9:56 PM, Sven Joachim wrote:
> On 2017-10-05 21:00 +0200, Andreas Tille wrote:
>
>> I migrated the Debian packaging of tifffile from SVN to Git[1]. After
>> upgrading to the latest upstream version (dated 2017-09-14) I get:
>>
>> ...
>> x86_64-linux-gnu-gcc -pthread -DNDEBU
On Thu, Oct 05, 2017 at 09:56:39PM +0200, Sven Joachim wrote:
> On 2017-10-05 21:00 +0200, Andreas Tille wrote:
> > It seems that the definition of GET_NEXT_CODE is just wrong - but
> > what would be correct?
>
> Remove the last backslash, or include a blank line after it. This
> prevents the "st
On 2017-10-05 21:00 +0200, Andreas Tille wrote:
> I migrated the Debian packaging of tifffile from SVN to Git[1]. After
> upgrading to the latest upstream version (dated 2017-09-14) I get:
>
> ...
> x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall
> -Wstrict-prototypes -fno-strict-ali
Hi Andreas,
On 10/05/2017 09:00 PM, Andreas Tille wrote:
> It seems that the definition of GET_NEXT_CODE is just wrong - but
> what would be correct?
So the code contains the following:
#define GET_NEXT_CODE \
code = *((uint32_t*)((void*)(encoded + (bitcount >> 3; \
if (little_endian
Hi,
I migrated the Debian packaging of tifffile from SVN to Git[1]. After
upgrading to the latest upstream version (dated 2017-09-14) I get:
...
x86_64-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes
-fno-strict-aliasing -g -O2 -fdebug-prefix-map=/build/tifffile-2017091
Hi Andreas,
On 08/26/2017 10:08 PM, Andreas Tille wrote:
> I moved disulfinder to Git[1] and tried to track down this issue with my
> limited C++ knowledge but failed. The issue is
>
> ...
> make[3]: Entering directory '/build/disulfinder-1.2.11/disulfind/src'
> g++ -Wdate-time -D_FORTIFY_SOURCE
Hi,
On 26/08/17 21:08, Andreas Tille wrote:
> Hi,
>
> I moved disulfinder to Git[1] and tried to track down this issue with my
> limited C++ knowledge but failed. The issue is
>
> ...
> make[3]: Entering directory '/build/disulfinder-1.2.11/disulfind/src'
> g++ -Wdate-time -D_FORTIFY_SOURCE=2 -
Hi,
I moved disulfinder to Git[1] and tried to track down this issue with my
limited C++ knowledge but failed. The issue is
...
make[3]: Entering directory '/build/disulfinder-1.2.11/disulfind/src'
g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O2
-fdebug-prefix-map=/build/disulfinder-1.2.11=. -fstack
Hi,
Andreas Tille wrote:
> there is a remaining issue:
> lk.c: In function 'Update_PMat_At_Given_Edge':
> lk.c:2263:31: error: invalid initializer
>int p_matrices[1] = b_fcus->Pij_rr_idx;
Try
int p_matrices[1] = { b_fcus->Pij_rr_idx };
In lk.c there is
void Update_P
On Sat, Jun 24, 2017 at 04:40:06PM +0200, Andreas Tille wrote:
> However, there is a remaining issue:
You've missed the suggestion for that one.
It basically says "do the same change".
--
WBR, wRAR
signature.asc
Description: PGP signature
Hi Thomas,
On Sat, Jun 24, 2017 at 03:29:56PM +0200, Thomas Schmitt wrote:
> i wrote:
> > https://anonscm.debian.org/cgit/debian-med/phyml.git/tree/src/lk.c
> > has
> > ...
> > double branch_lens[1] = { len };
>
> Duh. That's already how i think it should be.
>
> The git code has in lin
Hi,
i wrote:
> https://anonscm.debian.org/cgit/debian-med/phyml.git/tree/src/lk.c
> has
> ...
> double branch_lens[1] = { len };
Duh. That's already how i think it should be.
The git code has in line 2264
double branch_lens[1] = len;
Have a nice day :)
Thomas
Hi.
Andreas Tille wrote:
> lk.c:2264:31: error: invalid initializer
> double branch_lens[1] = len;
I guess the compiler wants {}-brackets around the scalar value
when it shall initialize a vector.
https://anonscm.debian.org/cgit/debian-med/phyml.git/tree/src/lk.c
has
phydbl len;
Hi,
I'd like to package the latest version of phyml[1]. Unfortunately I get
...
gcc -I. -I.. -Wdate-time -D_FORTIFY_SOURCE=2 -std=c99 -O2
-fomit-frame-pointer -funroll-loops -Wall -Winline -march=native
-I/usr/include/libhmsbeagle-1 -lhmsbeagle -ldl -c -o lk.o lk.c
utilities.c: In function
On Wed, Apr 19, 2017 at 4:20 PM, Andreas Tille wrote:
> Hi Bastien,
>
> On Wed, Apr 19, 2017 at 01:32:43PM +, Bastien Roucaries wrote:
>>
>> Le 19 avril 2017 08:09:11 GMT+02:00, Andreas Tille a
>> écrit :
>> >
>> >Psortb[1] was using header files from biosquid[2] and hmmer2[3] but did
>> >no
Hi Bastien,
On Wed, Apr 19, 2017 at 01:32:43PM +, Bastien Roucaries wrote:
>
> Le 19 avril 2017 08:09:11 GMT+02:00, Andreas Tille a écrit
> :
> >
> >Psortb[1] was using header files from biosquid[2] and hmmer2[3] but did
> >not shipped the according library code. No idea how this might hav
Le 19 avril 2017 08:09:11 GMT+02:00, Andreas Tille a écrit :
>Hi Christian,
>
>On Tue, Apr 18, 2017 at 11:07:03PM +0200, Christian Seiler wrote:
>> >
>> > which is probably due to the fact that I did not changed hmmer2 to
>> > create a shared rather than a static library and lhmmer is not
>comp
Hi Christian,
On Tue, Apr 18, 2017 at 11:07:03PM +0200, Christian Seiler wrote:
> >
> > which is probably due to the fact that I did not changed hmmer2 to
> > create a shared rather than a static library and lhmmer is not compiled
> > with -fPIC. What might be the less stressful way to solve thi
On 04/18/2017 11:01 PM, Andreas Tille wrote:
> x86_64-linux-gnu-gcc -g -O2 -fdebug-prefix-map=/build/psortb-3.0.4+dfsg=.
> -fstack-protector-strong -Wformat -Werror=format-security -Wl,-z,relro
> -shared -L/usr/local/lib -fstack-protector-strong HMM.o hmm-binding.o -o
> ../blib/arch/auto/Algor
Hi Walter,
On Tue, Apr 18, 2017 at 01:26:58PM -0700, Walter Landry wrote:
> > hmm-binding.cpp: In member function ‘void HMM::init(char*, int, int)’:
> > hmm-binding.cpp:245:20: error: ‘CUT_NONE’ was not declared in this scope
> >thresh.autocut = CUT_NONE;
> > ^~~~
> > M
Hi Andreas,
On 04/18/2017 10:15 PM, Andreas Tille wrote:
> The definition of the structure threshold_s can be found in
> /usr/include/hmmer2/structs.h (of package libhmmer2-dev) and
> looks like
>
> struct threshold_s {
> float globT; /* T parameter: keep only hits > globT bits
Andreas Tille wrote:
> hmm-binding.cpp: In member function ‘void HMM::init(char*, int, int)’:
> hmm-binding.cpp:245:20: error: ‘CUT_NONE’ was not declared in this scope
>thresh.autocut = CUT_NONE;
> ^~~~
> Makefile:346: recipe for target 'hmm-binding.o' failed
It is di
Hi,
I intend to package psortb in Debian Med team[1]. To successfully build
this package I needed to re-arrange the package layout of biosquid and
hmmer2 since psortb is using code from those project but only provides
the according header files. This was solved by proper -dev packages -
however,
On 2016-08-14, Andreas Tille wrote:
> Since there was no answer to this question I just did this since it
> seems like a working solution. Unfortunately there are further build
> issues I can't deal with:
>
...
> /build/hyphy-2.2.6+dfsg/src/gui/HYChartWindow.cpp:3010:54: error: no matching
> fu
* Manuel A. Fernandez Montecelo , 2016-08-14, 21:39:
Also, if you substitute e.g. "255*.94" for "255*94/100", make sure that
you use parentheses as in "(255*94)/100", otherwise you can end up with
"255*(94/100) -> 255*0 -> 0" for all such values (I cannot recall the
rules now, but I think that
2016-08-14 20:53 Andreas Tille:
Hi again,
On Sat, Aug 13, 2016 at 09:11:52PM +0200, Andreas Tille wrote:
_HYColorchartColors [HY_CHART_COLOR_COUNT] = {
{255*.94, 255*.12, 255*.11 },//(Red)
{255*.41, 255*.46, 255*.91 },//(Evening Blue)
{255, 255*.91, 255*.34 },//(Bana
Hi again,
On Sat, Aug 13, 2016 at 09:11:52PM +0200, Andreas Tille wrote:
> _HYColorchartColors [HY_CHART_COLOR_COUNT] = {
> {255*.94, 255*.12, 255*.11 },//(Red)
> {255*.41, 255*.46, 255*.91 },//(Evening Blue)
> {255, 255*.91, 255*.34 },//(Banana)
> {255*.18, 255*.55
Thanks for the always useful hints
Andreas.
On Thu, Jun 23, 2016 at 11:46:51AM +0200, Gert Wollny wrote:
> Hello Andreas,
>
> Am Donnerstag, den 23.06.2016, 11:24 +0200 schrieb Andreas Tille:
> > Hi,
> >
> > As I did yesterday successfully (thanks to the help of Gert) I again
> > conside
Hello Andreas,
Am Donnerstag, den 23.06.2016, 11:24 +0200 schrieb Andreas Tille:
> Hi,
>
> As I did yesterday successfully (thanks to the help of Gert) I again
> considered it the easiest way to build the lib by adding configure.ac
> and Makefile.am as quilt patch and use autoconf. This went fi
Hi,
I need to package libfastahack[1] as a pre-pre-dependency for some
Debian Med package. The code comes with a manually crafted Makefile
that simply creates an executable while the pre-depencency of my
package[2] needs a devel package.
As I did yesterday successfully (thanks to the help of Ger
On Wed, Jun 22, 2016 at 03:04:06PM +0200, Gert Wollny wrote:
> > I'll see what I can do to add these things, I expect to push this
> > later today or tomorrow.
>
> Later as in: "I just did it" :)
Muchas gracias.
Thanks for the very quick help
Andreas.
--
http://fam-tille.de
Am Mittwoch, den 22.06.2016, 14:54 +0200 schrieb Gert Wollny:
> I'll see what I can do to add these things, I expect to push this
> later today or tomorrow.
Later as in: "I just did it" :)
Hello Andreas,
Am Mittwoch, den 22.06.2016, 14:22 +0200 schrieb Andreas Tille:
> Hi,
>
> I need to package libsmithwaterman[1] as a pre-pre-dependency for
> some Debian Med package. The code comes with a manually crafted
> Makefile that simply creates an executable while the pre-depencency
> of
On Wed, Jun 22, 2016 at 7:37 PM, Neutron Soutmun wrote:
> Hi,
>
> On Wed, Jun 22, 2016 at 7:22 PM, Andreas Tille wrote:
> [snip]
>> [1] https://anonscm.debian.org/git/debian-med/libsmithwaterman.git
>
> It's broken, did you forget to push this repository ?
A few minutes later, it's valid. Sorry
Hi,
On Wed, Jun 22, 2016 at 7:22 PM, Andreas Tille wrote:
[snip]
> [1] https://anonscm.debian.org/git/debian-med/libsmithwaterman.git
It's broken, did you forget to push this repository ?
Best regards,
Neutron Soutmun
Hi,
I need to package libsmithwaterman[1] as a pre-pre-dependency for some
Debian Med package. The code comes with a manually crafted Makefile
that simply creates an executable while the pre-depencency of my
package[2] needs a devel package (tries to include one of the contained
headers SmithWate
Hi,
> g++ -ggdb -O6 -DNDEBUG -I./protoobj -g -O2 -fstack-protector-strong -Wformat
> -Werror=format-security -o obj-opt-x86_64/test_spectrum_preprocess.o -c
> src/test_spectrum_preprocess.cc
> In file included from src/test_spectrum_preprocess.cc:8:0:
> src/records.h: In destructor 'RecordWriter::
On Wed, Sep 30, 2015 at 08:28:17PM +0200, Andreas Tille wrote:
> Hi,
>
> I have started packaging Tide (a tandard tool for ass-spectroscopy) at
>
>git://anonscm.debian.org/debian-med/tide.git
>
> Unfortunately these days gcc is more picky about C++ syntax and I was
> running into
>
> g++ -g
Hi,
I have started packaging Tide (a tandard tool for ass-spectroscopy) at
git://anonscm.debian.org/debian-med/tide.git
Unfortunately these days gcc is more picky about C++ syntax and I was
running into
g++ -ggdb -O6 -DNDEBUG -I./protoobj -g -O2 -fstack-protector-strong -Wformat
-Werror=for
* Andreas Tille , 2015-07-03, 06:10:
CXX unit_tests/bin_test_all-test_main.o
In file included from ./unit_tests/gtest/gtest.h:308:0,
from unit_tests/test_main.cc:20:
/usr/include/c++/5/sstream:335:7: error: 'struct std::basic_stringbuf<_CharT,
_Traits, _Alloc>::__xfer_bufpt
Hi,
again I have no idea how to fix this issue and need to ask some c++ experts.
Thanks for any help
Andreas.
On Thu, Feb 12, 2015 at 10:32:46AM +, Matthias Klose wrote:
> Package: src:jellyfish
> Version: 2.1.4-1
> Severity: normal
> Tags: sid stretch
> User: debian-...@lists.debian.
Hi,
On Thu, Dec 08, 2011 at 09:53:03AM +0100, Mike Hommey wrote:
> > 219:bposhashstat_t () {
> > 220:}
>
> And line 163 is:
> 163: bposhashstat_t() {};
>
> In other words, you have two definitions of the same (empty) constructor
> in the same class.
Ahh, deleting the second one works
On Thu, Dec 08, 2011 at 09:39:05AM +0100, Andreas Tille wrote:
> Hi,
>
> I try to build a new upstream version of mira but failed and without
> having realy checked it also the current version will fail with latest
> gcc.
>
> The build log says:
>
> g++ -DPACKAGE_NAME=\"mira\" -DPACKAGE_TARNAME=
Hi,
I try to build a new upstream version of mira but failed and without
having realy checked it also the current version will fail with latest
gcc.
The build log says:
g++ -DPACKAGE_NAME=\"mira\" -DPACKAGE_TARNAME=\"mira\"
-DPACKAGE_VERSION=\"3.4.0.1\" -DPACKAGE_STRING=\"mira\ 3.4.0.1\"
-DPAC
Hi Allen!
You wrote:
> I hope i am not trobleing you by askin for your help.
> i was asked to do this, and i have no idea how its
> done, i dont know c++ at all and cant get out of doing
> this, i was wondering if any one can help me.
I think you should do your own homework.
--
Kind regards,
I hope i am not trobleing you by askin for your help.
i was asked to do this, and i have no idea how its
done, i dont know c++ at all and cant get out of doing
this, i was wondering if any one can help me.
1) extracts values from the standard input stream, and
displays the smallest an the largest
I hope i am not trobleing you by askin for your help.
i was asked to do this, and i have no idea how its
done, i dont know c++ at all and cant get out of doing
this, i was wondering if any one can help me.
1) extracts values from the standard input stream, and
displays the smallest an the largest
Hi Allen!
You wrote:
> I hope i am not trobleing you by askin for your help.
> i was asked to do this, and i have no idea how its
> done, i dont know c++ at all and cant get out of doing
> this, i was wondering if any one can help me.
I think you should do your own homework.
--
Kind regards,
On Wed, 29 Sep 1999, Antti-Juhani Kaijanaho wrote:
> Educated guess: s/operator+=/FGString& operator+=/
Ok, thanks for both suggestions, will try at home.
> > PS It seems the package is orphaned upstream, should I also orphan it then?
>
> If you are confident you can work without the help from
Hi,
I think you are requested to give return type of
the function that implements the operator +=
e.g.
void operator+=(const FGString& other);
and no, upstream orphaning is not a requirement
to orphan it in Debian.
t.aa
Christian T. Steigies <[EMAIL PROTECTED]> Wed Sept 29, 1999 12:28 PM
>
On Wed, Sep 29, 1999 at 11:28:19AM +0200, Christian T. Steigies wrote:
> In file included from main.cc:2:
> fgstring.h:34: ANSI C++ forbids declaration `operator +=' with no type
> fgstring.h:35: ANSI C++ forbids declaration `operator +=' with no type
> make: *** [main.o] Error 1
>
> The relevant
Hi,
I was trying to update ftpgrab to standards version 3.0.0.
As we are now also using gcc 2.95 (at least "now" on m68k), I ran into a
problem when building the package:
[EMAIL PROTECTED]:~/package/ftpgrab/ftpgrab-0.1.0>make
g++ -c main.cc
In file included from main.cc:2:
fgstring.h:34: ANSI C++
85 matches
Mail list logo
