Bug 4492 - Unable to build lesstif due to gcc inline asm errors
Summary: Unable to build lesstif due to gcc inline asm errors
Status: RESOLVED DUPLICATE of bug 4593
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL: http://pkgsubmit.mageia.org/uploads/f...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-12 08:11 CET by Funda Wang
Modified: 2012-02-20 03:53 CET (History)
4 users (show)

See Also:
Source RPM: lesstif
CVE:
Status comment:


Attachments

Description Funda Wang 2012-02-12 08:11:55 CET
When building lesstif, I've got following errors:

libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include/Motif-2.1 -I../../include/Motif-2.1 -I/usr/include -I/usr/include/freetype2 -I/usr/include -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -DMWM_DDIR=\"/usr/share/X11/mwm\" -c XmString.c  -fPIC -DPIC -o .libs/XmString.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include/Motif-2.1 -I../../include/Motif-2.1 -I/usr/include -I/usr/include/freetype2 -I/usr/include -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -DMWM_DDIR=\"/usr/share/X11/mwm\" -c LTV6Editres.c  -fPIC -DPIC -o .libs/LTV6Editres.o
libtool: compile:  gcc -DHAVE_CONFIG_H -I. -I. -I../../include -I../../include/Motif-2.1 -I../../include/Motif-2.1 -I/usr/include -I/usr/include/freetype2 -I/usr/include -O2 -g -pipe -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -DMWM_DDIR=\"/usr/share/X11/mwm\" -c ResConvert.c  -fPIC -DPIC -o .libs/ResConvert.o
XmString.c: In function 'XmStringGetNextTriple':
XmString.c:5484:9: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
XmString.c: In function 'XmStringComponentCreate':
XmString.c:5520:33: warning: cast from pointer to integer of different size [-Wpointer-to-int-cast]
XmIm.c: In function 'XmImCloseXIM':
XmIm.c:1067:3: warning: passing argument 1 of 'XtFree' from incompatible pointer type [enabled by default]
/usr/include/X11/Intrinsic.h:1854:13: note: expected 'char *' but argument is of type 'struct XmICStuff *'
{standard input}: Assembler messages:
{standard input}: Warning: end of file not at end of a line; newline inserted
{standard input}:1840: Error: number of operands mismatch for `test'
{standard input}: Error: open CFI at the end of file; missing .cfi_endproc directive
gcc: internal compiler error: Segmentation fault (program cc1)
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.mageia.org/> for instructions.
make[2]: *** [XmString.lo] Error 1
Comment 1 Manuel Hiebel 2012-02-13 01:16:07 CET
Any ideas guys ?

CC: (none) => arnaud.patard, tmb

Thomas Backlund 2012-02-19 23:19:25 CET

Status: NEW => ASSIGNED
Depends on: (none) => 4593
Assignee: bugsquad => tmb

Comment 2 Thomas Backlund 2012-02-20 02:07:11 CET
gcc-4.6.2-2.mga2 is now available with a fix for the gcc segfault, but lesstif build fails with:

libtool: link: cannot find the library `/usr/lib64/libXext.la' or unhandled argument `/usr/lib64/libXext.la'

Assignee: tmb => bugsquad
Source RPM: gcc => lesstif

David Walser 2012-02-20 02:17:58 CET

CC: (none) => dmorganec, luigiwalser

Comment 3 Funda Wang 2012-02-20 03:51:52 CET
(In reply to comment #2)
> gcc-4.6.2-2.mga2 is now available with a fix for the gcc segfault, but lesstif
> build fails with:
> 
> libtool: link: cannot find the library `/usr/lib64/libXext.la' or unhandled
> argument `/usr/lib64/libXext.la'
Which is another problem I think.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Comment 4 Funda Wang 2012-02-20 03:52:48 CET
Acturally, this is a dup.

*** This bug has been marked as a duplicate of bug 4593 ***

Resolution: FIXED => DUPLICATE

Funda Wang 2012-02-20 03:53:23 CET

Depends on: 4593 => (none)


Note You need to log in before you can comment on or make changes to this bug.