Am 12.08.2017 um 15:56 schrieb Jim Jagielski:
> Can you provide what 'echo $PATH' shows before autoconf and
> after the sourcing of winenv.set.sh?
>
> tia!
Sure!
Before "autoconf":
$ echo $PATH
/usr/local/bin:/usr/bin:/cygdrive/c/ProgramData/Oracle/Java/javapath:/cygdrive/c/Windows/system32:/cyg
Can you provide what 'echo $PATH' shows before autoconf and
after the sourcing of winenv.set.sh?
tia!
> On Aug 12, 2017, at 9:45 AM, Matthias Seidel
> wrote:
>
> Am 12.08.2017 um 15:14 schrieb Jim Jagielski:
>> Considering that the build system for OO depends on pollution, oops,
>> I mean *pop
Am 12.08.2017 um 15:14 schrieb Jim Jagielski:
> Considering that the build system for OO depends on pollution, oops,
> I mean *population* of the environment, I just wonder if that may
> be an issue.
>
> Are you using the default bash* startup scripts? Any modifications?
> That sort of thing?
I ne
Considering that the build system for OO depends on pollution, oops,
I mean *population* of the environment, I just wonder if that may
be an issue.
Are you using the default bash* startup scripts? Any modifications?
That sort of thing?
-
No, I initially build with Win 7 Home 32bit before I switched to Win 10
Pro 64bit (just to see if it works...).
The installed software looks good.
You could deinstall all (3) Versions of MS Visual C++ 2008
Redistributable 9.0.30729 leaving only the two with 9.0.30729.6161.
Am 11.08.2017 um 18:37
I wonder if it's because I'm on Win7, Home Premium.
The list of installed s/w looks correct:
http://home.apache.org/~jim/AOO-builds/aoobuilder-sw.png
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additi
FWIW, my builds never require multiple steps and I always build with
"build --all -P2 -- -P2"
The environment is important, you can see my setup for RC1 here:
http://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.1.4/wntmsci/ReadMe.txt
Am 11.08.2017 um 16:39 schrieb Jim Jagielski:
Yep... I've disabled using '--P2 -- --P2' as well, in
case it's something about parallel jobs, etc.
Weird as anything. The only thing I can think of is that
the links on the step-to-step guide are pointing to newer
versions of things, which is what is breaking my win7 builds.
I may try w/ a super
Have you tried repeating "build --all" a few times?
I quite often have failures that go away with a few repeated builds. My
interpretation is that whatever is supposed to make sure all
dependencies are satisfied before building a module does not quite work
right. Sooner or later, everything th
I've tried reinstalling, putting stuff in different locations,
etc... I just cannot get aoo-414 building on my windows7 VM.
I am following the step-by-step guide to the letter.
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.
> On Aug 8, 2017, at 12:59 PM, Don Lewis wrote:
>
> On 8 Aug, Jim Jagielski wrote:
>> It looks like some sort of variable interpolation issue... Note
>> that it's trying to do:
>>
>>- | awk -f C:/cygwin$S/solenv/gbuild/processdeps.awk
>>
>> Now with:
>>
>>S=$R/main
>>R=c:/cygwin
The only thing I can think of is some sort of env pollution
causing that... starting from a fresh dwnload.
> On Aug 8, 2017, at 12:59 PM, Don Lewis wrote:
>
> On 8 Aug, Jim Jagielski wrote:
>> It looks like some sort of variable interpolation issue... Note
>> that it's trying to do:
>>
>>-
On 8 Aug, Jim Jagielski wrote:
> It looks like some sort of variable interpolation issue... Note
> that it's trying to do:
>
> - | awk -f C:/cygwin$S/solenv/gbuild/processdeps.awk
>
> Now with:
>
> S=$R/main
> R=c:/cygwin/home/jim/src/asf/aoo-414
>
> you can see how what comes out
It looks like some sort of variable interpolation issue... Note
that it's trying to do:
- | awk -f C:/cygwin$S/solenv/gbuild/processdeps.awk
Now with:
S=$R/main
R=c:/cygwin/home/jim/src/asf/aoo-414
you can see how what comes out is:
- | awk -f C:/cygwinc:/cygwin/home/jim/src/a
I ran into this same error as well when I did an incremental build
starting from expat. Cleaning and doing a full build worked.
On 8 Aug, Patricia Shanahan wrote:
> Regardless of anything else you do, retry the full build, without
> cleaning but also without specifying starting from the failure
Regardless of anything else you do, retry the full build, without
cleaning but also without specifying starting from the failure.
Sometimes the windows builds don't seem to get all the dependency
ordering right. If that is the cause of the failure, repeating the build
can resolve it. For examp
Getting errors when building under Win7:
[ build RES ] apr-util/default
[ build RES ]
R=c:/cygwin/home/jim/src/asf/aoo-414 && O=$R/main/solver/414/wntmsci12 &&
W=$R/main/solver/414/wntmsci12/workdir && S=$R/main && $O/bin/makedepend.exe
-I. -IC:/cygwin$O/inc/stl -IC:/cygwin$O/inc/external -IC:/
17 matches
Mail list logo
