[Blink] logging options on Windows

Morgan Redfield morgar at u.washington.edu
Tue Oct 16 18:24:46 CEST 2012

Ok. I figured out one problem and ran into another. I had WinAVR
installed, which apparently had some unix-like commands that
conflicted with MSYS. I uninstalled WinAVR and now $python setup.py
build_ext --pjsip-clean-compile gets far enough to produce a
config.log file. I'm including the log file with this email in case
that helps.

The new error I'm getting is:
c:\mingw\bin\ar.exe creating ../../lib/libportaudio-i686-pc-mingw32.a
mkdir: cannot create directory
File or path name too long
make[3]: *** [output/libwebrtcaec-i686-pc-mingw32/common_audio/signal_processing_library/main/source]
Error 1
make[2]: *** [libwebrtcaec] Error 2
make[1]: *** [all] Error 1
make: *** [all] Error 1

Any advice about that?


On Tue, Oct 16, 2012 at 8:31 AM, Morgan Redfield
<morgar at u.washington.edu> wrote:
> I can't find conf.log. Would that be in the
> build\temp.win32-2.6\Release\pjsip directory? Is it possible that
> autoconf isn't completing correctly?
> Thanks,
> Morgan
> On Tue, Oct 16, 2012 at 1:07 AM, Saúl Ibarra Corretgé
> <saul at ag-projects.com> wrote:
>> On Oct 16, 2012, at 7:16 AM, Morgan Redfield wrote:
>>> Thanks. I've been working on installing the dependencies, but I'm
>>> having trouble with sip simple. I've been following the instructions
>>> for that here: http://download.ag-projects.com/SipClient/Windows/Install.windows
>>> I get this error message:
>>> bash.exe"-3.1$python setup.py build_ext --pjsip-clean-compile
>>> running build_ext
>>> Cleaning PJSIP
>>> Unpacking PJSIP
>>> Patching PJSIP
>>> Patching PortAudio
>>> Configuring PJSIP
>>> error: build\temp.win32-2.6\Release\pjsip\pjsip\include\pjsip\sip_autoconf.h:
>>> No such file or directory
>>> It looks like that sip_autoconf.h file should be created when PJSIP is
>>> configured, but all that is created is sip_autoconf.h.in. Any idea
>>> what's going wrong here?
>> Hum, I have never seen this myself, that file should indeed be there :-S
>> Maybe you can find some clues in config.log, it's automatically generated with the results of the tests autoconf does.
>> Regards,
>> --
>> Saúl Ibarra Corretgé
>> AG Projects
>> _______________________________________________
>> Blink mailing list
>> Blink at lists.ag-projects.com
>> http://lists.ag-projects.com/mailman/listinfo/blink
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: application/octet-stream
Size: 123995 bytes
Desc: not available
URL: <http://lists.ag-projects.com/pipermail/blink/attachments/20121016/118a5c4f/attachment.obj>

More information about the Blink mailing list