You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2010/07/07 18:06:52 UTC

[jira] Created: (TS-399) ./configure not honoring --*dir options properly

./configure not honoring --*dir options properly
------------------------------------------------

                 Key: TS-399
                 URL: https://issues.apache.org/jira/browse/TS-399
             Project: Traffic Server
          Issue Type: Bug
          Components: Build
    Affects Versions: 2.1.1
            Reporter: Leif Hedstrom
             Fix For: 2.1.2


I'm having problems with out generated 'configure', and various --*dir options. For example, this does not produce what I'd expect it to do:

    ./configure  --prefix=/opt/ats --sysconfdir=/opt/ats/conf


I'd expect the above to put my "config" files into /opt/ats/conf, but they end up in /opt/ats/etc/trafficserver instead. I'm pretty sure this is not as intended, because at runtime, the above installation will fail. E.g.

root@loki 528/0 # ./bin/traffic_server
[TrafficServer] using root directory '/opt/ats'
unable to access() management path '/opt/ats/conf': 2, No such file or directory
please set management path via command line '-d <managment directory>'


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

[jira] Closed: (TS-399) ./configure not honoring --*dir options properly

Posted by "Leif Hedstrom (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom closed TS-399.
----------------------------

    Resolution: Fixed

> ./configure not honoring --*dir options properly
> ------------------------------------------------
>
>                 Key: TS-399
>                 URL: https://issues.apache.org/jira/browse/TS-399
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 2.1.1
>            Reporter: Leif Hedstrom
>             Fix For: 2.1.2
>
>         Attachments: ts-399.diff
>
>
> I'm having problems with out generated 'configure', and various --*dir options. For example, this does not produce what I'd expect it to do:
>     ./configure  --prefix=/opt/ats --sysconfdir=/opt/ats/conf
> I'd expect the above to put my "config" files into /opt/ats/conf, but they end up in /opt/ats/etc/trafficserver instead. I'm pretty sure this is not as intended, because at runtime, the above installation will fail. E.g.
> root@loki 528/0 # ./bin/traffic_server
> [TrafficServer] using root directory '/opt/ats'
> unable to access() management path '/opt/ats/conf': 2, No such file or directory
> please set management path via command line '-d <managment directory>'

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

[jira] Updated: (TS-399) ./configure not honoring --*dir options properly

Posted by "Theo Schlossnagle (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/TS-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Theo Schlossnagle updated TS-399:
---------------------------------

    Attachment: ts-399.diff

removes forceful suffixing from pkg$var (no you don't know better than me).

Adds appropriate overrides in parse args to override the pkg$var


> ./configure not honoring --*dir options properly
> ------------------------------------------------
>
>                 Key: TS-399
>                 URL: https://issues.apache.org/jira/browse/TS-399
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 2.1.1
>            Reporter: Leif Hedstrom
>             Fix For: 2.1.2
>
>         Attachments: ts-399.diff
>
>
> I'm having problems with out generated 'configure', and various --*dir options. For example, this does not produce what I'd expect it to do:
>     ./configure  --prefix=/opt/ats --sysconfdir=/opt/ats/conf
> I'd expect the above to put my "config" files into /opt/ats/conf, but they end up in /opt/ats/etc/trafficserver instead. I'm pretty sure this is not as intended, because at runtime, the above installation will fail. E.g.
> root@loki 528/0 # ./bin/traffic_server
> [TrafficServer] using root directory '/opt/ats'
> unable to access() management path '/opt/ats/conf': 2, No such file or directory
> please set management path via command line '-d <managment directory>'

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