Dear Erik,
That's my guess. :)
I will try it later. I don't believe a mature system like linux can not
handle the long filename. But on the other hand, no one will use this
filename unless it is a test pattern for filesystem and in my case, it is.
So ... wait for a while to see whether it is the problem of relative path
or absolute path.
Thanks!
Best regards!
Sincerely,
Alex Zhu
Quality Engineering Department III
Sunnorth Electronic Technology Co., Ltd.
Tel: +86-10-62981668 Ext. 2792 (Office) / 2056 (3G Lab)
Fax: +86-10-62985972
Email: bohao@sunnorth.com.cn
"Erik Huelsmann" <ehuels@gmail.com> 亟噐 2007-11-26 18:14:49:
> On 11/26/07, 幀鴎裟 <bohao@sunnorth.com.cn> wrote:
> >
> > Hi Erik,
> >
> > Thanks for your kindly reply.
> >
> > It may not be the problem of APR for I tried to compile the latest APR
> > (1.2.x) with SVN and the same error occured.
> >
> > I guess there is nothing to do with absolute or relative paths. I
checkouted
> > the repository using the command like this:
> >
> > svn co https://aaa.bbb.ccc/aaa/bbb/ccc
>
> Just out of curiosity: why do you think this doesn't have to do with
> absolute paths? I'm not seeing absolute paths in the command above...
>
> To be more specific, the documentation for 'svn co' and 'svn up'
> documents to expand missing targets to '.' (ie the current directory).
> '.' is a relative path. This means the command above is interpreted /
> translated to
>
> svn co https://aaa.bbb.ccc/aaa/bbb/ccc .
>
>
> HTH,
>
>
> Erik.
Received on Mon Nov 26 11:44:35 2007