Bug#1055389: libgccjit-12-dev: gccjit is not added to the usual library search paths

2023-11-05 Thread Ralf Jung
Package: libgccjit-12-dev Version: 12.3.0-9 Severity: normal Dear Maintainer, when installing libgccjit-12-dev, I'd expect to be able to write applications that link against gccjit. (The GCC codegen backend for the Rust compiler is one example for such an application.) However, strangely, that

Bug#918226: marked as done (gcc-snapshot.prerm yields error messages - incorrect paths?)

2021-05-08 Thread Debian Bug Tracking System
Your message dated Sat, 8 May 2021 11:30:07 +0200 with message-id and subject line Re: gcc-snapshot.prerm yields error messages - incorrect paths? has caused the Debian Bug report #918226, regarding gcc-snapshot.prerm yields error messages - incorrect paths? to be marked as done. This means that

Bug#814977: marked as done ([fixed in 8] gnat paths are wrong due to ada-gcc-name.diff)

2019-01-23 Thread Debian Bug Tracking System
Your message dated Wed, 23 Jan 2019 10:00:21 + with message-id and subject line Bug#920166: Removed package(s) from unstable has caused the Debian Bug report #814977, regarding [fixed in 8] gnat paths are wrong due to ada-gcc-name.diff to be marked as done. This means that you claim that the

Bug#918226: gcc-snapshot.prerm yields error messages - incorrect paths?

2019-01-04 Thread Vincent Lefevre
Package: gcc-snapshot Version: 1:20190102-1 Severity: normal I can see the following error messages on upgrade or removal: find: ‘/usr/lib/gcc-snapshot/share/python’: No such file or directory find: ‘/usr/lib/gcc-snapshot/share/python’: No such file or directory They come from /var/lib/dpkg/info

Bug#889133: marked as done (gfortran-7: gfortran mod files include full paths, making software bit unreproducible)

2018-02-07 Thread Debian Bug Tracking System
Your message dated Wed, 07 Feb 2018 18:50:00 + with message-id and subject line Bug#889133: fixed in gcc-7 7.3.0-2 has caused the Debian Bug report #889133, regarding gfortran-7: gfortran mod files include full paths, making software bit unreproducible to be marked as done. This means that

Bug#889133: gfortran-7: gfortran mod files include full paths, making software bit unreproducible

2018-02-02 Thread Alastair McKinstry
> Please could you take this upstream to the fortran and gcc mailing lists? I'd > rather like to see something like > >-fdebug-prefix-map= > > which should go upstream. I've forwarded the patch to the gfortran list, but I'm not sure what you mean. I know of no code that uses the value in the

Bug#889133: gfortran-7: gfortran mod files include full paths, making software bit unreproducible

2018-02-02 Thread Matthias Klose
On 02.02.2018 10:23, Alastair McKinstry wrote: > Package: gfortran-7 > Version: 0.7.2-1 > Severity: normal > Tags: upstream patch > > gfortran creates binary .mod and .smod files. These are compressed files, > which look like: > (viewed with e.g. zmore /usr/include/cgns.mod ): > > GFORTRAN modul

Bug#889133: gfortran-7: gfortran mod files include full paths, making software bit unreproducible

2018-02-02 Thread Alastair McKinstry
Package: gfortran-7 Version: 0.7.2-1 Severity: normal Tags: upstream patch gfortran creates binary .mod and .smod files. These are compressed files, which look like: (viewed with e.g. zmore /usr/include/cgns.mod ): GFORTRAN module version '14' created from /build/libcgns-XmhIxt/libcgns-3.3.0/sr

Fwd: dh-fortran-mod, gfortran transition and .mod paths

2018-01-23 Thread Alastair McKinstry
break any other compilers (flang). Would there be any objections to a patch to search the path /usr/include/gfortran-$(mver), /usr/include/$(multiarch)/gfortran-$(mver) ahead of the usual paths, by default? Best regards Alastair McKinstry Forwarded Message Subject:dh-f

Bug#861760: marked as done (gcc-7: Please support multiarch paths for sh3)

2017-05-05 Thread Debian Bug Tracking System
Your message dated Fri, 05 May 2017 10:18:59 + with message-id and subject line Bug#861760: fixed in gcc-7 7.1.0-4 has caused the Debian Bug report #861760, regarding gcc-7: Please support multiarch paths for sh3 to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: Bug#851869: gcc-6: Please support multiarch paths for sh3

