You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@trafficserver.apache.org by "Andrew Hsu (JIRA)" <ji...@apache.org> on 2009/12/09 19:44:18 UTC

[jira] Commented: (TS-75) dependencies not always working

    [ https://issues.apache.org/jira/browse/TS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12788226#action_12788226 ] 

Andrew Hsu commented on TS-75:
------------------------------

>From IRC chat conversation:

andrewhsu: hmm...i notice that files like AbstractBuffer.cc is specified as a SOURCES for libTrafficServerStandalone and traffic_server.  but ICP.cc is only specified as a SOURCES for traffic_server.  it also looks like .Po files are created for all .cc files upon the first execution of `make`.  it may be that ICP.Po is created but never used by the build system (because it already has traffic_server-ICP.Po).  but for some reason files like AbstractBuffer.Po is created and then used in the final 'Makefile' that is generated.

I believe the fix is to not have the logstat, logcat, etc files LDADD the .o files directly, but instead have a static library shared between the linking of various binaries so the deps link up properly.

For now, workaround is to do `make clean` if you know you are changing a file that is not linked up properly with deps.

I'll take ownership of this jira.

> dependencies not always working
> -------------------------------
>
>                 Key: TS-75
>                 URL: https://issues.apache.org/jira/browse/TS-75
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Build
>            Reporter: John Plevyak
>         Attachments: ts-memcpy-jp-v1.patch
>
>
> When applying a patch, the dependency system did not correctly rebuild Prefetch.o
> as well as some other files for changes to I_IOBuffer.h
> Back out the attached patch and then reapply without doing a 'make clean' to see the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.