[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

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

Your message dated Mon, 04 May 2015 01:30:17 +0200
with message-id <5546AF89.3060707@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 for the user search paths (CPATH, etc.)
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
772642: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772642
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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
/usr/local/include
[...]
/usr/include/x86_64-linux-gnu
/usr/include

and when adding the -m32 option:

/usr/local/include/i386-linux-gnu
/usr/local/include
[...]
/usr/include/i386-linux-gnu
/usr/include

But if I use CPATH=/home/vlefevre/include, I just get:

/home/vlefevre/include

Adding the other directory to $CPATH is not a good solution because
one doesn't always know the ABI (whether -m32 is present or not) in
advance, i.e. one doesn't know in advance which directory to add.

-- System Information:
Debian Release: 8.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages cpp-4.9 depends on:
ii  gcc-4.9-base   4.9.2-5
ii  libc6          2.19-13
ii  libcloog-isl4  0.18.2-1
ii  libgmp10       2:6.0.0+dfsg-6
ii  libisl10       0.12.2-2
ii  libmpc3        1.0.2-1
ii  libmpfr4       3.1.2-1+b1
ii  zlib1g         1:1.2.8.dfsg-2+b1

cpp-4.9 recommends no packages.

Versions of packages cpp-4.9 suggests:
ii  gcc-4.9-locales  4.9.2-5

-- no debconf information

--- End Message ---
--- Begin Message --- 
On 05/04/2015 01:26 AM, Vincent Lefevre wrote:
>> the preprocessor doesn't know anything about "/home/vlefevre/include".
>> what should it append?
> 
> It should follow the same convention as the system directories.
> For instance, if I use CPATH=/home/vlefevre/include then it should
> add:
> 
>   /home/vlefevre/include/x86_64-linux-gnu
>   /home/vlefevre/include
> 
> for x86_64 compilation, and
> 
>   /home/vlefevre/include/i386-linux-gnu
>   /home/vlefevre/include
> 
> for i386 compilation (i.e. with -m32).

no, this assumption is not rectified. It completely depends on what you expect
on your own semantics.  I'm closing this issue.  If you care about it, convince
upstream, get it accepted upstream, and it will appear in Debian.

Matthias

--- End Message ---
Reply to: