Gentoo Archives: gentoo-dev

From: Arfrever Frehtes Taifersar Arahesis <Arfrever@g.o>
To: Gentoo Development <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild
Date: Sun, 20 Jun 2010 13:57:16
Message-Id: 201006201556.14340.Arfrever@gentoo.org
In Reply to: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in dev-python/traits: traits-3.4.0.ebuild by Mike Frysinger
2010-06-19 22:53:37 Mike Frysinger napisał(a):
> On Thursday, June 10, 2010 16:45:29 Arfrever Frehtes Taifersar Arahesis wrote: > > 2010-06-10 22:20:44 Nirbheek Chauhan napisał(a): > > > On Fri, Jun 11, 2010 at 1:30 AM, Arfrever Frehtes Taifersar wrote: > > > > 2010-06-10 21:27:40 Jeremy Olexa napisał(a): > > > >> I see no reason to *not* add a ChangeLog entry here. > > > > > > > > ChangeLog entries are not required for trivial changes. > > > > > > A "trivial" change is fixing a typo, or a manifest problem, a missing > > > quotation mark, etc. Anything else is not "trivial". > > > > > > Anything that changes how an ebuild functions, what it does, or the > > > installed files (and/or their contents) is NOT a trivial change. > > > > This commit only removed some compiler warnings. > > mucking with CFLAGS without documentation is wrong. compiler warnings come > and go, so a flag that was relevant one day could be completely extraneous the > next. > > however, especially with strict aliasing, you arent "just fixing warnings", > you're changing optimization behavior of gcc to workaround broken C code. > this obviously does not fall anywhere near the "trivial" mark. > > i see you still havent fixed this, so get on it already. a bug needs to be > opened somewhere to get the package properly *fixed*
This problem is probably caused by bugs in Python 2, which have been fixed in Python 3. $ echo 'a = True' > test.pyx $ cython test.pyx $ gcc -O2 -Wall -I/usr/include/python3.1 -c test.c $ gcc -O2 -Wall -I/usr/include/python2.6 -c test.c test.c: In function ‘inittest’: test.c:479: warning: dereferencing type-punned pointer will break strict-aliasing rules test.c:479: warning: dereferencing type-punned pointer will break strict-aliasing rules test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break strict-aliasing rules test.c:479: warning: dereferencing pointer ‘_Py_TrueStruct.42’ does break strict-aliasing rules test.c:479: note: initialized from here test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:482: warning: dereferencing pointer ‘__pyx_t_1’ does break strict-aliasing rules test.c:479: note: initialized from here -- Arfrever Frehtes Taifersar Arahesis

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies