Aurelien Jarno a écrit :
> Martin Michlmayr a écrit :
>> * Martin Michlmayr <[EMAIL PROTECTED]> [2007-05-22 12:58]:
>>> sed -n '/^baseline_dir *=/s,.*= *\(.*\)\$.*$,\1,p' Makefile
>>> /home/tbm/build/42/3/gcc-4.2-4.2-20070516/src/libstdc++-v3/config/abi/post/
>>>
>>> Any idea what to do about this?
* Aurelien Jarno <[EMAIL PROTECTED]> [2007-05-23 06:24]:
> Martin has tested the same kind of change on arm, I have tested it on
For the record, my build was successful.
--
Martin Michlmayr
http://www.cyrius.com/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Tr
Martin Michlmayr a écrit :
> * Martin Michlmayr <[EMAIL PROTECTED]> [2007-05-22 12:58]:
>> sed -n '/^baseline_dir *=/s,.*= *\(.*\)\$.*$,\1,p' Makefile
>> /home/tbm/build/42/3/gcc-4.2-4.2-20070516/src/libstdc++-v3/config/abi/post/
>>
>> Any idea what to do about this? Giving that there's no "arm" d
Martin Michlmayr a écrit :
> * Martin Michlmayr <[EMAIL PROTECTED]> [2007-05-22 12:58]:
>> sed -n '/^baseline_dir *=/s,.*= *\(.*\)\$.*$,\1,p' Makefile
>> /home/tbm/build/42/3/gcc-4.2-4.2-20070516/src/libstdc++-v3/config/abi/post/
>>
>> Any idea what to do about this? Giving that there's no "arm" d
* Martin Michlmayr <[EMAIL PROTECTED]> [2007-05-22 12:58]:
> sed -n '/^baseline_dir *=/s,.*= *\(.*\)\$.*$,\1,p' Makefile
> /home/tbm/build/42/3/gcc-4.2-4.2-20070516/src/libstdc++-v3/config/abi/post/
>
> Any idea what to do about this? Giving that there's no "arm" directory, I
> suppose simply rep
* Martin Michlmayr <[EMAIL PROTECTED]> [2007-05-21 08:55]:
> Are you sure? I just tried to build gcc-4.2 and I certainly need this
> patch. arm-libffi is applied which contains 'ffi_prep_closure' which
> leads to a conflict, as with 4.1.
After applying this patch, I get another build failure bui
Martin Michlmayr a écrit :
> * Aurelien Jarno <[EMAIL PROTECTED]> [2007-05-19 01:24]:
>> I have just given a quick look to gcc-4.2. As it does not uses
>> libjava-backport-updates2.dpatch, the problem is probably not present in
>> this version. Also I can't find any occurence of ffi_prep_closure_lo
* Aurelien Jarno <[EMAIL PROTECTED]> [2007-05-19 01:24]:
> I have just given a quick look to gcc-4.2. As it does not uses
> libjava-backport-updates2.dpatch, the problem is probably not present in
> this version. Also I can't find any occurence of ffi_prep_closure_loc
Are you sure? I just tried t
On Sat, May 19, 2007 at 12:22:02AM +0200, Aurelien Jarno wrote:
> On Fri, May 18, 2007 at 06:01:03PM +0200, Aurelien Jarno wrote:
> > Matthias Klose a écrit :
> > > Peter Green writes:
> > >> package:gcc-4.1
> > >> version:4.1.2-7
> > >> severity:serious
> > >>
> > >> from the relavent buildd logs:
On Fri, May 18, 2007 at 06:01:03PM +0200, Aurelien Jarno wrote:
> Matthias Klose a écrit :
> > Peter Green writes:
> >> package:gcc-4.1
> >> version:4.1.2-7
> >> severity:serious
> >>
> >> from the relavent buildd logs:
> >
> > Note, that the severity is not RC for 68k; I do not intend to fix
> >
Sorry...my error.
--George
On Friday 18 May 2007 03:40 pm, peter green wrote:
> > This type of message does not give me a warm and fuzzy feeling
> > that makes me
> > want to work on the Debian arm port.
>
> I'd just like to point out that you are addressing your critisism at the
> wrong person.
> This type of message does not give me a warm and fuzzy feeling
> that makes me
> want to work on the Debian arm port.
I'd just like to point out that you are addressing your critisism at the wrong
person. your reply seems to be directed at a message from a person replying to
me not to me.
Hello Peter,
This type of message does not give me a warm and fuzzy feeling that makes me
want to work on the Debian arm port.
Please think about, being considerate, being respectful and being
collaborative.
--George
On Friday 18 May 2007 09:48 am, Matthias Klose wrote:
> Peter Green write
Matthias Klose a écrit :
> Peter Green writes:
>> package:gcc-4.1
>> version:4.1.2-7
>> severity:serious
>>
>> from the relavent buildd logs:
>
> Note, that the severity is not RC for 68k; I do not intend to fix
> that. Same for arm, and arm porters don't seem to care that much, so
> maybe we sho
Matthias Klose a écrit :
> that. Same for arm, and arm porters don't seem to care that much, so
> maybe we should drop arm as a release architecture?
>
What make you think that? The build failure is known for less than 3
days, please let us time to fix that.
--
.''`. Aurelien Jarno
Riku Voipio writes:
> On Fri, May 18, 2007 at 03:48:00PM +0200, Matthias Klose wrote:
> > Peter Green writes:
> > > package:gcc-4.1
> > > version:4.1.2-7
> > > severity:serious
>
> > > from the relavent buildd logs:
>
> > Note, that the severity is not RC for 68k; I do not intend to fix
> > that.
On Fri, May 18, 2007 at 03:48:00PM +0200, Matthias Klose wrote:
> Peter Green writes:
> > package:gcc-4.1
> > version:4.1.2-7
> > severity:serious
> > from the relavent buildd logs:
> Note, that the severity is not RC for 68k; I do not intend to fix
> that. Same for arm
Is building libffi.so.4
package:gcc-4.1
version:4.1.2-7
severity:serious
from the relavent buildd logs:
/bin/sh ./libtool --mode=link /build/buildd/gcc-4.1-4.1.2/build/./gcc/xgcc
-B/build/buildd/gcc-4.1-4.1.2/build/./gcc/ -B/usr/arm-linux-gnu/bin/
-B/usr/arm-linux-gnu/lib/ -isystem /usr/arm-linux-gnu/include -isystem
/u
Peter Green writes:
> package:gcc-4.1
> version:4.1.2-7
> severity:serious
>
> from the relavent buildd logs:
Note, that the severity is not RC for 68k; I do not intend to fix
that. Same for arm, and arm porters don't seem to care that much, so
maybe we should drop arm as a release architecture?
19 matches
Mail list logo
