[Lunar Linux 0000393]: Wine lin failed

[noreply at bugs.lunar-linux.org]

The following bug requires your FEEDBACK.
=======================================================================
http://bugs.lunar-linux.org/view_bug_page.php?f_id=0000393
=======================================================================
Reporter:                   scereze3
Handler:                    sofar
=======================================================================
Project:                    Lunar Linux
Bug ID:                     0000393
Category:                   moonbase
Reproducibility:            unable to duplicate
Severity:                   feature
Priority:                   none
Status:                     feedback
=======================================================================
Date Submitted:             2003-10-26 19:22 GMT
Last Modified:              2003-10-27 20:05 GMT
=======================================================================
Summary:                    Wine lin failed
Description: 
I can't lin the last Wine. This is happpening on 2 different box.

gcc -shared -Wl,-soname,libwine.so.1 config.o debug.o ldt.o loader.o
port.o  -L../../libs/port -lwine_port -ldl  -s -lm  -o libwine.so.1
config.o: file not recognized: Format de fichier non reconnu
collect2: ld returned 1 exit status
make[2]: *** [libwine.so.1] Erreur 1
make[2]: Leaving directory `/usr/src/wine-20031016/libs/wine'
make[1]: *** [wine] Erreur 2
make[1]: Leaving directory `/usr/src/wine-20031016/libs'
Creating /var/log/lunar/compile/Wine-20031016.bz2
make: *** [libs] Erreur 2
! Problem detected during BUILD

I attached the entire compile log.

seb

=======================================================================

-----------------------------------------------------------------------
 sofar - 2003-10-26 19:55 GMT 
-----------------------------------------------------------------------
Can you resubmit the compile log with the following modifications? 

- LANGUANGE in ENGLISH (please!)
- turn on DEBUG (lin -v -d -c Wine)

-----------------------------------------------------------------------
 jmhodges - 2003-10-27 06:13 GMT 
-----------------------------------------------------------------------
No problems here :-/ Weird.. need more info

-----------------------------------------------------------------------
 scereze3 - 2003-10-27 07:24 GMT 
-----------------------------------------------------------------------
ok. I upload the new compile log with the DEBBUG option. 

gcc -shared -Wl,-soname,libwine.so.1 config.o debug.o ldt.o loader.o
port.o  -L. ./../libs/port -lwine_port -ldl  -s -lm  -o libwine.so.1
++ ccache  g++ -pipe "-shared -Wl,-soname,libwine.so.1 config.o debug.o
ldt.o lo ader.o port.o -L../../libs/port -lwine_port -ldl -s -lm -o
libwine.so.1"
config.o: file not recognized: Format de fichier non reconnu
collect2: ld returned 1 exit status
make[2]: *** [libwine.so.1] Erreur 1
make[2]: Leaving directory `/usr/src/wine-20031016/libs/wine'
make[1]: *** [wine] Erreur 2
make[1]: Leaving directory `/usr/src/wine-20031016/libs'
++ devoke_installwatch ()
++ stop_logging ()
Creating /var/log/lunar/compile/Wine-20031016.bz2
make: *** [libs] Erreur 2
++ temp_destroy (/var/tmp/lunar.lin.23494.Wine.compile-log.iwwgQ23692)
++ temp_destroy (/var/tmp/lunar.lin.23494.Wine.compile-fifo.EyfmP23697)
++ temp_destroy (/var/tmp/lunar.lin.23494.Wine.installwatch.RnNPZ23631)
++ sound (FAILURE)
! Problem detected during BUILD
++ report (/var/log/lunar/compile/Wine-20031016.bz2 compile log Wine
20031016)
++ activity_log (lin Wine 20031016 failed Due to build errors during
BUILD)
++ temp_destroy (/var/tmp/lunar.lin.23494.prepared-depends.naeWi23506)

thanks

-----------------------------------------------------------------------
 jmhodges - 2003-10-27 20:05 GMT 
-----------------------------------------------------------------------
This still makes no sense to me.  Have you tried re-downloading the file? 
Also, I'm not positive on what "file not recognized" means.  I'm looking
through error messages similar to this and once in a while "rebuild your
toolchain" comes up with a couple of other questions.  I have a feeling
that the former is really your problem, otherwise you've got a mess on
your hands (and it should be affecting lots of other packages).