Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 116169 - Request for marking tcc-0.9.22 stable (x86)
Summary: Request for marking tcc-0.9.22 stable (x86)
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: Gentoo Developers for the x86 Architecture
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-12-20 06:28 UTC by Luu Danh Hieu
Modified: 2006-01-08 13:30 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luu Danh Hieu 2005-12-20 06:28:34 UTC
tcc-0.9.19 fails to compile on my machine, but 0.9.22 compiles normally. Testing 0.9.22 on various scripts also went fine. Please mark tcc-0.9.22 stable :)

imsg3box ~ # emerge -av tcc

These are the packages that I would merge, in order:

Calculating dependencies ...done!
[ebuild  N    ] dev-lang/tcc-0.9.19  193 kB

Total size of downloads: 193 kB

<snip>

./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --build=i686-pc-linux-gnu
Binary  directory   /usr/bin
Library directory   /usr/lib
Include directory   /usr/include
Manual  directory   /usr/share/man
Source path      /var/tmp/portage/tcc-0.9.19/work/tcc-0.9.19
C compiler       gcc
make             make
CPU              x86
Big Endian       no
gprof enabled    no
Creating config.mak and config.h
gcc -O2 -g -Wall -mpreferred-stack-boundary=2 -march=i386 -falign-functions=0 -o tcc_g tcc.c -ldl
gcc -O2 -Wall -c -o libtcc1.o libtcc1.c
gcc -O2 -Wall -c -o bcheck.o bcheck.c
gcc -O2 -g -Wall -mpreferred-stack-boundary=2 -march=i386 -falign-functions=0 -DLIBTCC -c -o libtcc.o tcc.c
bcheck.c:172: error: conflicting types for '__bound_ptr_add'
bcheck.c:80: error: previous declaration of '__bound_ptr_add' was here
bcheck.c:172: error: conflicting types for '__bound_ptr_add'
bcheck.c:80: error: previous declaration of '__bound_ptr_add' was here
bcheck.c:231: error: conflicting types for '__bound_local_new'
bcheck.c:87: error: previous declaration of '__bound_local_new' was here
bcheck.c:231: error: conflicting types for '__bound_local_new'
bcheck.c:87: error: previous declaration of '__bound_local_new' was here
bcheck.c:247: error: conflicting types for '__bound_local_delete'
bcheck.c:88: error: previous declaration of '__bound_local_delete' was here
bcheck.c:247: error: conflicting types for '__bound_local_delete'
bcheck.c:88: error: previous declaration of '__bound_local_delete' was here
bcheck.c:281: error: conflicting types for '__bound_ptr_indir1'
bcheck.c:81: error: previous declaration of '__bound_ptr_indir1' was here
bcheck.c:281: error: conflicting types for '__bound_ptr_indir1'
bcheck.c:81: error: previous declaration of '__bound_ptr_indir1' was here
bcheck.c:282: error: conflicting types for '__bound_ptr_indir2'
bcheck.c:82: error: previous declaration of '__bound_ptr_indir2' was here
bcheck.c:282: error: conflicting types for '__bound_ptr_indir2'
bcheck.c:82: error: previous declaration of '__bound_ptr_indir2' was here
bcheck.c:283: error: conflicting types for '__bound_ptr_indir4'
bcheck.c:83: error: previous declaration of '__bound_ptr_indir4' was here
bcheck.c:283: error: conflicting types for '__bound_ptr_indir4'
bcheck.c:83: error: previous declaration of '__bound_ptr_indir4' was here
bcheck.c:284: error: conflicting types for '__bound_ptr_indir8'
bcheck.c:84: error: previous declaration of '__bound_ptr_indir8' was here
bcheck.c:284: error: conflicting types for '__bound_ptr_indir8'
bcheck.c:84: error: previous declaration of '__bound_ptr_indir8' was here
bcheck.c:285: error: conflicting types for '__bound_ptr_indir12'
bcheck.c:85: error: previous declaration of '__bound_ptr_indir12' was here
bcheck.c:285: error: conflicting types for '__bound_ptr_indir12'
bcheck.c:85: error: previous declaration of '__bound_ptr_indir12' was here
bcheck.c:286: error: conflicting types for '__bound_ptr_indir16'
bcheck.c:86: error: previous declaration of '__bound_ptr_indir16' was here
bcheck.c:286: error: conflicting types for '__bound_ptr_indir16'
bcheck.c:86: error: previous declaration of '__bound_ptr_indir16' was here
make: *** [bcheck.o] Error 1
make: *** Waiting for unfinished jobs....
tcc.c: In function `ieee_finite':
tcc.c:842: warning: dereferencing type-punned pointer will break strict-aliasing rules
tcc.c: In function `main':
tcc.c:9708: warning: dereferencing type-punned pointer will break strict-aliasing rules
tcc.c:9779: warning: dereferencing type-punned pointer will break strict-aliasing rules
tcc.c: In function `ieee_finite':
tcc.c:842: warning: dereferencing type-punned pointer will break strict-aliasing rules

!!! ERROR: dev-lang/tcc-0.9.19 failed.
!!! Function src_compile, Line 19, Exitcode 2
!!! (no error message)
!!! If you need support, post the topmost build error, NOT this status message.

----

imsg3box ~ # emerge --info
Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.4.4, glibc-2.3.5-r3, 2.6.14-gentoo-r2-undine i686)
=================================================================
System uname: 2.6.14-gentoo-r2-undine i686 Intel(R) Pentium(R) 4 CPU 2.40GHz
Gentoo Base System version 1.6.13
ccache version 2.3 [enabled]
dev-lang/python:     2.3.5-r2, 2.4.2
sys-apps/sandbox:    1.2.12
sys-devel/autoconf:  2.13, 2.59-r6
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O1 -march=pentium4 -pipe"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d"
CXXFLAGS="-O1 -march=pentium4 -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig ccache distlocks sandbox sfperms strict"
GENTOO_MIRRORS="ftp://ftp.ecc.u-tokyo.ac.jp/GENTOO http://gentoo.gg3.net http://gentoo.channelx.biz http://ftp.gentoo.or.kr http://mirror.gentoo.gr.jp"
LANG="en_US.UTF-8"
LC_ALL="en_US.UTF-8"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 X aac alsa apache2 apm audiofile avi bash-completion berkdb bitmap-fonts bmp bonobo browserplugin bzip2 cdr cjk crypt cups curl directfb eds emboss encode esd exif expat fam ffmpeg flac foomaticdb fortran ftp gd gdbm gif glut gmp gpm gstreamer gtk gtk2 gtkhtml howl iconv idn ieee1394 imagemagick imlib ipv6 java javascript jikes jpeg junit lcms ldap libg++ libwww lua mad matroska mhash migemo mikmod mime mmx mmxext mng motif mozilla mp3 mpeg mysql ncurses nls nptl nsplugin nvidia ogg oggvorbis opengl pam pcre pdflib perl php png python quicktime readline real recode samba sdl speex spell sse ssl svg szip tcltk tcpd tiff truetype truetype-fonts type1-fonts udev unicode verbose vorbis win32codecs wmf xine xml xml2 xosd xv xvid yahoo zlib userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LDFLAGS, LINGUAS
Comment 1 George Shapovalov (RETIRED) gentoo-dev 2005-12-20 08:04:28 UTC
Thanks for a report!

Hm, I don't feel well about moving stuff into stable that I cannot test, as I am on amd64 now and this package does not recognize this cpu :(. However I hope to get 32bit chroot going in about a month (its a space problem currently, laptop hard drives are not that big, need some external drive..) and then I'll be happy to move it into stable. That is unless somebody does that before I can, of course.
Spider: you did an update, so here is a hint for you ;). Oh, and there is that bug #109729 you might want to bump it as well, if you wish. Otherwise I'll do this when I have 32bit chroot going..

Meanwhile you can stick 
dev-lang/tcc-0.9.22 ~x86
into your /etc/portage/package.keywords..


Also, Stephanie:
I see you put -* there, claiming that other arches are unsupported, but I see this in configure script:

if test "$cpu" = "x86" ; then
  echo "ARCH=i386" >> config.mak
  echo "#define HOST_I386 1" >> $TMPH
elif test "$cpu" = "armv4l" ; then
  echo "ARCH=arm" >> config.mak
  echo "#define HOST_ARM 1" >> $TMPH
elif test "$cpu" = "powerpc" ; then
  echo "ARCH=ppc" >> config.mak
  echo "#define HOST_PPC 1" >> $TMPH
elif test "$cpu" = "mips" ; then
  echo "ARCH=mips" >> config.mak
  echo "#define HOST_MIPS 1" >> $TMPH
elif test "$cpu" = "s390" ; then
  echo "ARCH=s390" >> config.mak
  echo "#define HOST_S390 1" >> $TMPH
elif test "$cpu" = "alpha" ; then
  echo "ARCH=alpha" >> config.mak
  echo "#define HOST_ALPHA 1" >> $TMPH
else
  echo "Unsupported CPU"
  exit 1
fi

and some other interesting stuff, which really looks like support for some arches other than x86..
Can you please comment on that?

George
Comment 2 Luu Danh Hieu 2005-12-25 02:48:13 UTC
Thanks for the marking ~x86 into package.keywords advice :)

And please take your time :) It's not something urgent or anything anyway :)

Oh, and merry christmas ^^ (yes I know it's weird to write this in a bug report .. but .. christmas is here, isn't it ? ^^)

PS : what are the "testing for stable" procedures ? .. I mean, for this package ..
Comment 3 George Shapovalov (RETIRED) gentoo-dev 2006-01-08 08:50:03 UTC
Ok, I got my 32bit chroot up and tested this package. It seems fine and, considering how long it was in the tree, I think it indeed should go stable. However accordingly to the present policy x86 arch team should do this, as lang-misc has no "special" arrangements. Reassigning this bug to them (sorry, I should have done this earlier, but why whoever wrangled this bug did not assign it to arch team anyway?),
x86 team: please stabilize this one!

George
Comment 4 Mark Loeser (RETIRED) gentoo-dev 2006-01-08 13:30:09 UTC
Stable on x86.  The bug should first go to the maintainer so they can tell us if the package should be stable or not, then we'll test it and proceed :)