[
https://issues.apache.org/jira/browse/TS-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13265211#comment-13265211
]
B Wyatt commented on TS-1230:
-----------------------------
I am using debhelper to make some custom packaging. My rules are not complex,
but it does automate calling ./configure with a set of parameters. I am not
certain whether the bug applies to other build management programs, but
debhelper sits on top of make and exhibits the problem from above.
I have a branch staged up and potentially ready to commit that adds a
./configure parameter to override the auto-detected value. This was the least
intrusive method by which I could guarantee that no insanely large value made
it into the .h file and as a result sized a static array in the ~4exabyte range
on my build machine.
> ARG_MAX causing build errors
> ----------------------------
>
> Key: TS-1230
> URL: https://issues.apache.org/jira/browse/TS-1230
> Project: Traffic Server
> Issue Type: Bug
> Components: Build, Packaging
> Environment: Ubuntu 11.4 with 3.0.0 kernel, make 3.81-8ubuntu1,
> libc-bin 2.13-0ubuntu13.1
> Reporter: B Wyatt
> Assignee: Brian Geffon
>
> getconf ARG_MAX is used to size static arrays inside Main.cc and
> LocalManager.cc by way of the configure script. However, getconf ARG_MAX is
> returning inconsistent results based on how it is run. Below is an example
> from the environment above:
> {noformat}
> $ cat Makefile
> all:
> getconf ARG_MAX
> $ make
> getconf ARG_MAX
> 4611686018427387903
> $ getconf ARG_MAX
> 2097152
> {noformat}
> The results is that static arrays based on ARG_MAX in Main.cc and
> LocalManager.cc can vary based on whether the build is done manually or via
> make based packaging scripts. In the case of an outlandish return value,
> this can cause failure at link time.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
