You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@guacamole.apache.org by vincent lamy <vi...@wanadoo.fr> on 2018/08/13 15:10:24 UTC
Error "make" guacamole "please help me"
Hello all
I try install Guacamole but error "make"
OS : Ubuntu 18.04 server edition (all update)
Please help me !
make all-recursive
make[1]: Entering directory '/home/vincent1890/guacamole-server-0.9.14'
Making all in src/libguac
make[2]: Entering directory '/home/vincent1890/guacamole-server-0.9.14/src/libguac'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/vincent1890/guacamole-server-0.9.14/src/libguac'
Making all in src/common
make[2]: Entering directory '/home/vincent1890/guacamole-server-0.9.14/src/common'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/vincent1890/guacamole-server-0.9.14/src/common'
Making all in tests
make[2]: Entering directory '/home/vincent1890/guacamole-server-0.9.14/tests'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/vincent1890/guacamole-server-0.9.14/tests'
Making all in src/common-ssh
make[2]: Entering directory '/home/vincent1890/guacamole-server-0.9.14/src/common-ssh'
make[2]: Nothing to be done for 'all'.
make[2]: Leaving directory '/home/vincent1890/guacamole-server-0.9.14/src/common-ssh'
Making all in src/terminal
make[2]: Entering directory '/home/vincent1890/guacamole-server-0.9.14/src/terminal'
CC libguac_terminal_la-typescript.lo
typescript.c: In function ‘guac_terminal_typescript_alloc’:
typescript.c:133:46: error: ‘%s’ directive writing 6 bytes into a region of size between 0 and 2047 [-Werror=format-overflow=]
sprintf(typescript->timing_filename, "%s.%s", typescript->data_filename,
^~
In file included from /usr/include/stdio.h:862:0,
from typescript.c:28:
/usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: ‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a destination of size 2048
return __builtin___sprintf_chk (__s, __USE_FORTIFY_LEVEL - 1,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
__bos (__s), __fmt, __va_arg_pack ());
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
Makefile:566: recipe for target 'libguac_terminal_la-typescript.lo' failed
make[2]: *** [libguac_terminal_la-typescript.lo] Error 1
make[2]: Leaving directory '/home/vincent1890/guacamole-server-0.9.14/src/terminal'
Makefile:503: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/vincent1890/guacamole-server-0.9.14'
Makefile:427: recipe for target 'all' failed
make: *** [all] Error 2
Thank you for help !
Cordialement,
---
Vincent1890
Re: Error "make" guacamole "please help me"
Posted by vincent lamy <vi...@wanadoo.fr>.
>Yes, which is why I said it should be in 1.0.0 *when it is released* - 1.0.0 has not been released, yet, but the fix has been committed to the git repo. When 1.0.0 is released you will be able to download it on the web site. You are welcome to check out either the master or staging/1.0.0 branch from the git repo and build from there if you need the fix, now.
>
>-Nick
OK thank you very much I go to see(visit) how it works with him(it) is lying because never used until now and then I stay on wait 16.04 for the version it official 1.x.x on the site.
Thank you
Vincent1890
Re: Error "make" guacamole "please help me"
Posted by brian mullan <bm...@gmail.com>.
Nick
Wanted to let you know that the 2 cmd's to install the patch worked just
great and the v0.9.14 builds correctly without errors now.
Looking forward to guacamole v1.0 !
thanks
brian
On Sat, Sep 1, 2018 at 4:57 PM Nick Couchman <vn...@apache.org> wrote:
>
> On Sat, Sep 1, 2018 at 4:15 PM brian mullan <bm...@gmail.com>
> wrote:
>
>> Nick
>>
>> In that patch... Is there either a missin paren or an extra one ?
>>
>
> I doubt it - I don't know if any compile issues with the current code.
>
>
>>
>> I inserted a nano src/terminal/typeface.c
>> so could insert the changes after the wget & tar -xvf but after saving &
>> continuing it still had a different error which looked like a mismatched
>> paren ?
>>
>>
> You can try just downloading the commit as a patch and applying it that
> way:
>
> # wget
> https://github.com/apache/guacamole-server/commit/cd0e48234a079813664052b56c501e854753303a.patch
> # patch -p1 < cd0e48234a079813664052b56c501e854753303a.patch
>
> -Nick
>
Re: Error "make" guacamole "please help me"
Posted by Nick Couchman <vn...@apache.org>.
On Sat, Sep 1, 2018 at 4:15 PM brian mullan <bm...@gmail.com> wrote:
> Nick
>
> In that patch... Is there either a missin paren or an extra one ?
>
I doubt it - I don't know if any compile issues with the current code.
>
> I inserted a nano src/terminal/typeface.c
> so could insert the changes after the wget & tar -xvf but after saving &
> continuing it still had a different error which looked like a mismatched
> paren ?
>
>
You can try just downloading the commit as a patch and applying it that way:
# wget
https://github.com/apache/guacamole-server/commit/cd0e48234a079813664052b56c501e854753303a.patch
# patch -p1 < cd0e48234a079813664052b56c501e854753303a.patch
-Nick
Re: Error "make" guacamole "please help me"
Posted by brian mullan <bm...@gmail.com>.
Nick
In that patch... Is there either a missin paren or an extra one ?
I inserted a nano src/terminal/typeface.c
so could insert the changes after the wget & tar -xvf but after saving &
continuing it still had a different error which looked like a mismatched
paren ?
Brian
On Sat, Sep 1, 2018, 11:49 AM brian mullan <bm...@gmail.com> wrote:
> Thanks Nick.. I completely understand the "time suck" doing that patch
> into 0.9.14 might be for you folks.
>
> I can wait for v1.0 :-)
> brian
>
>
> On Sat, Sep 1, 2018 at 10:16 AM Nick Couchman <vn...@apache.org> wrote:
>
>> On Sat, Sep 1, 2018 at 9:22 AM bmullan <bm...@gmail.com> wrote:
>>
>>> Nick
>>>
>>> So I read your response and this is fixed in v1.0 master or branch but as
>>> users we don't know when that might become available.
>>>
>>
>> We're nearing completion on 1.0.0. It has a couple of outstanding issues
>> that need to be completed/fixed, and then some documentation to wrap up. I
>> hope it's a matter of weeks, but most of us that contribute to the project
>> have day jobs that don't involve actively contributing to the project, so
>> we can only work so fast. Unfortunately for me it's a hobby, not a career
>> :-).
>>
>> You can check the 1.0.0 version out from the Github mirror repo
>> (staging/1.0.0 branch):
>>
>> https://github.com/apache/guacamole-server
>>
>> if you go this route you'll also need to build the guacamole client code
>> of the same version due to the number of changes made:
>>
>> https://github.com/apache/guacamole-client
>>
>>
>>>
>>> Is there anyway to get this "fix" included into the current 0.9.14
>>> release ?
>>>
>>
>> I'm sure you could patch the 0.9.14 source with this fix - the code for
>> the fix is relatively simple:
>>
>> https://github.com/apache/guacamole-server/pull/150
>>
>> It should be pretty easy to patch the 0.9.14 code. The Guacamole project
>> will not release an official fix for it, though (aside from the 1.0.0
>> version) - we do not go do any official back-ports of patches to
>> already-released code.
>>
>>
>>>
>>> /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note:
>>> ‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a
>>> destination
>>> of size 2048
>>>
>>> There are a lot of 3rd party "build" scripts for Guacamole which I assume
>>> fail now due to this and may be causing new users of Guacamole alot of
>>> frustration trying to install it.
>>>
>>
>> Probably so - there's a reason we don't claim or support those third
>> party scripts. The build process is well-documented within the project,
>> and we fix issues like this within the repository. We definitely do not
>> want the process to be frustrating for people; however, sometimes those
>> third party build scripts only compound the frustration. They're fine when
>> they work, but when they don't you have the added steps of having to debug
>> the build script on top of what might actually be broken in code. The only
>> thing we officially support in that area is the Dockerfile build that is
>> part of the repositories - Docker is the way the project has decided to
>> take to automate Guacamole builds.
>>
>> Beginning with 1.0.0 we have/will take(n) a new approach to versions in
>> Guacamole that should allow us to release patches and minor version
>> increments much more quickly, which will enable us to respond better to
>> scenarios like this. 1.0.0 is nearing completion, and, after that we will
>> probably have another version out relatively quickly as we're already
>> accumulating quite a list of fixed issues in the master version of the
>> repo. Looking beyond 1.0.0 we want to be able to quickly/easily release
>> patch versions (e.g. 1.0.1) and minor versions (1.1.0) more quickly and
>> maintain compatibility across major versions of Guacamole (1.x.x).
>> Hopefully this will mean more than one release per year, which, as a
>> long-time user of open source projects, I fully understand can be
>> frustrating - I've experienced it myself more than once.
>>
>>
>>>
>>> Searching for a solution myself I saw a long thread about this error on a
>>> redhat user forum where they were blaming the failure to build guacamole
>>> on
>>> the gcc compiler version and several other wrong conclusions.
>>>
>>> Same thing with ubuntu users trying to build guacamole for the 1st time
>>> (I
>>> use ubuntu 18.04 but know its not the gcc ver and was aware of your fix
>>> for
>>> v1.0 Guacamole whenever it gets released.
>>>
>>
>> Yeah, and this particular change is a hotly-debated issue among many
>> software developers. The change in GCC has caused many, many issues with
>> various software builds, and a lot of people are not happy about it, but
>> the GNU Compiler folks have stuck to their guns and there are fixes
>> available. Sometimes they just take a while to come out.
>>
>>
>>>
>>> Many of those people may not know to how or want to /"check out either
>>> the
>>> master or staging/1.0.0 branch and build from there" /
>>>
>>
>> I certainly understand this, and we want to get 1.0.0 out as quickly as
>> we can. For the time being, your options are:
>> - Check out the Git repos for 1.0.0 or master and build that way.
>> - Grab the code from the pull request above and patch the 0.9.14 version
>> of the code.
>> - Stick with 0.9.14 and install with a compiler that is known to work.
>> This may mean using Ubuntu 16.04 or CentOS7 or some other combination of
>> known-good platforms. There are several that still work and compile
>> correctly. I use CentOS7, and, while it means I have to compile newer
>> versions of FreeRDP manually because the packages are so old, it's stable
>> and works well long-term. Ubuntu 16.04 is a LTS version, is stable where
>> it is, is known to compile Guacamole correctly, and is still supported and
>> active.
>> - Use the Docker images (available in Docker hub).
>>
>> - Nick
>>
>
Re: Error "make" guacamole "please help me"
Posted by brian mullan <bm...@gmail.com>.
Thanks Nick.. I completely understand the "time suck" doing that patch into
0.9.14 might be for you folks.
I can wait for v1.0 :-)
brian
On Sat, Sep 1, 2018 at 10:16 AM Nick Couchman <vn...@apache.org> wrote:
> On Sat, Sep 1, 2018 at 9:22 AM bmullan <bm...@gmail.com> wrote:
>
>> Nick
>>
>> So I read your response and this is fixed in v1.0 master or branch but as
>> users we don't know when that might become available.
>>
>
> We're nearing completion on 1.0.0. It has a couple of outstanding issues
> that need to be completed/fixed, and then some documentation to wrap up. I
> hope it's a matter of weeks, but most of us that contribute to the project
> have day jobs that don't involve actively contributing to the project, so
> we can only work so fast. Unfortunately for me it's a hobby, not a career
> :-).
>
> You can check the 1.0.0 version out from the Github mirror repo
> (staging/1.0.0 branch):
>
> https://github.com/apache/guacamole-server
>
> if you go this route you'll also need to build the guacamole client code
> of the same version due to the number of changes made:
>
> https://github.com/apache/guacamole-client
>
>
>>
>> Is there anyway to get this "fix" included into the current 0.9.14
>> release ?
>>
>
> I'm sure you could patch the 0.9.14 source with this fix - the code for
> the fix is relatively simple:
>
> https://github.com/apache/guacamole-server/pull/150
>
> It should be pretty easy to patch the 0.9.14 code. The Guacamole project
> will not release an official fix for it, though (aside from the 1.0.0
> version) - we do not go do any official back-ports of patches to
> already-released code.
>
>
>>
>> /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note:
>> ‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a
>> destination
>> of size 2048
>>
>> There are a lot of 3rd party "build" scripts for Guacamole which I assume
>> fail now due to this and may be causing new users of Guacamole alot of
>> frustration trying to install it.
>>
>
> Probably so - there's a reason we don't claim or support those third party
> scripts. The build process is well-documented within the project, and we
> fix issues like this within the repository. We definitely do not want the
> process to be frustrating for people; however, sometimes those third party
> build scripts only compound the frustration. They're fine when they work,
> but when they don't you have the added steps of having to debug the build
> script on top of what might actually be broken in code. The only thing we
> officially support in that area is the Dockerfile build that is part of the
> repositories - Docker is the way the project has decided to take to
> automate Guacamole builds.
>
> Beginning with 1.0.0 we have/will take(n) a new approach to versions in
> Guacamole that should allow us to release patches and minor version
> increments much more quickly, which will enable us to respond better to
> scenarios like this. 1.0.0 is nearing completion, and, after that we will
> probably have another version out relatively quickly as we're already
> accumulating quite a list of fixed issues in the master version of the
> repo. Looking beyond 1.0.0 we want to be able to quickly/easily release
> patch versions (e.g. 1.0.1) and minor versions (1.1.0) more quickly and
> maintain compatibility across major versions of Guacamole (1.x.x).
> Hopefully this will mean more than one release per year, which, as a
> long-time user of open source projects, I fully understand can be
> frustrating - I've experienced it myself more than once.
>
>
>>
>> Searching for a solution myself I saw a long thread about this error on a
>> redhat user forum where they were blaming the failure to build guacamole
>> on
>> the gcc compiler version and several other wrong conclusions.
>>
>> Same thing with ubuntu users trying to build guacamole for the 1st time (I
>> use ubuntu 18.04 but know its not the gcc ver and was aware of your fix
>> for
>> v1.0 Guacamole whenever it gets released.
>>
>
> Yeah, and this particular change is a hotly-debated issue among many
> software developers. The change in GCC has caused many, many issues with
> various software builds, and a lot of people are not happy about it, but
> the GNU Compiler folks have stuck to their guns and there are fixes
> available. Sometimes they just take a while to come out.
>
>
>>
>> Many of those people may not know to how or want to /"check out either the
>> master or staging/1.0.0 branch and build from there" /
>>
>
> I certainly understand this, and we want to get 1.0.0 out as quickly as we
> can. For the time being, your options are:
> - Check out the Git repos for 1.0.0 or master and build that way.
> - Grab the code from the pull request above and patch the 0.9.14 version
> of the code.
> - Stick with 0.9.14 and install with a compiler that is known to work.
> This may mean using Ubuntu 16.04 or CentOS7 or some other combination of
> known-good platforms. There are several that still work and compile
> correctly. I use CentOS7, and, while it means I have to compile newer
> versions of FreeRDP manually because the packages are so old, it's stable
> and works well long-term. Ubuntu 16.04 is a LTS version, is stable where
> it is, is known to compile Guacamole correctly, and is still supported and
> active.
> - Use the Docker images (available in Docker hub).
>
> - Nick
>
Re: Error "make" guacamole "please help me"
Posted by Nick Couchman <vn...@apache.org>.
On Sat, Sep 1, 2018 at 9:22 AM bmullan <bm...@gmail.com> wrote:
> Nick
>
> So I read your response and this is fixed in v1.0 master or branch but as
> users we don't know when that might become available.
>
We're nearing completion on 1.0.0. It has a couple of outstanding issues
that need to be completed/fixed, and then some documentation to wrap up. I
hope it's a matter of weeks, but most of us that contribute to the project
have day jobs that don't involve actively contributing to the project, so
we can only work so fast. Unfortunately for me it's a hobby, not a career
:-).
You can check the 1.0.0 version out from the Github mirror repo
(staging/1.0.0 branch):
https://github.com/apache/guacamole-server
if you go this route you'll also need to build the guacamole client code of
the same version due to the number of changes made:
https://github.com/apache/guacamole-client
>
> Is there anyway to get this "fix" included into the current 0.9.14 release
> ?
>
I'm sure you could patch the 0.9.14 source with this fix - the code for the
fix is relatively simple:
https://github.com/apache/guacamole-server/pull/150
It should be pretty easy to patch the 0.9.14 code. The Guacamole project
will not release an official fix for it, though (aside from the 1.0.0
version) - we do not go do any official back-ports of patches to
already-released code.
>
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note:
> ‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a
> destination
> of size 2048
>
> There are a lot of 3rd party "build" scripts for Guacamole which I assume
> fail now due to this and may be causing new users of Guacamole alot of
> frustration trying to install it.
>
Probably so - there's a reason we don't claim or support those third party
scripts. The build process is well-documented within the project, and we
fix issues like this within the repository. We definitely do not want the
process to be frustrating for people; however, sometimes those third party
build scripts only compound the frustration. They're fine when they work,
but when they don't you have the added steps of having to debug the build
script on top of what might actually be broken in code. The only thing we
officially support in that area is the Dockerfile build that is part of the
repositories - Docker is the way the project has decided to take to
automate Guacamole builds.
Beginning with 1.0.0 we have/will take(n) a new approach to versions in
Guacamole that should allow us to release patches and minor version
increments much more quickly, which will enable us to respond better to
scenarios like this. 1.0.0 is nearing completion, and, after that we will
probably have another version out relatively quickly as we're already
accumulating quite a list of fixed issues in the master version of the
repo. Looking beyond 1.0.0 we want to be able to quickly/easily release
patch versions (e.g. 1.0.1) and minor versions (1.1.0) more quickly and
maintain compatibility across major versions of Guacamole (1.x.x).
Hopefully this will mean more than one release per year, which, as a
long-time user of open source projects, I fully understand can be
frustrating - I've experienced it myself more than once.
>
> Searching for a solution myself I saw a long thread about this error on a
> redhat user forum where they were blaming the failure to build guacamole on
> the gcc compiler version and several other wrong conclusions.
>
> Same thing with ubuntu users trying to build guacamole for the 1st time (I
> use ubuntu 18.04 but know its not the gcc ver and was aware of your fix for
> v1.0 Guacamole whenever it gets released.
>
Yeah, and this particular change is a hotly-debated issue among many
software developers. The change in GCC has caused many, many issues with
various software builds, and a lot of people are not happy about it, but
the GNU Compiler folks have stuck to their guns and there are fixes
available. Sometimes they just take a while to come out.
>
> Many of those people may not know to how or want to /"check out either the
> master or staging/1.0.0 branch and build from there" /
>
I certainly understand this, and we want to get 1.0.0 out as quickly as we
can. For the time being, your options are:
- Check out the Git repos for 1.0.0 or master and build that way.
- Grab the code from the pull request above and patch the 0.9.14 version of
the code.
- Stick with 0.9.14 and install with a compiler that is known to work.
This may mean using Ubuntu 16.04 or CentOS7 or some other combination of
known-good platforms. There are several that still work and compile
correctly. I use CentOS7, and, while it means I have to compile newer
versions of FreeRDP manually because the packages are so old, it's stable
and works well long-term. Ubuntu 16.04 is a LTS version, is stable where
it is, is known to compile Guacamole correctly, and is still supported and
active.
- Use the Docker images (available in Docker hub).
- Nick
Re: Error "make" guacamole "please help me"
Posted by bmullan <bm...@gmail.com>.
Nick
So I read your response and this is fixed in v1.0 master or branch but as
users we don't know when that might become available.
Is there anyway to get this "fix" included into the current 0.9.14 release ?
/usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note:
‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a destination
of size 2048
There are a lot of 3rd party "build" scripts for Guacamole which I assume
fail now due to this and may be causing new users of Guacamole alot of
frustration trying to install it.
Searching for a solution myself I saw a long thread about this error on a
redhat user forum where they were blaming the failure to build guacamole on
the gcc compiler version and several other wrong conclusions.
Same thing with ubuntu users trying to build guacamole for the 1st time (I
use ubuntu 18.04 but know its not the gcc ver and was aware of your fix for
v1.0 Guacamole whenever it gets released.
Many of those people may not know to how or want to /"check out either the
master or staging/1.0.0 branch and build from there" /
Thanks for fixing this tho' and I am looking forward to 1.0 appearing.
Brian
--
Sent from: http://apache-guacamole-general-user-mailing-list.2363388.n4.nabble.com/
Re: Error "make" guacamole "please help me"
Posted by Nick Couchman <vn...@apache.org>.
On Mon, Aug 13, 2018 at 11:28 AM vincent lamy <
vincent.lamy.coueron@wanadoo.fr> wrote:
> Not version 1.0.0 only lasted version 0.9.14 on the site :
> https://guacamole.apache.org/releases/
>
>
>
Yes, which is why I said it should be in 1.0.0 *when it is released* -
1.0.0 has not been released, yet, but the fix has been committed to the git
repo. When 1.0.0 is released you will be able to download it on the web
site. You are welcome to check out either the master or staging/1.0.0
branch from the git repo and build from there if you need the fix, now.
-Nick
Re: Error "make" guacamole "please help me"
Posted by vincent lamy <vi...@wanadoo.fr>.
Not version 1.0.0 only lasted version 0.9.14 on the site : https://guacamole.apache.org/releases/
> Message du 13/08/18 17:24
> De : "vincent lamy"
> A : user@guacamole.apache.org
> Copie à :
> Objet : Re: Error "make" guacamole "please help me"
>
>
> Hello
>
> yes I have already seen this URL but me does not understand has solution final which is you it ?
>
>
> Message du 13/08/18 17:19
> De : "Nick Couchman"
> A : user@guacamole.apache.org, vincent.lamy.coueron@wanadoo.fr
> Copie à :
> Objet : Re: Error "make" guacamole "please help me"
>
>
> > CC libguac_terminal_la-typescript.lo
> > typescript.c: In function ‘guac_terminal_typescript_alloc’:
> > typescript.c:133:46: error: ‘%s’ directive writing 6 bytes into a region of size between 0 and 2047 [-Werror=format-java-script=]
> > sprintf(typescript->timing_filename, "%s.%s", typescript->data_filename,
> > ^~
> > In file included from /usr/include/stdio.h:862:0,
> > from typescript.c:28:
> > /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: ‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a destination of size 2048
>
This should be fixed in 1.0.0 when it is released - see the following JIRA issue:
>
https://issues.apache.org/jira/browse/GUACAMOLE-500
>
>
-Nick
Re: Error "make" guacamole "please help me"
Posted by vincent lamy <vi...@wanadoo.fr>.
Hello
yes I have already seen this URL but me does not understand has solution final which is you it ?
> Message du 13/08/18 17:19
> De : "Nick Couchman"
> A : user@guacamole.apache.org, vincent.lamy.coueron@wanadoo.fr
> Copie à :
> Objet : Re: Error "make" guacamole "please help me"
>
>
> CC libguac_terminal_la-typescript.lo
> typescript.c: In function ‘guac_terminal_typescript_alloc’:
> typescript.c:133:46: error: ‘%s’ directive writing 6 bytes into a region of size between 0 and 2047 [-Werror=format-java-script=]
> sprintf(typescript->timing_filename, "%s.%s", typescript->data_filename,
> ^~
> In file included from /usr/include/stdio.h:862:0,
> from typescript.c:28:
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note: ‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a destination of size 2048
>
This should be fixed in 1.0.0 when it is released - see the following JIRA issue:
>
https://issues.apache.org/jira/browse/GUACAMOLE-500
>
>
-Nick
Re: Error "make" guacamole "please help me"
Posted by Nick Couchman <vn...@apache.org>.
>
> CC libguac_terminal_la-typescript.lo
>
> typescript.c: In function ‘guac_terminal_typescript_alloc’:
>
> typescript.c:133:46: error: ‘%s’ directive writing 6 bytes into a region
> of size between 0 and 2047 [-Werror=format-overflow=]
>
> sprintf(typescript->timing_filename, "%s.%s",
> typescript->data_filename,
>
> ^~
>
> In file included from /usr/include/stdio.h:862:0,
>
> from typescript.c:28:
>
> /usr/include/x86_64-linux-gnu/bits/stdio2.h:33:10: note:
> ‘__builtin___sprintf_chk’ output between 8 and 2055 bytes into a
> destination of size 2048
>
This should be fixed in 1.0.0 when it is released - see the following JIRA
issue:
https://issues.apache.org/jira/browse/GUACAMOLE-500
-Nick