<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "http://bugs.gentoo.org/bugzilla.dtd">

<bugzilla version="2.22.7"
          urlbase="http://bugs.gentoo.org/"
          maintainer="bugzilla@gentoo.org"
>

    <bug>
          <bug_id>21548</bug_id>
          
          <creation_ts>2003-05-23 09:36 0000</creation_ts>
          <short_desc>app-emulation/mol fails to build with binutils &gt;=2.14</short_desc>
          <delta_ts>2006-02-04 06:03:46 0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>Gentoo Linux</product>
          <component>Applications</component>
          <version>unspecified</version>
          <rep_platform>PPC</rep_platform>
          <op_sys>Linux</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WONTFIX</resolution>
          
          
          
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          
          <everconfirmed>1</everconfirmed>
          <reporter>vincent.strubel+gentoo@m4x.org</reporter>
          <assigned_to>ppc@gentoo.org</assigned_to>
          <cc>dholm@gentoo.org</cc>

      

      
          <long_desc isprivate="0">
            <who>vincent.strubel+gentoo@m4x.org</who>
            <bug_when>2003-05-23 09:36:30 0000</bug_when>
            <thetext>Emerging Mac-on-Linux fails on my system after upgrading to binutils-2.14.90 
(both .1-r1 and .2). The error is as follows: 
... 
Making all in kmod 
Making all in Linux 
=========================================================== 
 Kernel headers:          /lib/modules/2.4.20-ben10/build/include 
 Module compiled for:     2.4.20-ben10 
 Running kernel:          2.4.20-ben10 
=========================================================== 
gcc -E -D__ASSEMBLY__  -I../..  -I./ -DMODVERSIONS -include 
/lib/modules/2.4.20-ben10/build/include/linux/modversions.h -D__KERNEL__ 
-DMODULE -I../../src/kmod/include                       -I../../src/shared -I- 
-I/lib/modules/2.4.20-ben10/build/include traps.S | m4 -s  | tr &apos;;&apos; &apos;\n&apos; &gt; traps.o.s 
as traps.o.s  -o traps.o 
emulation.S: Assembler messages: 
emulation.S:738: Error: too many positional arguments 
emulation.S:742: Error: too many positional arguments 
emulation.S:746: Error: too many positional arguments 
emulation.S:750: Error: too many positional arguments 
emulation.S:754: Error: too many positional arguments 
emulation.S:758: Error: too many positional arguments 
emulation.S:762: Error: too many positional arguments 
emulation.S:766: Error: too many positional arguments 
emulation.S:770: Error: too many positional arguments 
emulation.S:774: Error: too many positional arguments 
emulation.S:778: Error: too many positional arguments 
emulation.S:782: Error: too many positional arguments 
emulation.S:786: Error: too many positional arguments 
emulation.S:790: Error: too many positional arguments 
emulation.S:794: Error: too many positional arguments 
emulation.S:798: Error: too many positional arguments 
make[3]: *** [traps.o] Error 1 
make[2]: *** [all-recursive] Error 1 
make[1]: *** [all-recursive] Error 1 
make: *** [all-recursive] Error 1 
 
I get this with either mol-0.9.68-r4 or mol-0.9.69_pre1, on two different kernels ( 
ppc-sources-benh-2.4.20-r10 or 2.4.21-rc2-ben0), with gcc-3.2.2-r2 or 
-3.2.3-r1. Changing my CFLAGS to very basic ones gives me the same error. 
After downgrading to binutils-2.13.90.0.18-r1, both versions of mol build and work 
fine again. 

Reproducible: Always
Steps to Reproduce:
1.emerge &gt;=binutils-2.14.90.0.1-r1 
2.emerge mol 
3. 



 
  Portage 2.0.48_pre6 (default-ppc-1.4, gcc-3.2.3, glibc-2.3.2-r0) 
