spoke again to TL and asked if pine64 would be willing to look at
sponsorship witn rockpro64 boards (the ones that take 4x PCIe): if
someone from debian were to contact him direct he would happily
consider it.
i then asked him if i could cc him into this discussion and he said he
was way *way* too
On Fri, Jun 29, 2018 at 8:13 PM, Luke Kenneth Casson Leighton
wrote:
> On Fri, Jun 29, 2018 at 6:59 PM, Jonathan Wiltshire wrote:
>
>>> also worth noting, they're working on a 2U rackmount server which
>>> will have i think something insane like 48 Rock64Pro board
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, Jun 29, 2018 at 8:31 PM, Florian Weimer wrote:
> * Luke Kenneth Casson Leighton:
>
>> that is not a surprise to hear: the massive thrashing caused by the
>> linker phase not being possible
On Fri, Jun 29, 2018 at 6:59 PM, Jonathan Wiltshire wrote:
>> also worth noting, they're working on a 2U rackmount server which
>> will have i think something insane like 48 Rock64Pro boards in one
>> full-length case.
> None of this addresses the basic DSA requirement of remote management.
> T
On Fri, Jun 29, 2018 at 5:21 PM, Steve McIntyre wrote:
>>2G is also way too little memory these days for a new buildd.
>
> Nod - lots of packages are just too big for that now.
apologies for repeating it again: this is why i'm recommending people
try "-Wl,--no-keep-memory" on the linker phase a
On Fri, Jun 29, 2018 at 12:50 PM, Julien Cristau wrote:
> Everyone, please avoid followups to debian-po...@lists.debian.org.
> Unless something is relevant to *all* architectures (hint: discussion of
> riscv or arm issues don't qualify), keep replies to the appropriate
> port-specific mailing lis
On Fri, Jun 29, 2018 at 12:06 PM, John Paul Adrian Glaubitz
wrote:
> On 06/29/2018 10:41 AM, Luke Kenneth Casson Leighton wrote:
>> On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König
>> wrote:
>>
>>>> In short, the hardware (development boards) we're current
On Fri, Jun 29, 2018 at 12:23 PM, Adam D. Barratt
wrote:
>> i don't know: i'm an outsider who doesn't have the information in
>> short-term memory, which is why i cc'd the debian-riscv team as they
>> have current facts and knowledge foremost in their minds. which is
>> why i included them.
>
>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Fri, Jun 29, 2018 at 10:35 AM, Adam D. Barratt
wrote:
>> what is the reason why that package is not moving forward?
>
> I assume you're referring to the dpkg upload that's in proposed-updates
> waiting for the point
On Wed, Jun 27, 2018 at 9:03 PM, Niels Thykier wrote:
> armel/armhf:
>
>
> * Undesirable to keep the hardware running beyond 2020. armhf VM
>support uncertain. (DSA)
>- Source: [DSA Sprint report]
[other affected 32-bit architectures removed but still relevant]
... i'm
On Fri, Jun 29, 2018 at 8:16 AM, Uwe Kleine-König
wrote:
> Hello,
>
> On Wed, Jun 27, 2018 at 08:03:00PM +, Niels Thykier wrote:
>> armel/armhf:
>>
>>
>> * Undesirable to keep the hardware running beyond 2020. armhf VM
>>support uncertain. (DSA)
>>- Source: [DSA Sprint
On Sat, Feb 25, 2012 at 2:04 PM, Rene Engelhard wrote:
> Hi,
>
> On Sat, Feb 25, 2012 at 01:49:02PM +0000, Luke Kenneth Casson Leighton wrote:
>> it's even more hilarious than that: it's actually because java can't
>> access windows registry functions, so
On Fri, Feb 3, 2012 at 5:48 AM, Stephen Kitt wrote:
> Hi Peter,
>
> On Fri, Feb 03, 2012 at 02:36:17AM +, peter green wrote:
>> Libreoffice hasn't yet been built on armhf. I consider libreoffice
>> to be a reasonablly important package and one that we need to get in
>> before we can claim we h
Networks PSWiiXbox Pussycat DollsFree
http://img444.imageshack.us/img444/5944/bxqh6.gif
known Advantage initiative
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
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
On Thu, Jan 06, 2005 at 07:31:59PM +0100, Falk Hueffner wrote:
> Luke Kenneth Casson Leighton <[EMAIL PROTECTED]>, [EMAIL PROTECTED] schrieb
> am 06.01.05 19:10:48:
>
> > math ops - >> and & - cannot be performed with constants > 32-bit!
>
> I don
Package: gcc-3.3
Version: 1:3.3.4-11
Severity: normal
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux highfield 2.6.9-1-686 #1 Thu Nov 25 03:48:29 EST 2004 i686
Locale: LANG=C, LC_CTYPE=C
math ops - >> and & - cannot be performed with constants > 32-bit
falk, hi,
On Wed, Jan 05, 2005 at 03:30:25PM +0100, Falk Hueffner wrote:
> Hi,
>
> can you still reproduce this problem with the current gcc-4.0 package?
> If so, please provide the preprocessed source file.
shriek - that's with --enable-final so is the contents of every single
file in the di
../../../khtml/ecma/kjs_html.cpp:1237: error: Non-addressable variable
inside an alias set.
.GLOBAL_VAR, UID 3058, is an alias tag, is static, call clobbered,
default def: .GLOBAL_VAR_45
TMT.34829, UID 3040, is an alias tag, is global, call clobbered, default
def: TMT.34829_617, may aliases: { .GLO
Package: gcc-3.5
Version: 3.5-0pre1
Severity: normal
i get the following error on gcc 3.5. i am reluctant to include
a "full" report because the stupid kde build process is to stack
all source code .cpp files end-to-end and whack them through gcc.
result? in some cases a 12mbyte .s file in /tm
Package: libstdc++5
Version: 1:3.3.3-8
Severity: normal
i don't know how it happened and i have not been modifying anything
other than by doing regular apt-get installs of packages.
somehow i end up with a link from libstdc++.so to .5.0.0 instead
of .5.0.6 and yet /usr/lib/libstdc++.5.0.0 does n
at is not a bug so closing as invalid.
Great. If I knew anything about JNI, I guess that would have been
obvious.
I will close this bug myself in another message.
Thanks,
KEN
--
Kenneth J. Pronovici <[EMAIL PROTECTED]>
Personal Homepage: http://www.skyjammer.com/~pronovic/
"They
t in this case, but at least a location, where the sources
> can be fetched without debian specific tools.
>
> - the flags used to compile
>
> - the testcase, which fails.
Understood. I'll try to come up with a more minimal test case and
attach it to the upstream bug.
Thanks for your time,
KEN
--
Kenneth J. Pronovici <[EMAIL PROTECTED]>
pgpO70tStJlI6.pgp
Description: PGP signature
e time trying to reduce
that to as small of an example as I can.
Incidentally, at this point, I'm not sure whether this is a compiler bug
or an interpreter bug. I'm leaning toward it being an interpreter bug,
since Kaffe seems to be able to run the test code with no problems even
whe
re not the same
package).
So, as I said in my first email, I'd be happy to do additional research
if someone can let me know what they need. In the meantime, I've added
some comments in the GCC bugzilla report and I guess I'll manage it
myself from this point forward.
Thanks,
KEN
--
Kenneth J. Pronovici <[EMAIL PROTECTED]>
pgptKbbESzgCn.pgp
Description: PGP signature
ppy to do additional research
if you can let me know what you and/or the GCC developers need from me
over and above the test case I provided with the original bug report.
KEN
--
Kenneth J. Pronovici <[EMAIL PROTECTED]>
pgpddSg2qUj64.pgp
Description: PGP signature
On Wed, May 21, 2003 at 11:47:14AM +0200, Gregor Hoffleit wrote:
> Indeed, on all machines I checked, /lib was not in /etc/ld.so.conf (nor
> was /usr/lib on most machines).
>
> So the real cause for your trouble, Luke, appearently is the presence of
> that libgcc1_so file in /usr/lib. AFAICS, add
On Wed, May 21, 2003 at 11:49:33AM +0200, Gregor Hoffleit wrote:
> * Joel Baker <[EMAIL PROTECTED]> [030521 09:08]:
> > If it isn't finding things in /lib by default, someone has a rather serious
> > bug on their hands. Check the version of ldconfig and kin?
>
> AFAICS, the problem is not that t
On Tue, May 20, 2003 at 11:05:17PM +0200, Matthias Klose wrote:
> - add /lib to /etc/ld.so.conf before /usr/lib
> - install the new libgcc1
> - then upgrade other packages.
>
> It seems to be a local problem with your installation, else we had
> more than one bug report ... I'm downgrading the rep
On Tue, May 20, 2003 at 11:59:25AM +0200, Gregor Hoffleit wrote:
> * Luke Kenneth Casson Leighton <[EMAIL PROTECTED]> [030519 18:39]:
> > On Mon, May 19, 2003 at 10:16:50AM -0500, Skip Montanaro wrote:
> > >
> > > Luke> gcc 3.3 is now the latest for unst
of broken programs that have exactly this dependency
problem.
python2.2, update-menus were only two that i noticed and started to
freak out over.
> Luke Kenneth Casson Leighton writes:
> > Package: libgcc1
> > Version: 1:3.2.3-0pre6
> > Severity: critical
> &g
tracked down more information on this problem:
installation of gcc 3.3 causes installation of libstdc++5 causes
libgcc1 to fail for all programs linked with gcc 3.2.
that means that i cannot use reportbug without downgrading back
to gcc 3.2 which i cannot easily do because i now have packages
on
Package: libgcc1
Version: 1:3.2.3-0pre6
Severity: critical
actions taken:
apt-get remove jade
this required, at this time, the installation / upgrade of libgcc1
and the installation / upgrade of tetex.
gcc 3.3 and cpp 3.3 was NOT required as part of that installation / upgrade.
once ac
On Sat, Dec 07, 2002 at 10:56:57AM +0100, Matthias Klose wrote:
> Kenneth Pronovici writes:
> > Please let me know if there is any other information I can get you.
> > I'd be happy to help in any way that I can.
>
> you may want to recheck with gij from the gcc-snaps
Package: gij-3.2
Version: 1:3.2.2-0pre0
Severity: normal
Tags: sid
In converting the libnbio2-java package to build with all free tools, I
have discovered that gij is not able to run some programs that are part
of the NBIO test suite, although other interepreters such as Kaffe can.
There was a lo
correct if the FPU was set to
64 bit mode, so whether the bug is in the GCC back end or the GNAT
front end would seem to depend on whether the back end optimizations
are justified in assuming that the FPU is in 64 bit mode.
Kenneth Almquist
Hi all.
Im trying to build 2.4.19 with the command:
make-kpkg --initrd kernel_image
It fails after running through the whole process with error message that
follows.
what i do:
1. download source from mirror and extract it in /usr/local/src/
2. copy the config-2.4.18-686 from boot and give it
37 matches
Mail list logo
