Hi all,
I tried to build LibO on Linux-x64 with KDE 4 (openSUSE 11.4-x64) from a fresh
cloned
master and the build failed inside the module vcl. I then did source
./LinuxX86-64Env.Set.sh and walked to vcl and run a make -r. That gave me the
following output in the shell:
[ build DEP ] LNK:Lib
On Sun, 2011-07-17 at 00:17 +0200, Andreas Mantke wrote:
> Hi all,
>
> I tried to build LibO on Linux-x64 with KDE 4 (openSUSE 11.4-x64) from a
> fresh cloned
> master and the build failed inside the module vcl. I then did source
> ./LinuxX86-64Env.Set.sh and walked to vcl and run a make -r. Th
Hi Caolan, *,
Am Dienstag, 19. Juli 2011, 12:23:20 schrieb Caolán McNamara:
> On Sun, 2011-07-17 at 00:17 +0200, Andreas Mantke wrote:
> > Hi all,
> >
> > I tried to build LibO on Linux-x64 with KDE 4 (openSUSE 11.4-x64) from a
> > fresh cloned master and the build failed inside the module vcl. I
Hi Andreas,
On Tue, 2011-07-19 at 20:29 +0200, Andreas Mantke wrote:
> I used the same machine in the past for building with openSUSE 11.3-x64. In
> the
> meantime I updated to 11.4 using zypper -dup. Thus you could see it as a
> fresh
> install.
I assume you re-ran autogen.sh from a
Hi Michael, Caolan, *,
Am Mittwoch, 20. Juli 2011, 12:12:51 schrieb Michael Meeks:
> Hi Andreas,
>
> On Tue, 2011-07-19 at 20:29 +0200, Andreas Mantke wrote:
> > I used the same machine in the past for building with openSUSE 11.3-x64.
> > In the meantime I updated to 11.4 using zypper -dup. Thus
Hi Michael, Caolan, *,
Am Mittwoch, 20. Juli 2011, 20:07:14 schrieb Andreas Mantke:
> Hi Michael, Caolan, *,
>
> Am Mittwoch, 20. Juli 2011, 12:12:51 schrieb Michael Meeks:
> > Hi Andreas,
> >
> > On Tue, 2011-07-19 at 20:29 +0200, Andreas Mantke wrote:
> > > I used the same machine in the past
Hi Michael, Caolan, *,
Am Mittwoch, 20. Juli 2011, 20:07:14 schrieb Andreas Mantke:
> Hi Michael, Caolan, *,
>
> Am Mittwoch, 20. Juli 2011, 12:12:51 schrieb Michael Meeks:
(...)
> > > ./autogen.sh --with-num-cpus=2 --with-max-jobs=2 --without-junit
> > > --with-lang=de
> > >
> > > --enable-kde
There's no actual compiler/linker error included in that log. Its a
parallel build and the error messages from vcl itself are probably mile
back in your buffer. Just do a make -sr in vcl which is the reported
failed module and post the results here.
Your very first post had the type of information
Hi Andreas,
On Wed, 2011-07-20 at 21:59 +0200, Andreas Mantke wrote:
> a complete clean building in a new / clean shell with a fresh autogen.sh with
> the
> options above didn't help, but now I get another error inside vcl (vcl
> seemed to be
> an nightmare to me):
Goodness - lets ho
Hi Caolan, Michael, *,
Am Donnerstag, 21. Juli 2011, 12:58:53 schrieb Caolán McNamara:
> There's no actual compiler/linker error included in that log. Its a
> parallel build and the error messages from vcl itself are probably mile
> back in your buffer. Just do a make -sr in vcl which is the repor
Undefined references are typically because of a change that is missing
on your copy of the repo.
I would do the following: ./g pull -r ; autogen.sh; make dev-install
Marc-André Laverdière
Software Security Scientist
Innovation Labs, Tata Consultancy Services
Hyderabad, India
On 07/21/2011 10:57
On Fri, 2011-07-22 at 16:03 +0530, Marc-André Laverdière wrote:
> Undefined references are typically because of a change that is missing
> on your copy of the repo.
>
> I would do the following: ./g pull -r ; autogen.sh; make dev-install
won't help, the missing symbols aren't *our* symbols, they
12 matches
Mail list logo
