Hi Folks
I started a new attempt at buildtool, still no luck. Here is the log...
buildtool::Download::download:file key: buildtool.cfg
Warning: wildcards not supported in HTTP.
--09:12:19--
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/leaf/src/bering-uclibc/apps/linux/buildtool.cfg?rev=HEAD&content-type=application/octet-stream
=>
`/data/leaf/bering-uclibc/src/bering-uclibc/buildtool/source/linux/buildtool.cfg'
Resolving cvs.sourceforge.net... done.
Connecting to cvs.sourceforge.net[66.35.250.207]:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://cvs.sourceforge.net/viewcvs.py/*checkout*/leaf/src/bering-uclibc/apps/linux/buildtool.cfg?rev=HEAD&content-type=application/octet-stream
[following]
Warning: wildcards not supported in HTTP.
--09:12:19--
http://cvs.sourceforge.net/viewcvs.py/*checkout*/leaf/src/bering-uclibc/apps/linux/buildtool.cfg?rev=HEAD&content-type=application/octet-stream
=>
`/data/leaf/bering-uclibc/src/bering-uclibc/buildtool/source/linux/buildtool.cfg'
Connecting to cvs.sourceforge.net[66.35.250.207]:80... connected.
HTTP request sent, awaiting response... 502 Proxy Error
09:12:20 ERROR 502: Proxy Error.
It looks a bit like a sourceforge issue, but this really throws me off
balance. I am a bit puzzled by the above warnings. Are they meant to be?
Thanks
Erich
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel