[LLVMdev] Still Trying to Build on MINGW
reid at x10sys.com
Sat May 6 16:28:32 PDT 2006
From your initial email, I came to the same conclusion that
llvm::sys::Path was generating the "path is not valid" message. The Path
class has platform specific knowledge of what constitutes a valid path
name on that system. Generally it uses an operating system facility to
validate path names. The fact that it declared <invalid> as "not valid"
is correct behavior, Win32 doesn't allow < and > in path names. So, the
problem isn't there.
As you surmised, the real problem is: "why does <invalid> get used as a
path name?" You are probably correct that it is something ArchiveMember
is doing. I'll look into this and see if I can come up with a better
default name or eliminate the <invalid> member altogether.
Thanks for reporting this.
On Sat, 2006-05-06 at 16:43 -0400, Greg Pettyjohn wrote:
> On Sat, 6 May 2006, Greg Pettyjohn wrote:
> > Now I'm having problems with this:
> > llvm-ar rc ./libgcc.a libgcc/./_muldi3.o <and-lots-more-.o-files...>
> > C:\msys\1.0\home\llvm_home\install\bin\llvm-ar.exe: <invalid>: path is not valid
> I've tracked this down in the debugger. It is indeed a bug. The problem is
> that Path::isValid() will reject a string containing "<" and ">" on
> Note that this is not the case on Unix -- compare the implementation of
> Path::isValid() in .../Unix/Path.inc to the one in .../Win32/Path.inc.
> Probably the right place to make the fix is in
> ArchiveMember::ArchiveMember() (Archive.cpp circa line 43).
> As per the comment this constructor is being used to make a "sentry node"
> in an ilist. In the initializations you will see `path("<invalid>")' which
> on Windows should be something else (perhaps just use
> I'm new to this list should I go ahead and write a bug? Or do you have
> enough info here?
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part
More information about the llvm-dev