Closed rasmus-madsen closed 4 years ago
This line is odd:
Error: Error building site: process: readAndProcessContent: walk: Readdir: decorate: lstat /home/rasmus/opnetitan/rasmus@JBMPTN2.323: no such file or directory
Where's the opnetitan
typo coming from?
That is just my git path i accidentally made a typo wheb i created the folder
Hent Outlook til Androidhttps://aka.ms/ghei36
From: Philipp Wagner notifications@github.com Sent: Monday, October 26, 2020 3:21:35 PM To: lowRISC/opentitan opentitan@noreply.github.com Cc: Rasmus Madsen Rasmus.Madsen@wdc.com; Author author@noreply.github.com Subject: Re: [lowRISC/opentitan] [doc:build_docs.py] can't build document on ubunt WSL for windows 10 (#3901)
This line is odd:
Error: Error building site: process: readAndProcessContent: walk: Readdir: decorate: lstat /home/rasmus/opnetitan/rasmus@JBMPTN2.323: no such file or directory
Where's the opnetitan typo coming from?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/lowRISC/opentitan/issues/3901#issuecomment-716578668, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AM3LL7ZTNWQUXT34O232RS3SMWAW7ANCNFSM4S7NRDVQ.
@imphil I was looking in the usbdev/data/usbdev.prj.hjson that it seem to complain about but I don't see any problems there.
This looks like https://github.com/gohugoio/hugo/issues/6526, which points at emacs backup files created in the opentitan directory, which then hang hugo (it's surprisingly picky about things in the opentitan tree it shouldn't care about). Can you try to read through the linked issue and see if any of the proposed workarounds do the trick for you?
I'd try to
rm -f /home/rasmus/opnetitan/rasmus@JBMPTN2.*
rm -rf /home/philipp/src/opentitan/build/docs
closing emacs worked for some odd reason.. thank you
previously I have not had any issues building the document on my Linux subsystem but even after upgrading and updating I am having this issue.
I see doxygen spits out a huge file of warnings but I didn't find anything in the file to indicate the actual problem. but I am not sure how to continue my debugging