Displaying 4 results from an estimated 4 matches for "absbuilddir".
Did you mean:
abs_builddir
2008 Dec 10
2
[LLVMdev] Trouble Building llvm-gcc-4.2
...ultBranch='trunk'))
checking=""
if optimized == "--disable-optimized":
checking="--enable-checking"
f.addStep(Configure(workdir="llvm-gcc-4.2/obj", command=["../src/configure",
WithProperties("--prefix=%s/install", "absbuilddir"),
"--program-prefix=llvm-",
WithProperties("--enable-llvm=%s/build-llvm-initial/obj", "absbuilddir"),
"--enable-languages=c,c++", checking]))
f.addStep(WarningCountingShellCommand, workdir="llvm-gcc-4.2/obj", name =
"llvm-gcc-4.2_cl...
2008 Dec 10
0
[LLVMdev] Trouble Building llvm-gcc-4.2
...))
> checking=""
> if optimized == "--disable-optimized":
> checking="--enable-checking"
> f.addStep(Configure(workdir="llvm-gcc-4.2/obj", command=["../src/configure",
> WithProperties("--prefix=%s/install", "absbuilddir"),
>
Are you sure buildbot provides absbuilddir?
> The initial configure of llvm-gcc-4.2 works just fine. It's the actual build
> that fails, when the configure is done is subdirectories as part of "make
> bootstrap."
>
> Any hints?
How does the config...
2008 Dec 10
2
[LLVMdev] Trouble Building llvm-gcc-4.2
...t;
> > if optimized == "--disable-optimized":
> > checking="--enable-checking"
> > f.addStep(Configure(workdir="llvm-gcc-4.2/obj",
> > command=["../src/configure", WithProperties("--prefix=%s/install",
> > "absbuilddir"),
>
> Are you sure buildbot provides absbuilddir?
Yes, I wrote a BuildStep to compute it. I know it picks it up because the
error used to tell me to provide an absolute path. That happened during
the configure stage.
> > The initial configure of llvm-gcc-4.2 works just fine....
2008 Dec 10
0
[LLVMdev] Trouble Building llvm-gcc-4.2
...if optimized == "--disable-optimized":
>>> checking="--enable-checking"
>>> f.addStep(Configure(workdir="llvm-gcc-4.2/obj",
>>> command=["../src/configure", WithProperties("--prefix=%s/install",
>>> "absbuilddir"),
>>>
>> Are you sure buildbot provides absbuilddir?
>>
>
> Yes, I wrote a BuildStep to compute it. I know it picks it up because the
> error used to tell me to provide an absolute path. That happened during
> the configure stage.
>
>
&...