Displaying 2 results from an estimated 2 matches for "make1".
Did you mean:
make
2005 May 18
1
cvs commit: src/usr.bin/make job.c
...Assume badmake has same uid, so it can create a file in the uniq
> directory. (Of course this means that the bad guy already has
> your account.)
> Normal pattern:
> ---------------------
> make0: uses mkdtmp() to create dir /tmp/4321
> make0: tries to create fifo /tmp/4321
> make1: uses mkdtmp() to create dir /tmp/4321 but fails
> make1: mkdtmp() next tries to create /tmp/4322 successs
> make1: tries to create fifo /tmp/4322
>
>
> Sort of DOS:
> ---------------------
> make: uses mkdtmp() to create /tmp/1234/
>
> badmake: watches for creati...
2006 Feb 28
1
[LLVMdev] Leading spaces in Makefile.rules
...configuring with:
./configure --enable-debug-runtime --enable-jit --prefix=/opt/lvm-cvs
I then got a message indicating that Line 1099 of Makefile.rules has 8
leading spaces instead of a tab, I fixed that and then the build
completed, although there were 6 warnings
(http://www.saville.com/llvm/make1.out).
Reid suggested here
(http://lists.cs.uiuc.edu/pipermail/llvmdev/2006-February/005261.html)
that I install new runtime bytecodes. I did and then did:
make clean ; make
And got 4 warnings here (http://www.saville.com/llvm/make2.out).
Maybe the warnings are normal, just thought I'd...