This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Build script error (libiconv + custom prefix)


On 8/28/2012 4:02 PM, Tasos Laskos wrote:
On 08/28/2012 10:51 PM, Larry Hall (Cygwin) wrote:
On 8/28/2012 11:23 AM, Tasos Laskos wrote:
Hi,

Thanks for the replies guys.

The purpose of the build.sh script is to setup a full env under the
"arachni" dir which will include all system libs and other dependencies.

It also creates wrappers for the application's executables which setup
env
variables like PATH and LD_LIBRARY_PATH before running them.

The point of all this is that you'll be able to package up that dir and
transfer it between boxes without worrying about dependencies.

It's meant to create a self-contained package, so I don't want to rely on
what's already on the system.

I've attached the libiconv logfile and the cygcheck output.

OK, that explains the difference you and I are seeing. In your configure output, you get:

checking for iconv... (cached) no, consider installing GNU libiconv


So...libiconv's configure script requires libiconv, that's a bit wacky. However, I'm guessing that this is a standard test and doesn't play a part in this problem.

Configuring and installing libiconv manually (no prefix) works, it only
fails when running the build script.

And if you configure manually with a prefix?


If you'd like to recreate my Cygwin env and try again this is how:
-------------
setup.exe -q -R c:\cygwin -l c:\cygwin-packages -P make,gcc,g++,perl,wget
-------------

I already tried your script on a machine with Cygwin installed but without iconv and saw the same complaints from configure in your build script. There are other configure flags for this package which could help if you want to experiment with them (assuming you haven't already). But also doing what the configure script recommends solves the problem. If you're content to do that, then you have a solution. If you're not (as I expect you aren't) and the configure flags don't help, then I'd recommend talking to the package authors about the bump in the configure process you're noticing.

--
Larry

_____________________________________________________________________

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]