2017-05-03 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > unarchive 851869 Bug #851869 {Done: Matthias Klose } [src:gcc-6] gcc-6: Please support multiarch paths for sh3 Unarchived Bug 851869 > clone 851869 -1 Bug #851869 {Done: Matthias Klose } [src:gcc-6] gcc-6: Please support multiarch paths f

Bug#814978: marked as done (gcc-6(+gcc-5): gnat paths are wrong due to ada-gcc-name.diff)

2017-02-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 Feb 2017 21:03:40 + with message-id and subject line Bug#814978: fixed in gcc-6 6.3.0-6 has caused the Debian Bug report #814978, regarding gcc-6(+gcc-5): gnat paths are wrong due to ada-gcc-name.diff to be marked as done. This means that you claim that the problem

Bug#851869: marked as done (gcc-6: Please support multiarch paths for sh3)

2017-01-24 Thread Debian Bug Tracking System
Your message dated Tue, 24 Jan 2017 15:10:56 + with message-id and subject line Bug#851869: fixed in gcc-6 6.3.0-5 has caused the Debian Bug report #851869, regarding gcc-6: Please support multiarch paths for sh3 to be marked as done. This means that you claim that the problem has been dealt

Bug#851869: gcc-6: Please support multiarch paths for sh3

2017-01-19 Thread John Paul Adrian Glaubitz
Source: gcc-6 Version: 6.3.0-3 Severity: normal Tags: patch User: helm...@debian.org Usertags: rebootstrap Hi! In order to be able to support sh3 as an architecture in rebootstrap, we need to modify the gcc-multiarch patch to support both "sh4" and "sh3" for multiarch paths.

Processed: dpkg-dev: dpkg-shlibdeps searches paths given with -l in reverse order

2016-05-09 Thread Debian Bug Tracking System
Processing control commands: > block 818873 with -1 Bug #818873 [src:gcc-5-cross] gcc-5-cross: FTBFS when built with dpkg-buildpackage -A (No such file or directory) 818873 was not blocked by any bugs. 818873 was not blocking any bugs. Added blocking bug(s) of 818873: 823805 -- 818873: http://b

Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-25 Thread Matthias Klose
Control: tags -1 - patch On 18.02.2016 12:28, Svante Signell wrote: The remaining problem is a carriage return character in the target_bit variable, fixed by the patch: --- a/src/gcc/testsuite/ada/acats/run_all.sh.orig 2016-02-17 17:29:12.872370832 +0100 +++ b/src/gcc/testsuite/ada/acats

Processed: Re: Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-25 Thread Debian Bug Tracking System
Processing control commands: > tags -1 - patch Bug #814978 [src:gcc-5] gcc-5: gnat paths are wrong due to ada-gcc-name.diff Removed tag(s) patch. -- 814978: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=814978 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-18 Thread Svante Signell
tags 814978 patch thanks On Wed, 2016-02-17 at 12:06 +0100, Svante Signell wrote: > On Wed, 2016-02-17 at 11:50 +0100, Matthias Klose wrote: > > On 17.02.2016 10:31, Svante Signell wrote: > > > Source: gcc-5 > > > Version: 5.3.1-8 > > > Severity: important > > > Usertags: gnat-5 > > > this might

Processed: Re: Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-18 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > tags 814978 patch Bug #814978 [src:gcc-5] gcc-5: gnat paths are wrong due to ada-gcc-name.diff Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 814978: http://bugs.debian.org/c

Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-17 Thread Ludovic Brenta
On Wed, 17 Feb 2016 11:50:04 +0100, Matthias Klose wrote: this might be a bad merge/update; Ludovic, Nicolas, could you have a look? GCC 6 likely has the same issue. Will do. -- Ludovic.

Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-17 Thread Svante Signell
On Wed, 2016-02-17 at 11:50 +0100, Matthias Klose wrote: > On 17.02.2016 10:31, Svante Signell wrote: > > Source: gcc-5 > > Version: 5.3.1-8 > > Severity: important > > Usertags: gnat-5 > this might be a bad merge/update; Ludovic, Nicolas, could you have a look? GCC > 6  > likely has the same issu

Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-17 Thread Matthias Klose
On 17.02.2016 10:31, Svante Signell wrote: Source: gcc-5 Version: 5.3.1-8 Severity: important Usertags: gnat-5 Hi, Due to the Debian patch ada-gcc-name.diff the name of gcc becomes gcc-5-5 instead of gcc-5. This is easily shown with: /usr/bin/gnatchop -v fc51b00.a where fcb51b.a is located at s

