You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@thrift.apache.org by "Eric Evans (JIRA)" <ji...@apache.org> on 2009/05/05 18:36:31 UTC
[jira] Created: (THRIFT-483) have libtool files copied instead of
linked
have libtool files copied instead of linked
-------------------------------------------
Key: THRIFT-483
URL: https://issues.apache.org/jira/browse/THRIFT-483
Project: Thrift
Issue Type: Bug
Reporter: Eric Evans
Attachments: libtoolize-copy-not-link.txt
It should be possible to distribute a more self-contained tarball of the thrift source, one which had already had bootstrap.sh run on it, and all required build files are present. The attached trivial patch causes libtoolize to create copies of files, instead of symlinks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (THRIFT-483) have libtool files copied instead of
linked
Posted by "David Reiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-483?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12706131#action_12706131 ]
David Reiss commented on THRIFT-483:
------------------------------------
The instant releases <http://instant.thrift-rpc.org/> already have bootstrap.sh run, and it looks like "make dist" automatically dereferences symlinks.
I can still apply a slightly modified version of it.
> have libtool files copied instead of linked
> -------------------------------------------
>
> Key: THRIFT-483
> URL: https://issues.apache.org/jira/browse/THRIFT-483
> Project: Thrift
> Issue Type: Bug
> Reporter: Eric Evans
> Attachments: libtoolize-copy-not-link.txt
>
>
> It should be possible to distribute a more self-contained tarball of the thrift source, one which had already had bootstrap.sh run on it, and all required build files are present. The attached trivial patch causes libtoolize to create copies of files, instead of symlinks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (THRIFT-483) have libtool files copied instead of
linked
Posted by "Eric Evans (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Evans updated THRIFT-483:
------------------------------
Attachment: libtoolize-copy-not-link.txt
> have libtool files copied instead of linked
> -------------------------------------------
>
> Key: THRIFT-483
> URL: https://issues.apache.org/jira/browse/THRIFT-483
> Project: Thrift
> Issue Type: Bug
> Reporter: Eric Evans
> Attachments: libtoolize-copy-not-link.txt
>
>
> It should be possible to distribute a more self-contained tarball of the thrift source, one which had already had bootstrap.sh run on it, and all required build files are present. The attached trivial patch causes libtoolize to create copies of files, instead of symlinks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (THRIFT-483) have libtool files copied instead of
linked
Posted by "David Reiss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/THRIFT-483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Reiss resolved THRIFT-483.
--------------------------------
Resolution: Fixed
Fix Version/s: 0.2
> have libtool files copied instead of linked
> -------------------------------------------
>
> Key: THRIFT-483
> URL: https://issues.apache.org/jira/browse/THRIFT-483
> Project: Thrift
> Issue Type: Bug
> Reporter: Eric Evans
> Fix For: 0.2
>
> Attachments: libtoolize-copy-not-link.txt
>
>
> It should be possible to distribute a more self-contained tarball of the thrift source, one which had already had bootstrap.sh run on it, and all required build files are present. The attached trivial patch causes libtoolize to create copies of files, instead of symlinks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.