Closed Bug 279208 Opened 20 years ago Closed 19 years ago

Compile error in xptcinvoke_linux_s390.cpp when using --enable-optimize=-O0

Categories

(SeaMonkey :: General, defect)

1.7 Branch
Other
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: markkp, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: mozilla-source-1.7.5.tar.bz2

I am trying to compile Mozilla 1.7.5 for the Slack/390 distribution.  I'm having
problems with some programs getting a segmentation fault (which I will file
another report on), so I'm trying to compile with all optimizations turned off.
 When I do that, I get the following error:
xptcinvoke_linux_s390.cpp: In function `nsresult
   XPTC_InvokeByIndex(nsISupports*, unsigned int, unsigned int, nsXPTCVariant*)
   ':
xptcinvoke_linux_s390.cpp:204: error: can't find a register in class `
   GENERAL_REGS' while reloading `asm'

In the directory  /tmp/mozilla/xpcom/reflect/xptcall/src/md/unix
The following command failed to execute properly:
c++ -o xptcinvoke_linux_s390.o -c -DOSTYPE="Linux2.4" -DOSARCH="Linux"
-DEXPORT_XPTC_API -I../../../../../../dist/include/xpcom
-I../../../../../../dist/include -I/tmp/mozilla/dist/include/nspr -I./../..
-I/usr/X11R6/include -fPIC -I/usr/X11R6/include -fno-rtti -fno-exceptions -Wall
-Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth
-Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -pedantic
-fshort-wchar -pthread -pipe -DDEBUG -D_DEBUG -DDEBUG_root -DTRACING -g
-fno-inline -O0 -I/usr/X11R6/include -DMOZILLA_CLIENT -include
../../../../../../mozilla-config.h -Wp,-MD,.deps/xptcinvoke_linux_s390.pp
xptcinvoke_linux_s390.cpp
gmake[6]: *** [xptcinvoke_linux_s390.o] Error 1


glibc 2.3.3
gcc 3.3.4
I am specifying these configure options:
BUILD_OFFICIAL=1 MOZILLA_OFFICIAL=1 \
./configure --prefix=/usr \
  --enable-optimize=-O0 \
  --with-default-mozilla-five-home=/usr/lib/mozilla-1.7.5 \
  --enable-strip-libs \
  --disable-tests \
  --disable-short-wchar \
  --enable-nspr-autoconf \
  --enable-calendar \
  --enable-extensions=default,irc \
  --enable-crypto \
  --disable-xprint \
  --without-system-nspr \
  --with-system-zlib \
  --enable-default-toolkit=gtk2 \
  --disable-freetype2 \
  --enable-xft



Reproducible: Always

Steps to Reproduce:
1. Untar the source on a Linux/390 system
2. Run the provided configure command
3. Run BUILD_OFFICIAL=1 MOZILLA_OFFICIAL=1 make -s export
4. Run BUILD_OFFICIAL=1 MOZILLA_OFFICIAL=1 make -j4 -s libs


Actual Results:  
Things compiled fine until the xptcinvoke_linux_s390.cpp module.

Expected Results:  
Not generated a compilation error.
Version: unspecified → 1.7 Branch
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.