Processed: Re: Bug#814977: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-17 Thread Debian Bug Tracking System
Processing control commands: > reassign -1 gcc-5 5.3.1-8 Bug #814977 [src:gcc-5.3.1-8] gcc-5: gnat paths are wrong due to ada-gcc-name.diff Warning: Unknown package 'src:gcc-5.3.1-8' Bug reassigned from package 'src:gcc-5.3.1-8' to 'gcc-5'. Ignoring request to al

Re: Bug#814977: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-17 Thread Mattia Rizzolo
control: reassign -1 gcc-5 5.3.1-8 On Wed, Feb 17, 2016 at 10:29:42AM +0100, Svante Signell wrote: > Source: gcc-5.3.1-8 guess you wanted to split this in Source and Version. > Severity: important > Usertags: gnat-5 > > Hi, > > Due to the Debian patch ada-gcc-name.diff the name of gcc becomes

Bug#814978: gcc-5: gnat paths are wrong due to ada-gcc-name.diff

2016-02-17 Thread Svante Signell
Source: gcc-5 Version: 5.3.1-8 Severity: important Usertags: gnat-5 Hi, Due to the Debian patch ada-gcc-name.diff the name of gcc becomes gcc-5-5 instead of gcc-5. This is easily shown with: /usr/bin/gnatchop -v fc51b00.a where fcb51b.a is located at src/gcc/testsuite/ada/acats/support/ (same whe

Bug#595404: marked as done (gcc-4.4: prefers current directory over system paths for #include )

2015-07-05 Thread Debian Bug Tracking System
Your message dated Sun, 05 Jul 2015 16:18:22 + with message-id and subject line Bug#707276: Removed package(s) from unstable has caused the Debian Bug report #595404, regarding gcc-4.4: prefers current directory over system paths for #include to be marked as done. This means that you claim

Bug#772642: marked as done (cpp-4.9: please support multiarch for the user search paths (CPATH, etc.))

2015-05-03 Thread Debian Bug Tracking System
Your message dated Mon, 04 May 2015 01:30:17 +0200 with message-id <5546af89.3060...@debian.org> and subject line Re: Bug#772642: cpp-4.9: please support multiarch for the user search paths (CPATH, etc.) has caused the Debian Bug report #772642, regarding cpp-4.9: please support multiarch f

Bug#772642: cpp-4.9: please support multiarch for the user search paths (CPATH, etc.)

2015-05-03 Thread Vincent Lefevre
On 2015-05-03 18:33:12 +0200, Matthias Klose wrote: > On 12/09/2014 03:03 PM, Vincent Lefevre wrote: > > cpp currently supports multiarch search paths for /usr/local and /usr, > > but not for directories supplied via environment variables like $CPATH > > and $C_INCLUDE_PATH.

Processed: Re: Bug#772642: cpp-4.9: please support multiarch for the user search paths (CPATH, etc.)

2015-05-03 Thread Debian Bug Tracking System
Processing control commands: > tags -1 + wontfix Bug #772642 [cpp-4.9] cpp-4.9: please support multiarch for the user search paths (CPATH, etc.) Added tag(s) wontfix. -- 772642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772642 Debian Bug Tracking System Contact ow...@bugs.debian.

Bug#772642: cpp-4.9: please support multiarch for the user search paths (CPATH, etc.)

2015-05-03 Thread Matthias Klose
Control: tags -1 + wontfix On 12/09/2014 03:03 PM, Vincent Lefevre wrote: > Package: cpp-4.9 > Version: 4.9.2-5 > Severity: wishlist > > cpp currently supports multiarch search paths for /usr/local and /usr, > but not for directories supplied via environment variables

Bug#772642: cpp-4.9: please support multiarch for the user search paths (CPATH, etc.)

2014-12-09 Thread Vincent Lefevre
Package: cpp-4.9 Version: 4.9.2-5 Severity: wishlist cpp currently supports multiarch search paths for /usr/local and /usr, but not for directories supplied via environment variables like $CPATH and $C_INCLUDE_PATH. For instance, "cpp -v" gives: /usr/local/include/x86_64-linux-gnu

Bug#677582: gcc-4.4-base: NMU gcc-4.4 4.4.7-2.1 prepared to fix upgrade paths

2012-09-15 Thread Andreas Beckmann
Package: gcc-4.4-base Followup-For: Bug #677582 Hi, I've just prepared a NMU for gcc-4.4 that fixes this issue (i.e. the broken upgrade paths where apt prefers to keep (not upgrade) gcc-4.4-base instead of removing the obsolete gcj-4.4-base). Holger has agreed to sponsor this NMU and uplo

Re: sparse and multiarch include paths

2011-08-24 Thread Josh Triplett
On Thu, Aug 25, 2011 at 12:43:37AM +0200, Ludovic Brenta wrote: > Josh Triplett writes: > > When trying to use sparse on some low-level userspace code, I ran into > > the following error: > > > > /usr/include/bits/socket.h:381:11: error: unable to open 'asm/socket.h' > > See http://bugs.debian.or

Re: sparse and multiarch include paths

2011-08-24 Thread Ludovic Brenta
Josh Triplett writes: > When trying to use sparse on some low-level userspace code, I ran into > the following error: > > /usr/include/bits/socket.h:381:11: error: unable to open 'asm/socket.h' See http://bugs.debian.org/638418 Hope this helps -- Ludovic Brenta. -- To UNSUBSCRIBE, email to

Re: sparse and multiarch include paths

2011-08-24 Thread Chris Forbes
I've hit this as well. The ubuntu-packaged sparse seems to get this right; building from git sources gives busted paths -- suspect they have patches that need to come upstream? -- Chris On Thu, Aug 25, 2011 at 9:42 AM, Josh Triplett wrote: > When trying to use sparse on some low-level u

sparse and multiarch include paths

2011-08-24 Thread Josh Triplett
gnu in its default include path. This relates to Debian's multiarch efforts, moving such headers to paths which include the architecture to allow simultaneous installation of the headers for multiple architectures. I don't know how gcc ends up with that directory in its include path, but sp

Bug#595404: gcc-4.4: prefers current directory over system paths for #include

2010-09-03 Thread Sascha Silbe
Package: gcc-4.4 Version: 4.4.4-11 Severity: important gcc in Squeeze prefers header files from the current directory over those in system paths for #include : sascha.si...@twin:/tmp/sascha_silbe/tmpbox.4Pe8smERA3$ cat > test.c #include #include int main(int argc, char **argv) { pri

Bug#527537: marked as done (Broken library search paths)

2009-05-17 Thread Debian Bug Tracking System
Your message dated Sun, 17 May 2009 13:32:39 + with message-id and subject line Bug#527537: fixed in gcc-4.4 4.4.0-5 has caused the Debian Bug report #527537, regarding Broken library search paths to be marked as done. This means that you claim that the problem has been dealt with. If this

Bug#527537: Broken library search paths

2009-05-09 Thread Goswin von Brederlow
alize > > Not an issue. > >> ! Path for the wrong target > > Not an issue as long as the 32-bit paths are before the other paths. Unless one is missing a library and the other isn't. Esspecially in the case of glibc and uclibc based libs where I think the object format is th

Bug#527537: Broken library search paths

2009-05-09 Thread Arthur Loiret
ssue as long as the 32-bit paths are before the other paths. > "/lib/x86_64-linux-gnu" is missing. > "/lib/i486-linux-gnu" is missing. No they're not. We have never wanted them. > "/lib64", "/usr/lib64" could also > be considered missing, the

Bug#527537: Broken library search paths

2009-05-09 Thread Arthur Loiret
Thanks for your report. I'm trying to have this fixed asap. -- To UNSUBSCRIBE, email to debian-gcc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#527537: Broken library search paths

2009-05-07 Thread Goswin Brederlow
64/ld-linux-x86-64.so.2 (0x2b271088c000) Seems 100% broken. ------ MfG Goswin PS: I haven't checked the include paths. I hope you didn't break them with the new multiarch patch. -- System Information: Debian Release: squeeze/sid APT prefers unstable-i386 A

PATHS

2004-11-12 Thread Rui Fernandes
Hi,   Does anyone knows what's the name of the environment variable that controls the GCC libraries path ( include and lib )? How can I change it permanently? One more question: I'm still learning about installing packages, etc... in Debian. I have, in disk, a new compressed version of GCC;

Bug#167014: marked as done (gcj-3.2: Wrapper script cannot handle paths with spaces)

2003-03-17 Thread Debian Bug Tracking System
d 186jBv-0001Pj-00; Wed, 30 Oct 2002 14:06:47 +1100 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Ben Burton <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: gcj-3.2: Wrapper script can

Bug#167014: gcj-3.2: Wrapper script cannot handle paths with spaces

2002-10-29 Thread Ben Burton
Package: gcj-3.2 Version: 1:3.2.1-0pre4 Severity: normal Hi. The gcj-wrapper-3.2 script currently cannot handle paths containing spaces. As an example, create subdirectory "foo bar" containing Test.java. [EMAIL PROTECTED]:/tmp> gcj-wrapper-3.2 foo\ bar/Test.java gcj-3.2: cannot sp