[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Mingw-cross-env-list] libarchive

From: Natalie Tasman
Subject: Re: [Mingw-cross-env-list] libarchive
Date: Thu, 10 Jun 2010 15:15:00 -0700

Hi Tony, thanks for taking a look.

On Thu, Jun 10, 2010 at 1:32 AM, Tony Theodore <address@hidden> wrote:
> On 10 June 2010 04:46, Natalie Tasman <address@hidden> wrote:
> > Volker,
> > Here's a small test program for libarchive.  On a native system (OS X 10.6
> > using macports) it builds without error, while using my current (dev)
> > version of mignw-cross-env I still get errors suggesting the same confusion
> > between static and dynamic declarations ("undefined reference to
> > `__imp__archive_write_new'", etc) with this small test file.
> > build: <gcc> -o libarchive-test.exe libarchive-test.c -I <include path>
> > -L<lib path> -larchive
> Hi Natalie,

> Did you see if you can configure libtpp with --disable-shared?

No change.

> The simplest link test is probably to remove the --disable-bsdtar
> option from libarchive's configure. Then we can look through the log
> to see how it builds bsdtar.exe. The -DLIBARCHIVE_STATIC option to gcc
> seems to do the trick.

OK, check out http://pastebin.com/SZjeZtEi .  Around like 701 you
start seeing bsdtar stuff.  The link line doesn't have anything
interesting, but the compile lines have -DLIBARCHIVE_STATIC, as you
suggest, as well as -D__USE_MINGW_ANSI_STDIO  and -DLIBXML_STATIC.
Not sure if those are relevant too.

> Try compiling the test program with a line like:
> i686-pc-mingw32-gcc -o libarchive-test.exe libarchive-test.c \
> `i686-pc-mingw32-pkg-config libarchive --cflags --libs` \
> and you should get no errors, though this doesn't seem ideal.

Yes!  That works, with no errors.

> Hi Volker,
> Do you think it's reasonable to build bsdtar.exe as a link test then
> write a simple batch file as a runtime test?
> Tony

I don't know if this makes sense right now, as user's won't know to
add all of the special flags to get their own programs to work...
unless this is expected behavior?  I will also forward this to the
libarchive list at this point-- it doesn't seem right that users
should have to #define something in order to be able to correctly link
to a library.

Thanks again!


reply via email to

[Prev in Thread] Current Thread [Next in Thread]