Re: 5.30BETA1 cross-compile regression

[Nuno Gonçalves <nunojpg () gmail com>]

The only issue I have now is to cross compile with LUA support.
The other features, like openssl, look to disable checking completely
while cross-compiling, or some times look to the version installed on
the host compiler. With LUA it doesn't find it, even if it is
installed on both the host and the cross-compile target. Probably it
must also be disabled completely...

Best regards,
Nuno

2010/8/18 David Fifield <david () bamsoftware com>:
> On Sat, Aug 07, 2010 at 12:42:26AM +0100, Nuno Gonçalves wrote:
> > 2010/8/4 David Fifield <david () bamsoftware com>:
> > > Please try r19472. I've never seen this error before, but
> > > data_file_record::operator< should be const anyway. I just committed
> > > that and it may fix the problem.
> >
> > It fixs.
> > WIth the patch I just submitted, I can now cross-compile all tools.
> > There are some issues remaining with openssl, liblua and python
> > detection.
> > For example, because I have openssl present on the host computer, I
> > need to explicity disable it "--without-openssl", otherwise it's get
> > linked and then doesn't exist on the final device.
> >
> > --libdir="$(STAGING_DIR)/usr"  --includedir="$(STAGING_DIR)/usr"
> >
> > Shouldn't this be enough to specify where to look for(and just there)?
>
> Yes, but I think the build process of many tools is broken in this
> regard. If you can patch this so it works for you we will probably apply
> it. To make this work, you have to edit the code in configure.ac, then
> run the autoconf command to create configure, and then run configure as
> normal.
>
> David Fifield
_______________________________________________
Sent through the nmap-dev mailing list
http://cgi.insecure.org/mailman/listinfo/nmap-dev
Archived at http://seclists.org/nmap-dev/