search for: _did

Displaying 8 results from an estimated 8 matches for "_did".

Did you mean: _did_
2009 Oct 21
3
Cross-compiling speex
...vailable 2/ the libogg check is only done when cross-compiling 3/ libogg is assume to exist when cross-compiling Obviously it is the third thing here that gets me. I confess to being completely useless with atuo*, so my 'fix' was simply to change #3, so that configure assumed that libogg _did not_ exist when cross-compiling. This is obviously a crappy solution. I think it would be nice if there was a flag to pass to configure which disabled compiling of the binaries explicitly. Unfortunately I don't grok auto* enough to work out how to do this. Finally, my questions: 1/ Am I doin...
2009 Oct 22
3
Cross-compiling speex
Hi Jean-Marc
2009 Oct 22
1
Cross-compiling speex
...oss-compiling >>>> >>>> Obviously it is the third thing here that gets me. I confess to being >>>> completely useless >>>> with atuo*, so my 'fix' was simply to change #3, so that configure >>>> assumed that libogg >>>> _did not_ exist when cross-compiling. This is obviously a crappy solution. >>>> >>>> I think it would be nice if there was a flag to pass to configure >>>> which disabled compiling >>>> of the binaries explicitly. Unfortunately I don't grok auto* enoug...
2004 Aug 19
4
MASQUERADE problem again...
Dear list members, Masquerading does''not work for me. This is a Mandrake Linux 10 system, but I use another kernel, that included in the original distribution (original: 2.6.3, now used 2.6.8 because of a lot of suck with OpenSwan with kernels prior 2.6.4). The problem seems to be similar or identical mentioned here:
2008 Nov 03
0
No subject
...t; >> 3/ libogg is assume to exist when cross-compiling >> >> Obviously it is the third thing here that gets me. I confess to being >> completely useless >> with atuo*, so my 'fix' was simply to change #3, so that configure >> assumed that libogg >> _did not_ exist when cross-compiling. This is obviously a crappy solutio= n. >> >> I think it would be nice if there was a flag to pass to configure >> which disabled compiling >> of the binaries explicitly. Unfortunately I don't grok auto* enough to >> work out how to...
2009 Oct 21
0
Cross-compiling speex
...ne when cross-compiling > > 3/ libogg is assume to exist when cross-compiling > > Obviously it is the third thing here that gets me. I confess to being > completely useless > with atuo*, so my 'fix' was simply to change #3, so that configure > assumed that libogg > _did not_ exist when cross-compiling. This is obviously a crappy solution. > > I think it would be nice if there was a flag to pass to configure > which disabled compiling > of the binaries explicitly. Unfortunately I don't grok auto* enough to > work out how to > do this. > &...
2009 Oct 22
0
Cross-compiling speex
...assume to exist when cross-compiling >>> >>> Obviously it is the third thing here that gets me. I confess to being >>> completely useless >>> with atuo*, so my 'fix' was simply to change #3, so that configure >>> assumed that libogg >>> _did not_ exist when cross-compiling. This is obviously a crappy solution. >>> >>> I think it would be nice if there was a flag to pass to configure >>> which disabled compiling >>> of the binaries explicitly. Unfortunately I don't grok auto* enough to >>&gt...
2007 May 31
2
installing nut for Mac OS X
i'd like to install nut on Mac OS X 10.4.9; i can't seem to get the Fink install to work (notes below), and i'm only semi-facile at command line installs; is installing nut on Mac OS X as simple as "make install" and no dependencies? if not is there a summary of what i'd need to do? regarding nut on Fink: based on a note in this list's archive i found that nut