Created attachment 45599 [details]
diff of m213 and m214 of LinuxX86Env.Set.sh

The Linux is SLES 10 Eval.

looking at the provided snippet of your LinuxX86Env.Set.sh leaves the guess that
you're using python from your system. in that case you shouldn't need
pyversion.mk at all (see /pyuno/source/module/makefile.mk).
please check your environment.

Yes. I don't know why, but I find these ERROR where deliver. And after ERROR
behind d.lst files no deliver. I want to know how solve this problem. The ERROR is:

strip: /SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll.4239-1180869851:
二义性的文件格å¼
strip：匹é…æ ¼å¼ï¼š efi-app-ia32 pei-i386
strip：匹é…æ ¼å¼ï¼š efi-app-ia32 pei-i386
deliver: /SRC680_m214/external/prj/d.lst: ERROR: Failed to execute strip -R
'.comment' -s /SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll.4239-1180869851

strip:
/SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe.2445-1180870702:
二义性的文件格å¼
strip：匹é…æ ¼å¼ï¼š efi-app-ia32 pei-i386
strip：匹é…æ ¼å¼ï¼š efi-app-ia32 pei-i386
deliver: /SRC680_m214/python/prj/d.lst: ERROR: Failed to execute strip -R
'.comment' -s
/SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe.2445-1180870702

your linux directories contain windows binaries??? are you trying to
crosscompile? please check your environment.

after that, try to cleanup your solver from *.exe and *.dll and remove the
output tree in python.

I build m212 no problem use default params of configure. But when build m214,
there are these problems. How can disable "cross compile" when configure? I
don't want to build OOo with "cross compile". I only want to build newer OOo on
SLE 10. thx.

Ause: 
- 'unowinreg.dll' is the only thing which even in 'standard' builds eventually
gets cross compiled. If now, you have to have a precompiled version in your
tree, as you need this windows dll even in uniox builds for creating SDK sets.
- 'python2.3/distutils/command/wininst.exe' also seems to exist in python's
output trees of all platforms, though I have no idea why ...
In other words: these two file names alone are not a sign of a corrupted
environment.

jlcheng:
concerning that deliver error: I do not understand why at all deliver tries to
strip those two files. Can you please check what the 'file' command states about
them? Do
> file /SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll
> file /SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe
or, if the files are not present in solver, something like 
> file python/unxlngi6.pro/misc/build/Python-2.3.4/Lib/distutils/command/wininst.exe
and report the output here.

rt:
Ok, thx. And I want to test for configure --disable-odk to solver
"unowinreg.dll". Or I don't use precompiled version "unowinreg.dll". But the
2nd, I don't know how to do. I can try no deliver the file "wininst.exe", I
modify d.lst.
Now I only think there some problem in my Linux. But the m212 has no this problem.

lcheng :
--disable-odg or not delivering some files is not the solution here. It looks as
if the root cause of your problems is much deeper. You somehow have an insane
environment:
- apparently 'file unowinreg.dll' does not return what I would expect for a
linux environment
- environment variable GUI or SYSTEM_PYTHON also is not as I would expect (see
Auses comment above: if you configure with system-python, pyversion.mk should
not be included at all)

So, please thoroughly check your configure line. Get a new shell, carefully set
your environment, and try to reproduce. Do 'file unowinreg.dll', 'echo $GUI',
and 'echo $SYSTEM_PYTHON', and paste the output here.

file SRC680_m214/external/unowinreg/unowinreg.dll
SRC680_m214/external/unowinreg/unowinreg.dll: PE executable for MS Windows (DLL)
(console) Intel 80386 32-bit

No this file: SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll

file SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll.2015-1181039382
SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll.2015-1181039382: PE
executable for MS Windows (DLL) (console) Intel 80386 32-bit

No this file:
SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe
file
SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe.24553-1181039534
SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe.24553-1181039534:
PE executable for MS Windows (GUI) Intel 80386 32-bit

file
SRC680_m214/python/unxlngi6.pro/misc/build/Python-2.3.4/Lib/distutils/command/wininst.exe
SRC680_m214/python/unxlngi6.pro/misc/build/Python-2.3.4/Lib/distutils/command/wininst.exe:
PE executable for MS Windows (GUI) Intel 80386 32-bit


