You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Felix Buenemann (JIRA)" <ji...@apache.org> on 2016/04/30 08:31:12 UTC

[jira] [Updated] (TS-4397) Build on i386 fails due to lua_Integer type mismatch in traffic_manager metrics

     [ https://issues.apache.org/jira/browse/TS-4397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Felix Buenemann updated TS-4397:
--------------------------------
    Description: 
Currently building master at 4c3fe2aac5e6b45839238b4ae207dff798939e61 fails, because a call to bind_constant in metrics.cc uses int64_t type casting instead of the correct lua_Integer type.

This causes the following compile error on i386:

 {noformat}
metrics.cc: In function ‘bool metrics_binding_initialize(BindingInstance&)’:
metrics.cc:339:58: error: call of overloaded ‘bind_constant(const char [20], int64_t)’ is ambiguous
   binding.bind_constant("metrics.update.pass", int64_t(0));
                                                          ^
metrics.cc:339:58: note: candidates are:
In file included from metrics.cc:29:0:
../../lib/bindings/bindings.h:44:8: note: bool BindingInstance::bind_constant(const char*, lua_Integer)
   bool bind_constant(const char *name, lua_Integer value);
        ^
../../lib/bindings/bindings.h:45:8: note: bool BindingInstance::bind_constant(const char*, const char*)
   bool bind_constant(const char *name, const char *value);
        ^
{noformat}

I have identified the problem and will provide a pull request on GitHub. Update: PR GH-607

  was:
Currently building master at 4c3fe2aac5e6b45839238b4ae207dff798939e61 fails, because a call to bind_constant in metrics.cc uses int64_t type casting instead of the correct lua_Integer type.

This causes the following compile error on i386:

 {noformat}
metrics.cc: In function ‘bool metrics_binding_initialize(BindingInstance&)’:
metrics.cc:339:58: error: call of overloaded ‘bind_constant(const char [20], int64_t)’ is ambiguous
   binding.bind_constant("metrics.update.pass", int64_t(0));
                                                          ^
metrics.cc:339:58: note: candidates are:
In file included from metrics.cc:29:0:
../../lib/bindings/bindings.h:44:8: note: bool BindingInstance::bind_constant(const char*, lua_Integer)
   bool bind_constant(const char *name, lua_Integer value);
        ^
../../lib/bindings/bindings.h:45:8: note: bool BindingInstance::bind_constant(const char*, const char*)
   bool bind_constant(const char *name, const char *value);
        ^
{noformat}

I have identified the problem and will provide a pull request on GitHub.


> Build on i386 fails due to lua_Integer type mismatch in traffic_manager metrics
> -------------------------------------------------------------------------------
>
>                 Key: TS-4397
>                 URL: https://issues.apache.org/jira/browse/TS-4397
>             Project: Traffic Server
>          Issue Type: Bug
>            Reporter: Felix Buenemann
>
> Currently building master at 4c3fe2aac5e6b45839238b4ae207dff798939e61 fails, because a call to bind_constant in metrics.cc uses int64_t type casting instead of the correct lua_Integer type.
> This causes the following compile error on i386:
>  {noformat}
> metrics.cc: In function ‘bool metrics_binding_initialize(BindingInstance&)’:
> metrics.cc:339:58: error: call of overloaded ‘bind_constant(const char [20], int64_t)’ is ambiguous
>    binding.bind_constant("metrics.update.pass", int64_t(0));
>                                                           ^
> metrics.cc:339:58: note: candidates are:
> In file included from metrics.cc:29:0:
> ../../lib/bindings/bindings.h:44:8: note: bool BindingInstance::bind_constant(const char*, lua_Integer)
>    bool bind_constant(const char *name, lua_Integer value);
>         ^
> ../../lib/bindings/bindings.h:45:8: note: bool BindingInstance::bind_constant(const char*, const char*)
>    bool bind_constant(const char *name, const char *value);
>         ^
> {noformat}
> I have identified the problem and will provide a pull request on GitHub. Update: PR GH-607



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)