> Maybe you could work out a patch for your use case using @elextr's
> suggestions about `std::move()`, if you're C++ proficient enough to
> understand the implications (I don't, it's not C )
neither me :< snif... i will try with a frined.. thanks for all guys
--
You are receiving this
Maybe you could work out a patch for your use case using @elextr's suggestions
about `std::move()`, if you're C++ proficient enough to understand the
implications (I don't, it's not C :grin: )
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
> paging @codebrainz search services
https://groups.google.com/g/scintilla-interest/c/ma_3cmKAEVs/m/n61l9uT4BQAJ
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #2731.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geany/geany/issues/2731#event-4230823664
ummno w correctly copy cat adn understand.. puff so i cant backport geany 1.33
to olders versions of my production environment devbelopers.. puff i already
noted you guys were using the LongTerm3 brand for a while .. so i cant make
anything .. so i will try to backport the 1.26 version or
The errors posted in the OP (assuming Scintilla 3.7.5 or earlier, the line is
blank in later versions) do indeed look like a known bug in early C++11
compilers that didn't detect the return value was an rvalue and required
`std::move` on them. Of course then once that was fixed, later
> But if we accidentally started to depend on C++14, we probably should write
> this down
Not knowingly, Longterm3 branch claims "avoiding C++14" but Mitchell could have
made a mistake, but since he has retired the branch its not going to be fixed
if something did sneak in.
@b4n to explain,
> it seems related to this commit
> [170ebf6](https://github.com/geany/geany/commit/170ebf610f33ac414799f1a841ae01c1e058d567)
> so i'll try to investigate a little but seems i'll need more help
I hardly think this commits has anything to do with your problems, and I don't
see any reference to
> And a rant of my own if I may, I am tired of people demanding that others
> invest the effort to support their particular configuration with no
> contribution of their own. Even to find the cause and possible workarounds
> takes effort that somebody has to provide. As I said above, even
> > i'm asking about any trick or workaround puff
>
> * Build a new enough GCC for yourself
> * Adjust Scintilla's sources not to require features not in GCC 4.8
> * If it's that simple, figure out a set of GCC 4.8 options that make it work
> (I'm afraid there won't be any)
> * Convince
it seems is related to this commit: 170ebf610f33ac414799f1a841ae01c1e058d567 in
fact the error is produced in that line and inherits
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
> Build a new enough GCC for yourself
Its probably not even necessary to do that, for example Ubuntu 16.04 (which has
4.8 as the default compiler) has 4.9 and 5.4 in the repos ready to install.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
> i'm asking about any trick or workaround puff
* Build a new enough GCC for yourself
* Adjust Scintilla's sources not to require features not in GCC 4.8
* If it's that simple, figure out a set of GCC 4.8 options that make it work
(I'm afraid there won't be any)
* Convince Scintilla's authors
Yes the compiler requirement is driven by Scintilla, but thats a separate
project and can make its own decisions, and Geany is only one of the users of
that software. Whilst a branch compatible with C++11 has been maintained until
recently, because the requirement for C++17 the day the
> [Edit: assuming you are compiling Geany 1.37 a fully working C++11 compiler
> is needed, and as shown GCC 4.8 isn't that, 1.38 will probably need a c++17
> compiler which I think is at least GCC 7]
umm ok so @elextr geany 1.30+ will need moderns compilers .. pufff please is
there any
IIRC GCC 4.8 is too old, at least GCC 5.4 is needed, and probably GCC 7? for
next version. A distro with 4.8 as the default compiler will usually have at
least up to 5.4 available in the repos.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly
i have following error when try to compile geany, using gcc 4.8 cos ist
upstream provided.. is any workaround to prioperty compile of can i disable
that part?
```
[ 181s] Making all in scintilla
[ 181s] make[3]: Entering directory `/usr/src/packages/BUILD/scintilla'
[ 181s] Making all in
17 matches
Mail list logo
