not as if
gnat-4.9 is about to migrate into testing, even then the new version
would migrate with the constraints met.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgpbnbEwmKcfw.pgp
Description: OpenPGP digital signature
On Sat, 14 Jul 2012 20:12:45 +0200
Matthias Klose wrote:
> On 14.07.2012 20:02, Neil Williams wrote:
> > On Sat, 14 Jul 2012 03:08:09 +0200 Matthias Klose wrote:
> >
> >> please could you find out, which object files (if there are more than
> >> one) do export
() const;
const QList &arguments() const;
template void serialize(Stream &stream) const;
template void deserialize(Stream &stream);
Why is gcc-4.7 overriding the class and optimising away a public symbol
in -O2 when it does not in -O1 or in gcc-4.6 with -O2?
dbg
pn libgomp1-dbg
pn libitm1-dbg
pn libmudflap0-4.7-dev
pn libmudflap0-dbg
pn libquadmath0-dbg
-- no debconf information
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgpjgG0ceHZ4O.pgp
Description: PGP signature
ch gcc-4.6 can pick up as an error or warning in
the qmf sources.
Reinstalling gcc-4.7 & g++-4.7 and rebuilding with the same flags
(and the #include patch) does not indicate any problems with
the qmfclient library itself, g++-4.7 just fails to link the test
binary.
--
Neil Williams
the .la file and the
dependency_libs settings, please raise this on debian-devel for
clarification.
--
Neil Williams
=
http://www.linux.codehelp.co.uk/
pgpWFqMTKvwXH.pgp
Description: PGP signature
moment, I think that this
issue is severe enough that it can't be a release architecture. (Note
that if it is solved, there may be other problems, but we can get to
those later.)
Neil
--
A. Because it breaks the logical sequence of discussion
Q. Why is top posting bad?
gpg key - http://www.hal
On Fri, 20 Aug 2010 13:07:46 +0200
Reinhard Tartler wrote:
> On Fri, Aug 20, 2010 at 11:34:51 (CEST), Neil McGovern wrote:
>
> > On Wed, Aug 18, 2010 at 05:17:32PM +0200, Matthias Klose wrote:
> >> >I'm not sure there are any in the original, plugins and a gre
a the point. These apply for any package, and especially so
for a toolchain.
Given that there doesn't seem to be any compelling reason for gcc4.5 in
squeeze, I'm afraid it's not going to make it for this release.
Apologies,
Neil
--
* hermanr feels like a hedgehog having
On Mon, Aug 16, 2010 at 12:36:34PM +0200, Matthias Klose wrote:
> On 11.08.2010 23:16, Neil McGovern wrote:
> >Hi Matthias,
> >
> >Sorry for not getting back to you sooner.
> >
> >On Sat, Aug 07, 2010 at 11:42:42PM +0200, Matthias Klose wrote:
> >>gcc-4.5
tails as to the (previously mentioned) unit/regression
tests?
Thanks,
Neil
--
* hermanr feels like a hedgehog having sex...
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100811211612.gf7...@halon.org.uk
ut the file into /usr/powerpc-linux-gnu/lib/
Question is, where did this file come from?
I can check the chroot on emdebian.org - I just need to know which one
was used.
Could this be a result of a failed clean up in this chroot?
--
Neil Williams
=
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/
pgpUlzMhpzXK6.pgp
Description: PGP signature
reassign 518754 gcc-4.3
clone 518754 -1
reassign -1 gcc-4.4
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ging tools and that means dpkg and no dpkg-cross, it means apt
and no apt-cross and it means that cross-building needs to adopt and
modify multiarch to the point where we can all use it, albeit with
wrappers and support tools where necessary. Then, we can work on
absorbing those wrappers into the new
/usr/ -- so I
> don't think there is a pressing need to replicate a filesystem hierarchy
> standard below a triplet directory.
True, however, that is not a sufficient reason to not
move /usr/ to /usr/lib/ and /usr/include/
if it means getting such support into the core Debia
usr/arm-linux-gnu/[usr/]lib/libbla.so
> /usr/arm-linux-gnu/[usr/]include/foo.h
>
> or
>
> /lib/arm-linux-gnu/libfoo.so
> /usr/lib/arm-linux-gnu/libbla.so
> /usr/include/arm-linux-gnu/foo.h
>
> It has always been a question of where to put the tripplet, not
> whether or not to have an extra subdir below that. Although I'm
> against the subdirs. No need to duplicate that this is "usr".
I'd agree - [usr] below $arch-linux-gnu appears redundant to me. The
only difference between /lib and /usr/lib/ relates to the libraries
required to boot before /usr is mounted. That reasoning doesn't apply
to toolchain issues.
--
Neil Williams
=
http://www.data-freedom.org/
http://www.linux.codehelp.co.uk/
http://e-mail.is-not-s.ms/
pgpm553xyH46c.pgp
Description: PGP signature
lib/libfoo.so
/usr/include/arm-linux-gnu/usr/include/foo.h
?
I thought the question was whether we would have:
/usr/lib/arm-linux-gnu/lib/libfoo.so
or
/usr/lib/arm-linux-gnu/usr/lib/libfoo.so
or
/usr/arm-linux-gnu/usr/lib/libfoo.so
or the current
/usr/arm-linux-gnu/lib/libfoo.so
as a conversion of /usr/lib/libfoo.so
--
Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/
pgpmAQytPasu5.pgp
Description: PGP signature
Package: gcc-snapshot
Version: 20090224-1
Severity: normal
This issue affects Emdebian Grip in gcc-4.3 but I'm filing it here because Grip
has
a workaround that is OK for 4.3 and I'm trying to fix the problem before 4.4
arrives.
Please let me know if I did that wrong.
The -base postinst script
o be so off-topic. I'm mostly trying to justify my
request for g++-3.4, although if there is a place where I could
legitimately discuss my concerns about Debian testing in general, I'd be
glad if you could point me to it.
--Neil
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: g++-3.4
Version: 3.4.6-6
Severity: important
g++-3.4 has recently disappeared from testing (although gcc-3.4 is still
there). *Please don't do this!* I rely on my Debian testing system for
hosting application development that needs to work on all kinds of other
platforms, many of which d
hat need support from the existing Debian
arm port as well as newer devices that need the new ABI. There is a
possible method for combining the two but both will be needed - and
probably for some time after Lenny. Contact debian-arm for more info.
--
Neil Williams
=
http://ww
Raphael Hertzog wrote:
> On Sun, 09 Dec 2007, Neil Williams wrote:
>>> I'm ok with a
>>> supplementary specific check for building of a cross-compiler, but not
>>> with a generic check like testing the ARCH environment variable.
>> OK, I have a solution
Raphael Hertzog wrote:
> On Sun, 09 Dec 2007, Neil Williams wrote:
>> Emdebian cannot build, patch or test every permutation of toolchain that
>> people need so this isn't about "us" patching locally, it is about
>> lowering the barrier to cross building on De
Guillem Jover wrote:
> Hi,
>
> [ I don't have a real opinion yet on the initial patch and this
> changes proposed, will try to get to this on Sunday. ]
OK, thanks, Guillem. I'd like to get this resolved asap.
> On Sat, 2007-12-08 at 19:01:14 +, Neil Williams
Raphael Hertzog wrote:
> On Wed, 05 Dec 2007, Neil Williams wrote:
>> My first patch did exactly that - and failed on building a cross
>> compiler. gcc needs dpkg-shlibdeps to take notice of $ARCH in the
>> preparation of libgcc1-$arch-cross and other libraries used in the
Package: gcc-4.2
Version: 4.2.2-3
Severity: wishlist
gcc has a complex debian build layout and it isn't straightforward to
disable the generation of the various -doc packages when preparing test
builds or (in my case) cross builds. It would save a lot of build time
and upload time if gcc could sup
ption for the others.
When building Emdebian toolchains, we install libgcc1 (amongst others)
using apt-cross, then build binutils and gcc, then install in one
operation.
Try checking the source code of emchain from emdebian-tools.
--
Neil Williams
=
http://www.data-freedom.
upstream comment on how to fix it.
>
On a more general note, I'd like to see xulrunner/nss built and
depending packages[0] built so we can get the fixes into testing easier
before this is started.
Cheers,
Neil
[0] Most of: http://security-tracker.debian.net/tracker/status/dtsa-candidates
--
i
cvs20070426) | 2.17cvs20070426-8
libgcc1 (>= 1:4.2-20070627-1) | 1:4.2-20070627-1
libgomp1 (>= 4.2-20070627-1) | 4.2-20070627-1
libc6 (>= 2.5-5) | 2.5-11
--
Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.c
--- Comment #1 from neil at gcc dot gnu dot org 2006-10-14 12:25 ---
Not a bug - just 2 elements are initialized, the NUL is dropped.
--
neil at gcc dot gnu dot org changed:
What|Removed |Added
Get the Finest Rolex Watch Replica !
We only sell premium watches. There's no battery in these replicas
just like the real ones since they charge themselves as you move.
The second hand moves JUST like the real ones, too.
These original watches sell in stores for thousands of dollars.
We sel
--- Additional Comments From neil at gcc dot gnu dot org 2004-02-04 10:26
---
Nothing to do with CPP.
--
What|Removed |Added
Component|preprocessor
--
What|Removed |Added
Component|preprocessor|c
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9071
--- You are receiving this mail because: ---
You r
PLEASE REPLY TO [EMAIL PROTECTED] ONLY, *NOT* [EMAIL PROTECTED]
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11459
--- Additional Comments From neil at daikokuya dot co dot uk 2003-07-09
05:45 ---
Subject: Re: -stdc=c90 -pedantic -ansi warns about C90's non long-long support
wh
which part of
the C standard is violated. You got an address, why are you unhappy?
Neil.
> #define TA char
> #define TB int
> #define TC int
>
> void foobar(TA a, TB b, TC c);
>
> int main()
> {
> foobar(1,2,3);
> return 0;
> }
>
> void foobar(
Synopsis: _Pragma within macros is improperly expanded
State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Mon Nov 18 12:51:59 2002
State-Changed-Why:
Fixed, I hope. Applied in 3.3, will soon apply in 3.2.2.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20au
Neil Booth wrote:-
> I think this fixes it for good. I'm applying this to 3.3, and 3.2.2
> when it arrives.
>
> Neil.
>
> PR preprocessor/8524
> * cpplib.c (run_directive): Remove previous kludge to _Pragma.
> Add a new one in its
I think this fixes it for good. I'm applying this to 3.3, and 3.2.2
when it arrives.
Neil.
PR preprocessor/8524
* cpplib.c (run_directive): Remove previous kludge to _Pragma.
Add a new one in its place, which hopefully works.
(skip_rest_of_line): Change tes
Synopsis: _Pragma within macros is improperly expanded
State-Changed-From-To: analyzed->open
State-Changed-By: neil
State-Changed-When: Sun Nov 17 14:07:28 2002
State-Changed-Why:
Patch in progress. Let's nail this for good. Other than a rewrite the
only possible fix is a kludge,
Synopsis: incorrect line numbers in warning messages when using inline functions
State-Changed-From-To: open->analyzed
State-Changed-By: neil
State-Changed-When: Sat Nov 16 03:23:59 2002
State-Changed-Why:
Confirmed. Change category to C as it clearly has nothing to do with
preproces
Synopsis: _Pragma within macros is improperly expanded
Responsible-Changed-From-To: unassigned->neil
Responsible-Changed-By: neil
Responsible-Changed-When: Sun Nov 10 22:44:07 2002
Responsible-Changed-Why:
Mine.
State-Changed-From-To: open->analyzed
State-Changed-By: neil
State-Change
I've a nasty feeling the fix I gave doesn't work in all cases anyway;
a proper fix might have to wait for 3.4.
Neil.
> # 1 ""
> # 1 "foo.c"
>
> # 1 "foo.c"
> #pragma foo
> # 1 "foo.c"
> ; int y;
>
>
> # 3 "foo.c"
> #pragma ; int x;foo
>
> > The first line is expanded correctly; the third is not (rendering
> &
> # 1 ""
> # 1 "foo.c"
>
> # 1 "foo.c"
> #pragma foo
> # 1 "foo.c"
> ; int y;
>
>
> # 3 "foo.c"
> #pragma ; int x;foo
>
> > The first line is expanded correctly; the third is not (rendering
> > _Pragma almost completely useless).
>
> Do you have time to look into this, Neil?
I'll try to have a look this weekend.
Neil.
Martin v. Loewis wrote:-
> Neil Booth <[EMAIL PROTECTED]> writes:
>
> > If it's a system header, why are you lying to the compiler?
>
> I'm not lying, I use
You've not told the compiler it's a system header, so it doesn't think
it is. Let me see what Zack thinks.
Neil.
Martin,
If it's a system header, why are you lying to the compiler?
Maybe a real-life example and not "a.h" would help.
Neil.
gt; brackets? Why is #include "foo.h" not good enough?
Neil.
Synopsis: gcc 3.0 0526 fails to build on mips
State-Changed-From-To: open->closed
State-Changed-By: neil
State-Changed-When: Wed Jun 6 05:32:48 2001
State-Changed-Why:
I believe this has been fixed; we have since had successful
builds, e.g.
http://gcc.gnu.org/ml/gcc-testresu
we accept //. I'm tempted to leave it as it is,
but we can turn of the warning if you think it's inappropriate.
Neil.
49 matches
Mail list logo
