Closed
Bug 280336
Opened 20 years ago
Closed 20 years ago
Build fails when compiling pratom.c
Categories
(NSPR :: NSPR, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: mach1, Assigned: wtc)
Details
Attachments
(1 file)
|
16.66 KB,
text/plain
|
Details |
User-Agent: Mozilla/5.0 (X11; U; Linux alpha; en-US; rv:1.0.2) Gecko/20030716 Build Identifier: Mozilla/5.0 (X11; U; Linux alpha; en-US; rv:1.0.2) Gecko/20030716 The compilation of pratom.c fails with several parse errors. I will attach a log of the build. Reproducible: Always
| Assignee | ||
Comment 2•20 years ago
|
||
The inline assembly code that caused your build to fail was a patch that falk@debian.org submitted (see bug 151709 comment 1). falk, could you help me with this bug report? I don't have a Linux alpha machine. mach1, please provide the version info of gcc and as on your system. (Try "gcc -v" and "as -V".)
(In reply to comment #2) > The inline assembly code that caused your build > to fail was a patch that falk@debian.org submitted > (see bug 151709 comment 1). The syntax for the asm constraints was apparently only introduced in gcc 3.1. This could be circumvented ad the cost of decreased readability. However, IIRC gccs that old miscompiled mozilla anyway, so I would prefer to document at least 3.3 is needed, or similar.
My gcc version is 2.96. I have no heartburn with upgrading to gcc 3.3 if you can tell me where to get the alpha rpm.
| Assignee | ||
Comment 5•20 years ago
|
||
Marked the bug WONTFIX. We will instead require a minimum gcc version (3.1) for building NSPR on Linux Alpha.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
| Assignee | ||
Comment 6•20 years ago
|
||
I'm not that familiar with gcc releases, so please recommend a minimum version. I put version 3.1 in my previous comment just as a placeholder.
(In reply to comment #6) > I'm not that familiar with gcc releases, > so please recommend a minimum version. I'd suggest gcc 3.3, since 3.1 and 3.2 were never used widely and will most likely not be tested properly with mozilla.
You need to log in
before you can comment on or make changes to this bug.
Description
•