Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 578468 - net-misc/curl-7.48.0 creates dylib with undefined symbols
Summary: net-misc/curl-7.48.0 creates dylib with undefined symbols
Status: RESOLVED INVALID
Alias: None
Product: Gentoo/Alt
Classification: Unclassified
Component: Prefix Support (show other bugs)
Hardware: All OS X
: Normal normal (vote)
Assignee: Gentoo Prefix
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-28 15:20 UTC by *
Modified: 2016-04-10 15:44 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
environment (environment.bz2,26.83 KB, application/x-bzip2)
2016-03-28 15:23 UTC, * 		Details
build.log (build.log.bz2,15.75 KB, application/x-bzip2)
2016-03-28 15:24 UTC, * 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description * 2016-03-28 15:20:56 UTC 
My system is OS X El Capitan (10.11.3).
I'm using an installation built with a successful bootstrap from bug 564814.
When I emerge (or re-emerge) net-misc/curl it creates a libcurl.4.4.0.dylib with undefined symbols.

For example, before re-emerge:
$ nm libcurl.4.4.0.dylib | grep DIGEST_MD5
0000000000052130 s _Curl_DIGEST_MD5

After re-emerge:
$ nm libcurl.4.4.0.dylib | grep DIGEST_MD5
0000000000053d90 s _Curl_DIGEST_MD5
                 U _Curl_DIGEST_MD5

I think this is also an issue with curl-7.47.1. When I restore my gentoo installation back to the point of the successful bootstrap above (Feb 13) I have the same issue re-emerging curl-7.47.1.

Reproducible: Always

Steps to Reproduce:
1. quickpkg net-misc/curl
2. emerge --oneshot =net-misc/curl-7.48.0
Comment 1 * 2016-03-28 15:23:51 UTC 
Created attachment 429184 [details]
environment
Comment 2 * 2016-03-28 15:24:20 UTC 
Created attachment 429186 [details]
build.log
Comment 3 Fabian Groffen gentoo-dev 2016-03-31 13:42:32 UTC 
I cannot seem to reproduce this.
Comment 4 * 2016-04-10 15:44:18 UTC 
This was caused by bug 579452. Thanks for trying to reproduce.