{"thread":{"id":"12552","subject":"Problems building git with custom curl installation","startedAt":"2008-03-07T00:39:03Z","lastAt":"2008-03-07T13:40:35Z","messageCount":4,"participants":["Ian Hinder","Stephen Sinclair","Johannes Schindelin","Jakub Narebski"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"71299","messageId":"47D08EA7.8000607@gravity.psu.edu","threadId":"12552","inReplyTo":null,"subject":"Problems building git with custom curl installation","fromName":"Ian Hinder","fromEmail":"hinder@gravity.psu.edu","sentAt":"2008-03-07T00:39:03Z","receivedAt":"2008-03-07T00:39:03Z","isPatch":false,"sender":{"key":"hinder@gravity.psu.edu","avatar":null},"body":"Hi,\n\nI have had some problems building git on a machine which does not have\nthe distro development packages for Curl installed. I have installed it\nfrom source, but there are some issues.\n\n>From a clean download of git-1.5.4, I do:\n\n./configure --prefix=/home/ian/software/git-1.5.4\n--with-curl=/home/ian/software/curl-7.18.0\n\nI get\n\n checking for curl_global_init in -lcurl... no\n\neven though curl has been installed in /home/ian/software/curl-7.18.0\n\nI do \"make\", and get\n\n /bin/sh: curl-config: command not found\n\nbut the make proceeds anyway. When linking, I get warnings\n\n cc: unrecognized option\n'-R/usr/center/atlas1/numrel/software/curl-7.18.0/lib'\nand \"ldd git\" gives\n\n libcurl.so.4 => not found\n\nIf I do\n\n NO_R_TO_GCC_LINKER=yes make\n\nthen things seem to work perfectly, and the rpath to curl is set in\nthe git executable. In the course of debugging this problem, I also\nfound that LDFLAGS were not being passed from the configure command\nline to the makefile.\n\nI suggest that the following are bugs:\n\n1. Configure: Specifying the curl location leads to output that\nindicates that curl was not correctly located, even though a\nsubsequent make finds it successfully and includes it in the build.\n\n2. Make: an error appears indicating that curl-config is not found,\nwhich suggests that curl will not be used successfully, even though it\nworks fine. It must not be looking for curl-config in the right\nplace, and it doesn't even seem to be necessary.\n\n3. The use of the makefile option NO_R_TO_GCC_LINKER is not\nautomatically determined - perhaps an autoconf test could be written\nfor it? All the machines I have tried give an error if you try to\ngive gcc a -R option, and gcc is being used as the linker.\n\n4. LDFLAGS is not passed from the configure command line to the\nmakefile. Modifying config.mak.in to contain the line LDFLAGS =\n@LDFLAGS@ might be the appropriate fix.\n\n-- \nIan Hinder\nhinder@gravity.psu.edu\nhttp://www.gravity.psu.edu/~hinder\n"},{"id":"71301","messageId":"9b3e2dc20803061737l1832fb82g6532808b58a12ab5@mail.gmail.com","threadId":"12552","inReplyTo":"47D08EA7.8000607@gravity.psu.edu","subject":"Re: Problems building git with custom curl installation","fromName":"Stephen Sinclair","fromEmail":"radarsat1@gmail.com","sentAt":"2008-03-07T01:37:15Z","receivedAt":"2008-03-07T01:37:15Z","isPatch":false,"sender":{"key":"radarsat1@gmail.com","avatar":null},"body":"On Thu, Mar 6, 2008 at 7:39 PM, Ian Hinder wrote:\n[snip]\n> 1. Configure: Specifying the curl location leads to output that\n> indicates that curl was not correctly located, even though a\n> subsequent make finds it successfully and includes it in the build.\n\nI'd just like to add that configure also doesn't detect and warn about\na missing gettext package, which became evident to me today when I\ntried compiling it on a newly installed machine. The configure is\nsuccessful, but the build fails.\n\n\nSteve\n"},{"id":"71307","messageId":"alpine.LSU.1.00.0803070317010.19395@racer.site","threadId":"12552","inReplyTo":"9b3e2dc20803061737l1832fb82g6532808b58a12ab5@mail.gmail.com","subject":"Re: Problems building git with custom curl installation","fromName":"Johannes Schindelin","fromEmail":"johannes.schindelin@gmx.de","sentAt":"2008-03-07T02:17:45Z","receivedAt":"2008-03-07T02:17:45Z","isPatch":false,"sender":{"key":"johannes.schindelin@gmx.de","avatar":"https://avatars.githubusercontent.com/u/127790?v=4"},"body":"Hi,\n\nOn Thu, 6 Mar 2008, Stephen Sinclair wrote:\n\n> On Thu, Mar 6, 2008 at 7:39 PM, Ian Hinder wrote:\n> [snip]\n> > 1. Configure: Specifying the curl location leads to output that\n> > indicates that curl was not correctly located, even though a\n> > subsequent make finds it successfully and includes it in the build.\n> \n> I'd just like to add that configure also doesn't detect and warn about\n> a missing gettext package, which became evident to me today when I\n> tried compiling it on a newly installed machine. The configure is\n> successful, but the build fails.\n\nYou probably forgot to include the relevant output.\n\nBut I guess I know it already: msgfmt ist not found. Alas, there are \npatches underway to fix that already.\n\nHth,\nDscho\n\n"},{"id":"71346","messageId":"m3ejamhctv.fsf@localhost.localdomain","threadId":"12552","inReplyTo":"47D08EA7.8000607@gravity.psu.edu","subject":"Re: Problems building git with custom curl installation","fromName":"Jakub Narebski","fromEmail":"jnareb@gmail.com","sentAt":"2008-03-07T13:40:35Z","receivedAt":"2008-03-07T13:40:35Z","isPatch":false,"sender":{"key":"jnareb@gmail.com","avatar":"https://avatars.githubusercontent.com/u/2706?v=4"},"body":"Ian Hinder writes:\n\n> I suggest that the following are bugs:\n\n> 3. The use of the makefile option NO_R_TO_GCC_LINKER is not\n> automatically determined - perhaps an autoconf test could be written\n> for it? All the machines I have tried give an error if you try to\n> give gcc a -R option, and gcc is being used as the linker.\n\nI try to contribute to configure script, but I simply don't know how\nrobustly and in standard way to test if linker (gcc) accepts '-R'\noption. Additionalyy, I don't have system where this is needed (it\nfails), so I don't have a way to test if it works correctly.\n \n> 1. Configure: Specifying the curl location leads to output that\n> indicates that curl was not correctly located, even though a\n> subsequent make finds it successfully and includes it in the build.\n\nI guess that this bug is result of 3.\n\n-- \nJakub Narebski\nPoland\nShadeHawk on #git\n"}]}