You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bruce Snyder (JIRA)" <ji...@apache.org> on 2008/06/16 23:56:00 UTC
[jira] Created: (AMQCPP-183) Add a note about using LIBTOOLIZE
environment variable when building on MacOS X
Add a note about using LIBTOOLIZE environment variable when building on MacOS X
-------------------------------------------------------------------------------
Key: AMQCPP-183
URL: https://issues.apache.org/activemq/browse/AMQCPP-183
Project: ActiveMQ C++ Client
Issue Type: Improvement
Environment: ProductName: Mac OS X
ProductVersion: 10.5.2
BuildVersion: 9C2028
Reporter: Bruce Snyder
Assignee: Nathan Mittler
When building the ActiveMQ CPP client on MacOS X 10.5, I continually received the following error even though I had all the right tools and versions installed:
{panel}
$ ./autogen.sh
Can't exec "libtoolize": No such file or directory at /opt/local/share/autoconf/Autom4te/FileUtils.pm line 290, <GEN2> line 5.
autoreconf: failed to run libtoolize: No such file or directory
{panel}
I was able to work around this by using the LIBTOOLIZE environment variable to point to /usr/bin/glibtoolize. After doing this the build completed successfully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQCPP-183) Add a note about using LIBTOOLIZE
environment variable when building on MacOS X
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQCPP-183.
---------------------------------
Resolution: Fixed
Resolved in trunk
> Add a note about using LIBTOOLIZE environment variable when building on MacOS X
> -------------------------------------------------------------------------------
>
> Key: AMQCPP-183
> URL: https://issues.apache.org/activemq/browse/AMQCPP-183
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Affects Versions: 2.2
> Environment: ProductName: Mac OS X
> ProductVersion: 10.5.2
> BuildVersion: 9C2028
> Reporter: Bruce Snyder
> Assignee: Timothy Bish
> Fix For: 2.3
>
> Attachments: AMQCPP-183.diff.txt
>
>
> When building the ActiveMQ CPP client on MacOS X 10.5, I continually received the following error even though I had all the right tools and versions installed:
> {panel}
> $ ./autogen.sh
> Can't exec "libtoolize": No such file or directory at /opt/local/share/autoconf/Autom4te/FileUtils.pm line 290, <GEN2> line 5.
> autoreconf: failed to run libtoolize: No such file or directory
> {panel}
> I was able to work around this by using the LIBTOOLIZE environment variable to point to /usr/bin/glibtoolize. After doing this the build completed successfully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQCPP-183) Add a note about using LIBTOOLIZE
environment variable when building on MacOS X
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish updated AMQCPP-183:
--------------------------------
Assignee: Timothy Bish (was: Nathan Mittler)
Fix Version/s: 2.3
Affects Version/s: 2.2
> Add a note about using LIBTOOLIZE environment variable when building on MacOS X
> -------------------------------------------------------------------------------
>
> Key: AMQCPP-183
> URL: https://issues.apache.org/activemq/browse/AMQCPP-183
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Affects Versions: 2.2
> Environment: ProductName: Mac OS X
> ProductVersion: 10.5.2
> BuildVersion: 9C2028
> Reporter: Bruce Snyder
> Assignee: Timothy Bish
> Fix For: 2.3
>
> Attachments: AMQCPP-183.diff.txt
>
>
> When building the ActiveMQ CPP client on MacOS X 10.5, I continually received the following error even though I had all the right tools and versions installed:
> {panel}
> $ ./autogen.sh
> Can't exec "libtoolize": No such file or directory at /opt/local/share/autoconf/Autom4te/FileUtils.pm line 290, <GEN2> line 5.
> autoreconf: failed to run libtoolize: No such file or directory
> {panel}
> I was able to work around this by using the LIBTOOLIZE environment variable to point to /usr/bin/glibtoolize. After doing this the build completed successfully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQCPP-183) Add a note about using LIBTOOLIZE
environment variable when building on MacOS X
Posted by "Bruce Snyder (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bruce Snyder updated AMQCPP-183:
--------------------------------
Attachment: AMQCPP-183.diff.txt
Attaching a patch to add a note for MacOS X users to use the LIBTOOLIZE environment variable.
> Add a note about using LIBTOOLIZE environment variable when building on MacOS X
> -------------------------------------------------------------------------------
>
> Key: AMQCPP-183
> URL: https://issues.apache.org/activemq/browse/AMQCPP-183
> Project: ActiveMQ C++ Client
> Issue Type: Improvement
> Environment: ProductName: Mac OS X
> ProductVersion: 10.5.2
> BuildVersion: 9C2028
> Reporter: Bruce Snyder
> Assignee: Nathan Mittler
> Attachments: AMQCPP-183.diff.txt
>
>
> When building the ActiveMQ CPP client on MacOS X 10.5, I continually received the following error even though I had all the right tools and versions installed:
> {panel}
> $ ./autogen.sh
> Can't exec "libtoolize": No such file or directory at /opt/local/share/autoconf/Autom4te/FileUtils.pm line 290, <GEN2> line 5.
> autoreconf: failed to run libtoolize: No such file or directory
> {panel}
> I was able to work around this by using the LIBTOOLIZE environment variable to point to /usr/bin/glibtoolize. After doing this the build completed successfully.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.