Le lun 01/09/2003 à 09:42, mk793652@mail.inf.tu-dresden.de a écrit :
> Hi Jérôme,
>
> > This is just a reminder of the problems I still see with the build
> > system (maybe to add to the TODO if not already there?):
> > - still needs to be real root user to build at some time (fakeroot is
> > not enough, for whatever reason)
>
> Please move away your ~/.sversionrc and see if the build succeeds (with
> fakeroot). I have to do this for my build. Otherwise ~/.sversionrc gets
> clobbered and the install stage fails. Nobody has confirmed this so far.
> Maybe your problem is the same.
This is exactly the problem:
/home/jwarnier/debian/ooo/openoffice.org-1.0.99+1.1rc3/vcl/unx/source/src
...
/home/jwarnier/debian/ooo/openoffice.org-1.0.99+1.1rc3/vcl/unx/source/gdi/native-msgbox
------------------------------
Making: ../../../../unxlngi4.pro/misc/salgdimsgbox.dpc
dmake subdmake=true -f makefile.mk instsetext="" depend=t ALLDPC
------------------------------
No Dependencies
-------------
setenv UGLY_HACK_INDEED "/LD_LIBRARY_PATH"; \
unsetenv LD_LIBRARY_PATH; \
gcc-3.0 `pkg-config --cflags gtk+-2.0` `pkg-config --libs
gtk+-2.0` -o ../../../../unxlngi4.pro/bin/msgbox-gnome msgbox.c; \
setenv LD_LIBRARY_PATH "/UGLY_HACK_INDEED"
pkg-config: error while loading shared libraries: libfakeroot.so.0:
cannot open shared object file: No such file or directory
pkg-config: error while loading shared libraries: libfakeroot.so.0:
cannot open shared object file: No such file or directory
gcc-3.0: error while loading shared libraries: libfakeroot.so.0: cannot
open shared object file: No such file or directory
/home/jwarnier/debian/ooo/openoffice.org-1.0.99+1.1rc3/vcl/source/control
>
> > - // building is still not possible, yet could be really useful (can I
> > do something to help with this? Can I try and tell where it breaks?)
>
> Hah. I had to see your // symbol so many times until I realized that it
> means parallel. I'm sure that the tools.openoffice.org people want to know
> where parallel compiling breaks.
Well, it seems to me // always represent parallelism, but maybe your
understanding is different?
I think they already know where it breaks. And I know I could submit bug
reports with attached log outputs, but I don't know how to do it in a
useful fashion.
> Regards,
> Martin
--
Jérôme Warnier <jwarnier@beeznest.net>
Attachment:
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e?=