I noticed something disturbing (to me) with a recent upgrade of wheezy:
for some reason that I do not quite understand, when today I fired up
synaptic on some wheezy machines I administer, updated the list of packages
and clicked on select updates and then apply, not only it updated
libgpgme11
I set PCIe 3.0 permanently.
With a system of 150K atoms there is no acceleration at all of molecular
dynamics with ivy with respect to sandy bridge.
At the end of this exercise, given the very meager acceleration with 500K
atoms (which is a large system under any respect, even for
.
francesco pietra
-- Forwarded message --
From: Francesco Pietra chiendar...@gmail.com
Date: Sun, Nov 17, 2013 at 4:09 PM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian debian-amd64@lists.debian.org, Lennart Sorensen
lsore...@csclub.uwaterloo.ca
Em 18-11-2013 13:13, Francesco Pietra escreveu:
It is getting hard, unless I mistaken what was suggested by nvidia .
Thus, following what was suggested by nvidia as a no-barrier solution,
Em 18-11-2013 13:13, Francesco Pietra escreveu:
It is getting hard, unless I mistaken what was suggested by nvidia .
Thus, following what was suggested by nvidia as a no-barrier solution,
On Sun, Nov 17, 2013 at 10:45:58AM +0100, Francesco Pietra wrote:
I am attacking the problem from another side, directly from within the OS
itself:
#lspi -
tells that the link speed (= link status) LnkSta is at 5Gb/s, no matter
whether the system is at number crunching or not. I.e.,
Might need nvidia-current instead of nvidia.
It failed to bring to PCIe 3.0 when inserted into nvidia.conf
francesco@gig64:/etc/modprobe.d$ cat nvidia.conf
alias nvidia nvidia-current
remove nvidia-current rmmod nvidia
# 1. options nvidia-current NVreg_EnablePCIeGen3=1
(of course it was not
I forgot to mention that LnkSta 8GT/s is obtained only when actually
carrying out the MD simulation.
fp
-- Forwarded message --
From: Francesco Pietra chiendar...@gmail.com
Date: Mon, Nov 18, 2013 at 10:37 PM
Subject: Re: Fwd: upgrade to jessie from wheezy with cuda problems
On Mon, Nov 18, 2013 at 10:39:53PM +0100, Francesco Pietra wrote:
I forgot to mention that LnkSta 8GT/s is obtained only when actually
carrying out the MD simulation.
I believe to save power the link speed changes on the fly based on demand.
--
Len Sorensen
--
To UNSUBSCRIBE, email to
I am attacking the problem from another side, directly from within the OS
itself:
#lspi -
tells that the link speed (= link status) LnkSta is at 5Gb/s, no matter
whether the system is at number crunching or not. I.e., my system is at
PCIe 2.0. This might explain why upgrading from sandy
...@gmail.com
Date: Tue, Nov 12, 2013 at 3:54 PM
Subject: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian debian-amd64@lists.debian.org
Hello:
I decided to try jessie to get PCIe 3.0 with a recent nvidia driver, thus
upgrading from wheezy.
wheezy was
uname -r
3.2.0-4-amd64
nvidia
and LnkSta are 5GT/s, as from PCIe
2.0.
Thus, the problem seems to be activating PCIe 3.0, as before said.
francesco pietra
-- Forwarded message --
From: Francesco Pietra chiendar...@gmail.com
Date: Sun, Nov 17, 2013 at 11:29 AM
Subject: Fwd: upgrade to jessie from wheezy
, 2013 at 11:42 AM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian debian-amd64@lists.debian.org, Lennart Sorensen
lsore...@csclub.uwaterloo.ca
Very sorry, forget about previous post. There, I had started MD from the
gnome terminal, without activating the GPUUs
entered the scene while
updating/upgrading from a clean wheezy.
The bad news are that with the new driver 319.60 there was no
acceleration
of molecular dynamics for a job of modest size (150K atoms) and slight
acceleration (0.12 s/step vs 0.14 s/step) for a heavy job (500K atoms
...@csclub.uwaterloo.ca wrote:
On Tue, Nov 12, 2013 at 10:35:53PM +0100, Francesco Pietra wrote:
# apt-get --purge remove *legacy*
did the job.
I wonder how these legacy packages entered the scene while
updating/upgrading from a clean wheezy.
The bad news are that with the new driver 319.60
On Wed, Nov 13, 2013 at 10:13:15AM +0100, Francesco Pietra wrote:
I think it was renamed. No idea why. modinfo nvidia-current should
work though.
Yes, it does.
Do you have the cuda libraries for the 319 version installed?
Yes
I don't play around with GPU computations, but
On Wed, Nov 13, 2013 at 10:32:26AM +0100, Francesco Pietra wrote:
My answer seems to have disappeared. I summarize here.
modinfo nvidia-curred works well. CUDA libraries are installed.
For nvidia-cuda-toolkit, nvidia offers SDK packages for Ubuntu, not for
Debian. I don't like to get into
francesco@gig64:~/tmp$
-- Forwarded message --
From: Francesco Pietra chiendar...@gmail.com
Date: Wed, Nov 13, 2013 at 10:32 AM
Subject: Re: upgrade to jessie from wheezy with cuda problems
To: Lennart Sorensen lsore...@csclub.uwaterloo.ca
Cc: amd64 Debian debian-amd64
the bandwidth.
thanks
francesco pietra
-- Forwarded message --
From: Francesco Pietra chiendar...@gmail.com
Date: Wed, Nov 13, 2013 at 7:40 PM
Subject: Fwd: upgrade to jessie from wheezy with cuda problems
To: amd64 Debian debian-amd64@lists.debian.org
francesco@gig64:~/tmp$ export
On Wed, Nov 13, 2013 at 07:40:10PM +0100, Francesco Pietra wrote:
francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
That is unnecesary. That is already in the library path. The local
directory is not. Windows implicitly looks in the current directory
for files, linux
Em 13-11-2013 16:40, Francesco Pietra escreveu:
francesco@gig64:~/tmp$ export LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/
francesco@gig64:~/tmp$ ./CUDA-Z-0.7.189.run
CUDA-Z 0.7.189 Container
Starting CUDA-Z...
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z: error while
loading shared
francesco@gig64:~$ file
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z
/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z: ERROR: cannot open
`/home/francesco/tmp/CUDA-Z-95b0-7943-3edd-827e/cuda-z' (No such file or
directory)
francesco@gig64:~$
On Wed, Nov 13, 2013 at 8:18 PM, Fabricio
What does 'file ./CUDA-Z-0.7.189.run' say?
francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
./CUDA-Z-0.7.189.run: data
francesco@gig64:~/tmp$
On Wed, Nov 13, 2013 at 7:52 PM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
On Wed, Nov 13, 2013 at 07:40:10PM +0100, Francesco Pietra
On Wed, Nov 13, 2013 at 10:53:30PM +0100, Francesco Pietra wrote:
francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
./CUDA-Z-0.7.189.run: data
francesco@gig64:~/tmp$
OK that's weird. I expected to see x86 32 or 64bit binary.
Seems to be a shell scripts with compressed code in it. Yuck. :)
On Wed, Nov 13, 2013 at 05:43:47PM -0500, Lennart Sorensen wrote:
On Wed, Nov 13, 2013 at 10:53:30PM +0100, Francesco Pietra wrote:
francesco@gig64:~/tmp$ file ./CUDA-Z-0.7.189.run
./CUDA-Z-0.7.189.run: data
francesco@gig64:~/tmp$
OK that's weird. I expected to see x86 32 or 64bit
Hello:
I decided to try jessie to get PCIe 3.0 with a recent nvidia driver, thus
upgrading from wheezy.
wheezy was
uname -r
3.2.0-4-amd64
nvidia-smi
304.88
nvcc --version
4.2
(the latter is also the version at which the molecular dynamics code was
compiled, and used without calling the X
On Tue, Nov 12, 2013 at 03:54:32PM +0100, Francesco Pietra wrote:
Hello:
I decided to try jessie to get PCIe 3.0 with a recent nvidia driver, thus
upgrading from wheezy.
wheezy was
uname -r
3.2.0-4-amd64
nvidia-smi
304.88
nvcc --version
4.2
(the latter is also the version
On Tue, Nov 12, 2013 at 05:22:18PM +0100, Francesco Pietra wrote:
Yes. Also,
# apt-get remove nvidia-kernel-dkms
# apt-get install nvidia-kernel-dkms
(which, in the year 2011, served to clear the driver at
/lib/modules/2.6.38-2-amd64/updates/dkms. But now the kernel was 3.2.) left
the
# apt-get --purge remove *legacy*
did the job.
I wonder how these legacy packages entered the scene while
updating/upgrading from a clean wheezy.
The bad news are that with the new driver 319.60 there was no acceleration
of molecular dynamics for a job of modest size (150K atoms) and slight
On Tue, Nov 12, 2013 at 10:35:53PM +0100, Francesco Pietra wrote:
# apt-get --purge remove *legacy*
did the job.
I wonder how these legacy packages entered the scene while
updating/upgrading from a clean wheezy.
The bad news are that with the new driver 319.60 there was no acceleration
On 08/16/2013 06:18 AM, Karl Schmidt wrote:
Back in 2011-sep-29 There was a problem booting from a raid partition
with raid mdam metadata version 1.2. There was a workaround - but I'm
trying to update some documentation for wheezy.
It looks like this has not been dealt with?
At issue
Back in 2011-sep-29 There was a problem booting from a raid partition with raid mdam metadata
version 1.2. There was a workaround - but I'm trying to update some documentation for wheezy.
It looks like this has not been dealt with?
At issue is working with modern drives that are now larger
here.
I am facing lot of problems in installing wheezy.
1) I downloaded the dvd-1 image of amd-64 precisely
debian-7.1.0-amd64-DVD-1 for installing wheezy. I checked the md5sum of my
downloaded file and it was the same as of the original. So the image was
verified.
Being a hybrid image, I just
Hello everyone, this is my first post here.
I am facing lot of problems in installing wheezy.
1) I downloaded the dvd-1 image of amd-64 precisely
debian-7.1.0-amd64-DVD-1 for installing wheezy. I checked the md5sum of my
downloaded file and it was the same as of the original. So the image
lot of problems in installing wheezy.
1) I downloaded the dvd-1 image of amd-64 precisely
debian-7.1.0-amd64-DVD-1 for installing wheezy. I checked the md5sum of my
downloaded file and it was the same as of the original. So the image was
verified.
Being a hybrid image, I just ran the following
to install it.
-Ivan
On Sun, Aug 11, 2013 at 12:53 AM, Anubhav Yadav anubhav1...@gmail.comwrote:
Hello everyone, this is my first post here.
I am facing lot of problems in installing wheezy.
1) I downloaded the dvd-1 image of amd-64 precisely
debian-7.1.0-amd64-DVD-1 for installing wheezy. I
On Mon, Jun 03, 2013 at 02:32:39PM -0500, Karl Schmidt wrote:
This is serious - I sure hope you wrote up a bug report?
I first wanted to make sure that the serious error isn't on my side.
Up to now I seem to be the only one affected...
S
--
To UNSUBSCRIBE, email to
After installing Wheezy (using FAI, so the setup is essentially unaltered),
one of my machines doesn't report memory errors via mcelog anymore. Error
messages go to syslog instead:
Jun 3 09:47:07 testbed kernel: [231899.816038] [Hardware Error]: CPU:0
MC0_STATUS[Over|CE|-|-|AddrV|CECC
This is serious - I sure hope you wrote up a bug report?
Karl Schmidt EMail k...@xtronics.com
Transtronics, Inc. WEB
http://secure.transtronics.com
Émeric == Émeric Maschino emeric.masch...@gmail.com writes:
Émeric Just to let you know that I've successfully installed Wheezy
Émeric using the netinst CD on a spare HDD, using default parameters
Émeric (using entire HDD and one single partition as partition
Émeric scheme) except
Hi,
Sorry for the late reply, I didn't have access to my zx6000 workstation
until now.
Just to let you know that I've successfully installed Wheezy using the
netinst CD on a spare HDD, using default parameters (using entire HDD and
one single partition as partition scheme) except
and testing them individually with memtest. Sure
enough, one of my RAM sticks (Crucial brand; DDR3) had gone bad, and
once it was removed Wheezy started working fine.
--
Harry Prevor
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of unsubscribe. Trouble
was failing, so I decided to try taking out
my two 8GB RAM sticks and testing them individually with memtest. Sure
enough, one of my RAM sticks (Crucial brand; DDR3) had gone bad, and
once it was removed Wheezy started working fine.
memtest is great at telling when there is an error for sure
10.05.2013 21:23, Harry Prevor пишет:
On 5/10/13, Артём Н. artio...@yandex.ru wrote:
10.05.2013 05:04, Harry Prevor пишет:
The normal images didn't work
for some reason now forgotten, so I had to use the unofficial
installation images that included nonfree drivers.
What are the drivers?
copy /var/log/messages, /var/log/syslog
(and send to list, of course)?
Also /etc/fstab plus result of sfdisk -lxuM /dev/sd command (or pvs --all lvs
--all, if you use LVM)...
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Thu, May 09, 2013 at 09:04:47PM -0400, Harry Prevor wrote:
So a few weeks ago, I decided to install Debian Wheezy (then unstable)
on a computer I built for my brother. The normal images didn't work
for some reason now forgotten, so I had to use the unofficial
installation images
guessing you have bad
hardware that just decided to coincidentally die with your new install of
the OS. Perhaps all the writes to the disk did it when you upgraded.
I installed Wheezy from the get-go on this machine; I had done a few
apt-get upgrades but no major distribution upgrades. Oddly enough
wrote:
Given that these problems were occurring before, I'm guessing you have bad
hardware that just decided to coincidentally die with your new install of
the OS. Perhaps all the writes to the disk did it when you upgraded.
I installed Wheezy from the get-go on this machine; I had done
).
Did you uninstall all third party packages?
– Chris
On Wed, May 8, 2013 at 3:18 AM, Jaime Ochoa Malagón chp...@gmail.comwrote:
Hi,
After my upgrade to wheezy my X has failed.
I tried to find the problem to fix it, and I was not be able to do it...
I have a partial success narrowing
Yes I have the debian packages for nvidia...
On Wed, May 8, 2013 at 8:57 AM, Lennart Sorensen
lsore...@csclub.uwaterloo.ca wrote:
On Wed, May 08, 2013 at 03:18:09AM -0500, Jaime Ochoa Malagón wrote:
After my upgrade to wheezy my X has failed.
I tried to find the problem to fix it, and I
, uninstalling or downgrading, then reinstalling
after the upgrade (if necessary).
Did you uninstall all third party packages?
– Chris
On Wed, May 8, 2013 at 3:18 AM, Jaime Ochoa Malagón chp...@gmail.comwrote:
Hi,
After my upgrade to wheezy my X has failed.
I tried to find the problem
So a few weeks ago, I decided to install Debian Wheezy (then unstable)
on a computer I built for my brother. The normal images didn't work
for some reason now forgotten, so I had to use the unofficial
installation images that included nonfree drivers. I had some problem
(also now unforgotten
10.05.2013 05:04, Harry Prevor пишет:
The normal images didn't work
for some reason now forgotten, so I had to use the unofficial
installation images that included nonfree drivers.
What are the drivers?
please mute the audio
Interesting music... :-)
Any ideas as to how to debug this? I
Hi,
After my upgrade to wheezy my X has failed.
I tried to find the problem to fix it, and I was not be able to do it...
I have a partial success narrowing the problem...
And I ask you for help to find it clearly I don't know if it is amd64
specific or not...
The usual suspect is the nvidia
an inventory, uninstalling or downgrading, then reinstalling
after the upgrade (if necessary).
Did you uninstall all third party packages?
– Chris
On Wed, May 8, 2013 at 3:18 AM, Jaime Ochoa Malagón chp...@gmail.comwrote:
Hi,
After my upgrade to wheezy my X has failed.
I tried to find
On Wed, May 08, 2013 at 03:18:09AM -0500, Jaime Ochoa Malagón wrote:
After my upgrade to wheezy my X has failed.
I tried to find the problem to fix it, and I was not be able to do it...
I have a partial success narrowing the problem...
And I ask you for help to find it clearly I don't
/DebianCD/ReleaseTesting/Wheezy
and I'll be filling in more details there in the next couple of days,
including some specific configurations that I'd like to see tested. If
you can help us test on Saturday, please take a look and join me in
#debian-cd where we'll be coordinating.
Cheers,
--
Steve
Karl,
I can see nvidia-kernel-source in my debian unstable package list, though i
have no 'src' line in sources.list. Probably because that package can not have
a binary counterpart unless you used it :)
When i used this package (along nvidia-glx and module-assistant) in the past,
i just
'm-a a-i'
sorry, should be: m-a a-i nvidia
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130429154448.7c88e...@mirrors.kernel.org
On Wed, 24 Apr 2013, Hans-J. Ullrich wrote:
Don't use the nvidia package from debian for googleearth. They do not work, as
the 32-bit-libs of nvidia have dependency problems. Obviously no one cared for
this at the moment.
Just download the installer from the nvidia website and execute it -
On Fri, Apr 26, 2013 at 04:08:58PM +0200, Giacomo Mulas wrote:
On Wed, 24 Apr 2013, Hans-J. Ullrich wrote:
Don't use the nvidia package from debian for googleearth. They do not work,
as
the 32-bit-libs of nvidia have dependency problems. Obviously no one cared
for
this at the moment.
was debugging my wheezy upgrade.. My hunch
is it is very close to being usable.
If not - I will look into moving to AMD if I can find cards that support dual-head 1920 x 1200 res
for each output..
Karl Schmidt
On 04/24/2013 12:00 AM, Hans-J. Ullrich wrote:
Don't use the nvidia package from debian for googleearth. They do not work, as
the 32-bit-libs of nvidia have dependency problems. Obviously no one cared for
this at the moment.
Just download the installer from the nvidia website and execute it -
I was trying to get google earth to work with the proprietary driver - it fails, so I thought I
would try the nouveau driver as it now supports dual monitors.
Never got it to recognize the card ( seems strange as wheezey is just about
stable? )
I followed the error -16 back to kernel issues
Don't use the nvidia package from debian for googleearth. They do not work, as
the 32-bit-libs of nvidia have dependency problems. Obviously no one cared for
this at the moment.
Just download the installer from the nvidia website and execute it - works
like a charm!
Good luck!
Hans
--
To
On Sun, Apr 14, 2013 at 11:34 PM, Bob Proulx b...@proulx.com wrote:
Francesco Pietra wrote:
Is any official (= working) advice on getting java at work with wheezy
(specifically in amd64, if relevant)?
http://wiki.debian.org/Java
What should be installed/reconfigured/uninstalled other
On Sunday 14 Apr 2013, Zenaan Harkness wrote:
My test (and Java app I want to run) is sweethome3d.
Wasn't working on wheezy.
Upgraded to sid. Sweethome3d worked.
Upgraded some days back, now it doesn't work.
Not sure if I'm doing anything wrong. 64-bit.
Haven't tested in a browser.
Zenaan
Francesco Pietra wrote:
Is any official (= working) advice on getting java at work with wheezy
(specifically in amd64, if relevant)?
http://wiki.debian.org/Java
What should be installed/reconfigured/uninstalled other than the packages
obtained from wheezy desktop install, followed
expect that these problems will be mostly sorted out by the time
wheezy gets close to being stable.
There should be good reason why you would upgrade an Ubuntu (for
example) only in minor consecutive version steps. In Debian, this resembles
tracking 'testing' all the time. The only alternative
On 02/14/2013 10:47 PM, Hendrik Boom wrote:
I do expect that these problems will be mostly sorted out by the time wheezy
gets close to being
stable.
That is really the basic question - wheezy is close - down to 211 bugs
http://bugs.debian.org/release-critical/
I'm wondering if I can jump
On Fri, Feb 15, 2013 at 10:02:46AM -0600, Karl Schmidt wrote:
On 02/14/2013 10:47 PM, Hendrik Boom wrote:
I do expect that these problems will be mostly sorted out by the time wheezy
gets close to being
stable.
That is really the basic question - wheezy is close - down to 211 bugs
http
On Fri, Feb 15, 2013 at 11:21:47AM -0500, Hendrik Boom wrote:
I check that both systems boot, and that, when booted, they each have
mounted the correct partitions, and not each others'. In the case of
lilo, I try to make it boot from a floppy, and I install the old and new
systems' lilos
Archive: http://lists.debian.org/20130215162914.gb12...@topoi.pooq.com
wheezy and nvidia doesn't work with my card
I have to add the kernel commandline nomodeset
then install the nvidia-dkms package and setup xorg.conf
once i've done that it's perfect
I have a GeForce GTX 550 Ti
Dick Thomas
I am still using squeeze - I want to jump the gun and upgrade to wheezy - Most likely problems would
have to do with nvidia.
Is anyone running wheezy today? (down to 211 release critical bugs !! )
Karl
Is anyone running wheezy today?
Yes. I don't see crashes or critical bugs with major applications, but i avoid
KDE on 'production' desktops :) but then, 'production ready' is a slightly
broad term :)
From my i386 laptop, it seems to be ok though (with plasma desktop) if you
don't insist
On Thu, Feb 14, 2013 at 04:35:28PM -0600, Karl Schmidt wrote:
I am still using squeeze - I want to jump the gun and upgrade to
wheezy - Most likely problems would have to do with nvidia.
Is anyone running wheezy today? (down to 211 release critical bugs !! )
I'm running wheezy on all my
On Fri, Feb 15, 2013 at 12:58:45AM +0100, Michael wrote:
Is anyone running wheezy today?
Yes. I don't see crashes or critical bugs with major applications, but i
avoid KDE on 'production' desktops :) but then, 'production ready' is a
slightly broad term :)
From my i386 laptop
Hendrik,
I see. Now that's another statement !
Maybe you should move to grub then, within Squeeze, and also try to upgrade
only the 'problem' packages first ? if that's all fine, to the rest ?
I always do such things within aptitude, maybe in several cycles, since it
gives me more choices
--upgrade, but at least, there is a chance.
I do expect that these problems will be mostly sorted out by the time
wheezy gets close to being stable.
There should be good reason why you would upgrade an Ubuntu (for example)
only in minor consecutive version steps. In Debian, this resembles
why is autologin not working with gdm3 on Debian wheezy..??
this is my /etc/gdm3/deamon.conf
# GDM configuration storage
#
# See /usr/share/gdm/gdm.schemas for a list of available options.
[daemon]
# Enabling automatic login
# AutomaticLoginEnable = true
# AutomaticLogin = user1
# Enabling
Hi,
With the sound of the ever approaching freeze ringing loudly in our ears,
we're (somewhat belatedly) looking at finalising the list of release
architectures for the Wheezy release.
Comments on / additions and corrections to the content of
http://release.debian.org/wheezy/arch_qualify.html
on other architectures is welcome.
The Java and Go frontends already default to 4.7, the D frontend may be updated
for 4.7 in time (currently unused, as all D packages are built using gdc-v1).
As I understand Ludovic, the Ada frontend will stay with 4.6.
GCC-4.4 will stay in wheezy (D v1 frontend
Howdy,
Has anyone used Wheezy as an OpenVZ host? Apparently the openvz patches
are merged now in the default kernel (see http://wiki.debian.org/OpenVz)
Though vzctl has other ideas...
root@astrotrain:/lib/modules# service vz start
Running kernel is not an OpenVZ kernel
The openvz website
If not misused with wheezy, file-roller/amd64 wheezy, in my hands,
expects gzip format, refusing to decompress, untar *.tar.gz files. Any
of the commands i used (tar -zxvf ... including file-roller itself)
complained about that. I had to open the tar.gz file (VMD binary) on
another machine
...@btinternet.com
À: debian-amd64@lists.debian.org
Envoyé: Wed, 06 Apr 2011 02:18:09 +0200 (CEST)
Objet: Evolution problem - SQUEEZE/WHEEZY
I have recently installed WHEEZY to a separate partion on one of my
hard drives. My HOME folder is on another partition and is mounted
on /home in /etc
On Wed, Apr 06, 2011 at 01:18:09AM +0100, Alasdair Campbell wrote:
I have recently installed WHEEZY to a separate partion on one of my
hard drives. My HOME folder is on another partition and is mounted
on /home in /etc/fstab in both WHEEZY and SQUEEZE.
Now here is the funny thing - I cannot
On Mon, Nov 15, 2010 at 21:29:07 -0500, Matt Turner wrote:
On Mon, Nov 15, 2010 at 8:15 PM, Samuel Thibault sthiba...@debian.org wrote:
Matt Turner, le Mon 15 Nov 2010 19:51:10 -0500, a écrit :
On Mon, Nov 15, 2010 at 7:24 PM, Roger Leigh rle...@codelibre.net wrote:
What's the actual
On Tue, Nov 16, 2010 at 01:14:09 +0100, Matthias Klose wrote:
On 14.11.2010 13:19, Julien Cristau wrote:
On Fri, Oct 29, 2010 at 15:43:57 +0200, Matthias Klose wrote:
For wheezy I'm planning to change the linking behaviour for DSOs
(turning on --as-needed and --no-copy-dt-needed-entries
On Tue, Nov 16, 2010 at 01:14:09AM +0100, Matthias Klose wrote:
On 14.11.2010 13:19, Julien Cristau wrote:
On Fri, Oct 29, 2010 at 15:43:57 +0200, Matthias Klose wrote:
For wheezy I'm planning to change the linking behaviour for DSOs
(turning on --as-needed and --no-copy-dt-needed-entries
This change is one I can agree with on technical grounds, though it
will cause a great deal of pain in the short term. Have we got any
estimates on exactly how much breakage will result before the change
gets made?
Fedora already made the change a full release cycles ago, and Fedora
package
* Kurt Roeckx k...@roeckx.be [101114 14:08]:
People have been claiming that constructors or init section are a
possible problem. I have yet to see an example where it breaks.
The following example is a bit constructed, but shows a silent change
of run-time behaviour if --as-needed is passed:
On Tue, Nov 16, 2010 at 09:49:08AM +0100, Julien Cristau wrote:
On Mon, Nov 15, 2010 at 21:29:07 -0500, Matt Turner wrote:
I can't see why you think --as-needed is fundamentally wrong or
unnecessary.
Check out http://www.gentoo.org/proj/en/qa/asneeded.xml
--as-needed has saved tons
Steve Langasek, le Tue 16 Nov 2010 09:14:40 -0800, a écrit :
I don't argue that this makes --as-needed *correct* as a default, but I
think it's clear how using --as-needed may benefit a distribution in terms
of reducing churn when library dependencies change.
We agree on the second part, but
On 16.11.2010 10:42, Roger Leigh wrote:
On Tue, Nov 16, 2010 at 01:14:09AM +0100, Matthias Klose wrote:
On 14.11.2010 13:19, Julien Cristau wrote:
On Fri, Oct 29, 2010 at 15:43:57 +0200, Matthias Klose wrote:
For wheezy I'm planning to change the linking behaviour for DSOs
(turning
* Roland McGrath:
I can't see why you think --as-needed is fundamentally wrong or unnecessary.
It is fundamentally wrong because -lfoo means I demand that the
initializers of libfoo.so run, whether or not I called anything in it.
So it's more like static linking. 8-)
IMHO, the current
On Tue, Nov 16, 2010 at 07:04:53PM +0100, Matthias Klose wrote:
On 16.11.2010 10:42, Roger Leigh wrote:
On Tue, Nov 16, 2010 at 01:14:09AM +0100, Matthias Klose wrote:
On 14.11.2010 13:19, Julien Cristau wrote:
On Fri, Oct 29, 2010 at 15:43:57 +0200, Matthias Klose wrote:
For wheezy I'm
On 15.11.2010 07:16, Roland McGrath wrote:
mattst88 airlied_, does Fedora use --as-needed by default? Fedora 14 too?
airlied_ mattst88: yes
The naming of the options makes people easily confused.
--no-add-needed is the only option Fedora's gcc passes.
yes, OpenSuse is using --as-needed,
On 14.11.2010 16:06, Roger Leigh wrote:
While I understand the rationale for --no-copy-dt-needed-entries for
preventing encapsulation violations via indirect linking, I don't agree
with the use of --as-needed *at all*. If a library has been explicitly
linked in, it shouldn't be removed. This
On Mon, Nov 15, 2010 at 11:02:57PM +0100, Matthias Klose wrote:
maybe, and fix it in N - ~100 packages? Or fix the ~100 packages?
The point of injection is for discussion. I would prefer having
this set in dpkg-buildflags, and then disabled by these ~100
packages. Note that this is probably
On 15.11.2010 07:16, Roland McGrath wrote:
yes, OpenSuse is using --as-needed, but not --no-add-needed.
That is a pretty nutty choice.
--
To UNSUBSCRIBE, email to debian-amd64-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
1 - 100 of 116 matches
Mail list logo