ls -l
SRC680_m214/python/unxlngi6.pro/misc/build/Python-2.3.4/Lib/distutils/command/wininst.exe
-rwxr-xr-x 1 94717 261 57344 2004-05-26 02:47
SRC680_m214/python/unxlngi6.pro/misc/build/Python-2.3.4/Lib/distutils/command/wininst.exe

ls -l SRC680_m214/external/unowinreg/unowinreg.dll
-rw------- 1 root root 6144 2007-06-04 19:54
SRC680_m214/external/unowinreg/unowinreg.dll


The environment variable GUI or SYSTEM_PYTHON have nothing.
My configure is not with system-python.

Maybe these information is helpful. My m212 is complete build, no any problem.
Thanks all.

Created attachment 45660 [details]
LinuxX86Env.Set.sh of m212

Created attachment 45661 [details]
LinuxX86Env.Set.sh diff m212 and m214

Created attachment 45662 [details]
config.log of m212

Created attachment 45663 [details]
config.log diff of m212 and m214

try

export LANG=C
strip -R
'.comment' -s /SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll 
or wherever you find that file...

and paste the result

And, yes, between m212 and m214 deliver.pl got changed so that now files of type
"PE executable" get stripped. I just do not know why stripping fails in your
build, it does not do so here. Therefore it really could help to get that output
Ause (hjs) asked for. (I simply cannot understand the error message you pasted
earlier.)

The Ause (hjs) test command, I will check tonight. Thanks. Maybe, my SLES 10
Eval has some problem, I can't solve :(

I translate the Chinese to English(Google Translate):
strip: /SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll.4239-1180869851:
ambiguity file format
strip：Match format: efi-app-ia32 pei-i386
strip：Match format: efi-app-ia32 pei-i386
deliver: /SRC680_m214/external/prj/d.lst: ERROR: Failed to execute strip -R
'.comment' -s /SRC680_m214/solver/680/unxlngi6.pro/bin/unowinreg.dll.4239-1180869851

strip:
/SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe.2445-1180870702:
ambiguity file format
strip：Match format: efi-app-ia32 pei-i386
strip：Match format: efi-app-ia32 pei-i386
deliver: /SRC680_m214/python/prj/d.lst: ERROR: Failed to execute strip -R
'.comment' -s
/SRC680_m214/solver/680/unxlngi6.pro/lib/python/distutils/command/wininst.exe.2445-1180870702

# export LANG=C

# strip -R '.comment' -s unowinreg.dll

strip: unowinreg.dll: File format is ambiguous
strip: Matching formats: efi-app-ia32 pei-i386
strip: Matching formats: efi-app-ia32 pei-i386

# strip --help
strip: supported targets: elf32-i386 a.out-i386-linux efi-app-ia32 elf32-little
elf32-big elf64-alpha ecoff-littlealpha elf64-little elf64-big elf32-littlearm
elf32-bigarm elf32-hppa-linux elf32-hppa elf64-ia64-little elf64-ia64-big
efi-app-ia64 elf32-m68k a.out-m68k-linux elf32-powerpc aixcoff-rs6000
elf32-powerpcle ppcboot elf64-powerpc elf64-powerpcle aixcoff64-rs6000
elf32-s390 elf64-s390 elf32-sparc a.out-sparc-linux elf64-sparc a.out-sunos-big
elf64-x86-64 pe-i386 pei-i386 srec symbolsrec tekhex binary ihex trad-core

Yes, the SLES 10 Eval strip support too many targets :(
How can I delete some targets, I want to delete "pei-i386".

Created attachment 45689 [details]
Proposed patch for solenv/bin/deliver.pl

.

Please try attached patch for 'deliver.pl'. If it works for you, I'll try to
find a CWS for bringing it into one of the next milestones.

Thanks all.
I think this is two problem, SLES 10 Eval strip command has too many targets.
2nd the cws mingwport04 changed deliver.pl, but little problem.
Ok, now I use rt deliver.pl.patch, I had pyversion.mk file in
SRC680_m214/solver/680/unxlngi6.pro/inc/.
That's OK. The patch works very fine, very good.

Glad to hear that it works for you.

Fixed on CWS rt21 by applying attached patch.

Please verify on CWS rt21.

Vverified

Close issue.