================================================================= 
System uname: 2.4.20-ben10 ppc 
GENTOO_MIRRORS=&quot;http://gentoo.linux.no 
http://www.ibiblio.org/pub/Linux/distributions/gentoo&quot; 
CONFIG_PROTECT=&quot;/etc /var/qmail/control /usr/share/config 
/usr/kde/2/share/config /usr/kde/3/share/config 
/usr/X11R6/lib/X11/xkb:/usr/kde/3.1/share/config:/usr/share/texmf/tex/generic/config/ 
/usr/share/texmf/tex/platex/config/:/usr/share/config&quot; 
CONFIG_PROTECT_MASK=&quot;/etc/gconf /etc/env.d&quot; 
PORTDIR=&quot;/usr/portage&quot; 
DISTDIR=&quot;/usr/portage/distfiles&quot; 
PKGDIR=&quot;/usr/portage/packages&quot; 
PORTAGE_TMPDIR=&quot;/var/tmp&quot; 
PORTDIR_OVERLAY=&quot;/usr/local/portage&quot; 
USE=&quot;oss dvd mitshm ppc gnome-libs gtkhtml gdbm berkdb slang aalib bonobo 
tcltk java guile sdl gpm tcpd pam libwww ssl perl python esd imlib gtk motif mozilla 
-gnome X xv freetype truetype fbcon gtk2 socks5 nls cjk pdflib tetex kde qt qt-mt 
alsa arts xmms oggvorbis jpeg png tiff gif mpeg quicktime altivec moznomail 
moznoirc moznocompose mozsvg encode cups directfb pic cdr doc flash gb jikes 
opengl plotutils readline&quot; 
COMPILER=&quot;gcc3&quot; 
CHOST=&quot;powerpc-unknown-linux-gnu&quot; 
CFLAGS=&quot;-O2 -pipe -mcpu=7450 -maltivec -mabi=altivec -mpowerpc-gfxopt 
-fsigned-char&quot; 
CXXFLAGS=&quot;-O2 -pipe -mcpu=7450 -maltivec -mabi=altivec -mpowerpc-gfxopt 
-fsigned-char&quot; 
ACCEPT_KEYWORDS=&quot;ppc ~ppc&quot; 
MAKEOPTS=&quot;-j2&quot; 
AUTOCLEAN=&quot;no&quot; 
SYNC=&quot;rsync://rsync.gentoo.org/gentoo-portage&quot; 
FEATURES=&quot;noauto ccache&quot;</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>lu_zero@gentoo.org</who>
            <bug_when>2003-05-23 14:23:28 0000</bug_when>
            <thetext>confirmed, we&apos;ll need some time to discover what&apos;s wrong, please downgrade in the mean time just to build mol, if you need it badly.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>lu_zero@gentoo.org</who>
            <bug_when>2003-05-23 22:52:02 0000</bug_when>
            <thetext>seems that the current source (from rysnc) doesn&apos;t have the issue, builds cleanly, maybe we&apos;ll roll a snapshot or backport the fix.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>lu_zero@gentoo.org</who>
            <bug_when>2003-05-24 20:17:41 0000</bug_when>
            <thetext>new snapshot uploaded, it builds correctly</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>dholm@gentoo.org</who>
            <bug_when>2003-10-13 13:05:49 0000</bug_when>
            <thetext>0.9.69* is broken on the Pegasos at the moment (it is a known problem). So
perhaps we/I should try to get 0.9.68 to compile again.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>pylon@gentoo.org</who>
            <bug_when>2004-01-29 20:33:18 0000</bug_when>
            <thetext>Or could you test the 0.9.70_rc2?</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>dholm@gentoo.org</who>
            <bug_when>2004-01-29 23:47:02 0000</bug_when>
            <thetext>I&apos;ll try that when the new Pegasos kernel is finished. It will take at least another week though since the developer is on vacation.
Early rumors state that recent versions from CVS work though.</thetext>
          </long_desc>
          <long_desc isprivate="0">
            <who>dholm@gentoo.org</who>
            <bug_when>2004-02-04 10:53:23 0000</bug_when>
            <thetext>The 0.70 snapshot works great on Pegasos so 0.68 is no longer needed.</thetext>
          </long_desc>
      
    </bug>

</bugzilla>