Processing commands for cont...@bugs.debian.org:
> tag 634821 + wontfix
Bug #634821 {Done: Matthias Klose } [libgcc1] libgcc1:
filename change breaks old gcc
Added tag(s) wontfix.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
634821: http://bugs.debian.org/cgi-
tag 634821 + wontfix
thanks
both gcc-4.2 and gcc-4.3 are removed from unstable. If you want to make them
work, you'll have to backport the multiarch patches to these versions.
the libgcc1 version in unstable explicitly breaks these gcc versions.
--
To UNSUBSCRIBE, email to debian-gcc-requ...@
gcc-4.3 is no longer installable:
# apt-get install gcc-4.3
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution tha
Hello,
I am sorry , i think you must reopen the Bug , or give an solution , some
debian packets by example like linux-headers-2.6.32-5-AMD64 want gcc-4.3 and
so in SID the kernel linux 2.6.32-5 can't be used any time, when some driver
or services must be updated and compiled whith dkms they can'
On 07/20/2011 11:54 AM, Andy Chittenden wrote:
>> By the way, Andy, could you give a quick reminder of what you are
>> using gcc 4.2 and 4.3 to do?
>
> We have some old code that we need to maintain that won't compile with later
> versions of the compiler.
IMO the better approach would be mult
Jonathan Nieder wrote:
> 1. Is there any GCC command-line option that people can use to work
>around this kind of thing (e.g., to add a directory to the front of
>the search order)?
Just for kicks (and in case there's a good place to document it):
mkdir /usr/local/lib/gcc/4.3.5
> By the way, Andy, could you give a quick reminder of what you are
> using gcc 4.2 and 4.3 to do?
We have some old code that we need to maintain that won't compile with later
versions of the compiler.
--
Andy, BlueArc Engineering
--
To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debia
Jonathan Nieder wrote:
> Are there symlinks under /usr/lib/gcc hard-coding the path to libstdc++
> and libgfortran?
Ah, found them. Yes, in libstdc++6-4.x-dev and gfortran-4.x packages
(which presumably also need to be marked broken). Sorry for the noise.
--
To UNSUBSCRIBE, email to debian-
Matthias Klose wrote:
> libgcc2 and libgcc4 are missing. But I don't like it. Why stop at
> libgcc/libgomp, and not at libstdc++ and libgfortran?
Are there symlinks under /usr/lib/gcc hard-coding the path to libstdc++
and libgfortran?
> For now, I'll add an
> unconditional break on gcc-4.1 and g
On 07/20/2011 10:17 AM, Jonathan Nieder wrote:
> Jonathan Nieder wrote:
>
>> 2. Would it make sense to introduce a new package libgcc1-multiarch
>>and make libgcc1 into a compatibility package that ships a symlink
>>
>> /lib/libgcc_s.so.1 -> /lib/$arch/libgcc_s.so.1
>>
>>for the sake
Jonathan Nieder wrote:
> 2. Would it make sense to introduce a new package libgcc1-multiarch
>and make libgcc1 into a compatibility package that ships a symlink
>
> /lib/libgcc_s.so.1 -> /lib/$arch/libgcc_s.so.1
>
>for the sake of smooth partial upgrades?
i.e., something like this?
Package: libgcc1
Version: 4.6.0-12
Severity: important
Justification: breaks related software
X-Debbugs-Cc: Andrew Chittenden
Hi,
As Andy noticed[*], moving libgcc_s.so.1 from /lib to /lib/$arch
breaks versions of gcc from before that move.
$ echo 'int main(void) { return 0; }' | gcc-4.3 -x c
12 matches
Mail list logo
