Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 68477 invoked from network); 21 Jan 2010 22:41:38 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 21 Jan 2010 22:41:38 -0000 Received: (qmail 16944 invoked by uid 500); 21 Jan 2010 22:41:37 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 16834 invoked by uid 500); 21 Jan 2010 22:41:37 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Id: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 16826 invoked by uid 99); 21 Jan 2010 22:41:37 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jan 2010 22:41:37 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of philipp_subx@redfish-solutions.com designates 66.232.79.143 as permitted sender) Received: from [66.232.79.143] (HELO mail.redfish-solutions.com) (66.232.79.143) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 21 Jan 2010 22:41:32 +0000 Received: from [192.168.10.7] (builder.redfish-solutions.com [192.168.10.7]) (authenticated bits=0) by mail.redfish-solutions.com (8.14.3/8.14.3) with ESMTP id o0LMelEf014571 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Thu, 21 Jan 2010 15:40:49 -0700 Message-ID: <4B58D7EF.9010000@redfish-solutions.com> Date: Thu, 21 Jan 2010 14:40:47 -0800 From: "Philip A. Prindeville" User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.4pre) Gecko/20091112 Fedora/3.0-2.8.b4.fc11 Thunderbird/3.0b4 MIME-Version: 1.0 To: "NEAL, RYAN" CC: dev@apr.apache.org Subject: Re: Cross compiling the APR suite References: <4B2CB099CF3D4F40B1B1442281CA94FFD99BCA@EXCHANGEVS01.appsig.com> <5944A430-18EE-4051-B16F-E451AA50F40F@apache.org> <4B56E332.7030201@pocock.com.au> <4B2CB099CF3D4F40B1B1442281CA94FFD99C64@EXCHANGEVS01.appsig.com> <4B5802AF.1090005@redfish-solutions.com> <4B2CB099CF3D4F40B1B1442281CA94FFD99CFE@EXCHANGEVS01.appsig.com> In-Reply-To: <4B2CB099CF3D4F40B1B1442281CA94FFD99CFE@EXCHANGEVS01.appsig.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.67 on 192.168.1.3 Do you need -D_GNU_SOURCE in your $CFLAGS? On 01/21/2010 02:38 PM, NEAL, RYAN wrote: > Philip, > > Thanks for the advice. I went into the buildroot and had it compile > iconv. This allowed me to have an iconv that is cross-compiled already. > I tried doing it myself - just another headache... > > What I had to do was NOT provide the --with-iconv flag and add the > LDFLAGS="-L/tmp/buildroot-2009.11/output/target/lib > -L/tmp/buildroot-2009.11/output/target/usr/lib" flag. This is where the > libiconv.so resided. This worked beautifully. And then the compile on > the log4cxx worked as well. > > Still having a problem linking against the pthread library (in the same > spot as the iconv lib) but that is a log4cxx problem. > > I was wondering where the possibilities for PACKAGE were > (--with-PACKAGE)? > > Thanks soooo much! I couldn't have done this without you guys! > > :: Ryan Neal > > > -----Original Message----- > From: Philip A. Prindeville [mailto:philipp_subx@redfish-solutions.com] > Sent: Wednesday, January 20, 2010 11:31 PM > To: dev@apr.apache.org > Subject: Re: Cross compiling the APR suite > > You might need to use: > > -isystem /xyzzy > > for your CFLAGS, where "/xyzzy" is the prefix to your target's include > directory, and: > > --sysroot=/barfoo -L/barfoo/lib > > (or whatever) for your LDFLAGS to find the right libraries. > > > On 01/20/2010 04:30 PM, NEAL, RYAN wrote: >> Hey, >> >> So after some investigation I have found something that I think is a >> problem...I have work around that gets me closer but it isn't there > yet. >> >> When APU is trying to determine iconv "presence" it will write a > little >> program and try and compile it. The file is just to determine if the >> included files are there. What ends up happening when I am cross >> compiling is that iconv.h includes features.h which includes >> gnu/stubs-32.h. When it tries this it is relying on the build > machine's >> install. I am building on a F11 64bit machine. Thus I have a >> stubs-64.h, but no stubs-32.h. I went and got a stubs-32.h from > another >> Red Hat machine, this allows me to get to the point where it tries to >> find the libiconv file (-liconv). This is failing. >> >> I am not sure where I can get a copy of this. Do I not have a iconv >> installed on the machine? I thought it came with the F11 install. >> >> Again thanks for helping! >> >> :: Ryan Neal >> >> >> -----Original Message----- >> From: Daniel Pocock [mailto:daniel@pocock.com.au] >> Sent: Wednesday, January 20, 2010 3:04 AM >> To: Nick Kew >> Cc: NEAL, RYAN; dev@apr.apache.org >> Subject: Re: Cross compiling the APR suite >> >> >> I've attempted cross compiling with the Android NDK and the NDK >> wrappers. >> >> There were a few things I had to tweak, I will publish some details >> shortly. Some of what I did will be necessary for any cross-compile, >> not just Android. >> >> Nick Kew wrote: >> >>> On 20 Jan 2010, at 01:02, NEAL, RYAN wrote: >>> >>> >>> >>>> Hello, >>>> >>>> >>> Your mail would be more legible it you can stop your mailer >>> scrambling it into pseudo-HTML. >>> >>> >>> >>>> ./configure CC=powerpc-linux-gcc --host=powerpc-linux >>>> >> --prefix=/tmp/target_filesystem/apr ac_cv_file__dev_zero=yes >> ac_cv_func_setpgrp_void=yes apr_cv_tcp_nodelay_with_cork=yes >> ac_cv_sizeof_struct_iovec=8 --enable-threads CXX=powerpc-linux-g++ >> >>>> >>>> >>> Is this a cross-compile you're attempting? If not, whence all those >>> >> settings? >> >>> >>> >>>> /tmp/target_filesystem/apr/lib/libapr-1.so: warning: the use of >>>> >> LEGACY `utimes' is discouraged, use `utime' >> >>>> >>>> >>> Could be worth following up ... >>> >>> >>> >>>> /tmp/target_filesystem/apr/lib/libapr-1.so: undefined reference to >>>> >> `pthread_create' >> >>>> >>>> >>> So it's compiled libapr with pthread for the target system but > doesn't >>> >> find it >> >>> on the host system. Maybe it would help if you point your --with-apr >>> to the target apr's apr-1-config? >>> >>> >>> >>>> Any ideas would be REALLY helpful. I am stumped! >>>> >>>> >>> If we knew what you're really trying to do .... >>> >>> Find exactly what failed in config.log. Then try the same thing by >>> >> hand, >> >>> and tweak that until you have it working. You can then work > backwards >>> to the build options and/or patches you may need. >>> >>> >>> >> >