On Monday, April 14 2014, Ludovic Courtès wrote:
>> Is it deprecated to use -Werror with the autotoools?
>
> In general, using -Werror is very risky, because a slight change in a
> third-party header, or in compiler warnings, can cause the project to
> fail to build. In Guile building with -Werro
Andreas Enge skribis:
> On Mon, Apr 14, 2014 at 09:16:31PM +0200, Ludovic Courtès wrote:
>> This is because you’re compiling with -Wundef -Werror, something that
>> libc 2.19 headers apparently don’t support.
>
> I tried without both, and then it works. Do you have a source and suggestion
> on wh
On Mon, Apr 14, 2014 at 09:16:31PM +0200, Ludovic Courtès wrote:
> This is because you’re compiling with -Wundef -Werror, something that
> libc 2.19 headers apparently don’t support.
I tried without both, and then it works. Do you have a source and suggestion
on what to do in such a case? Is it de
Andreas Enge skribis:
> On Sat, Apr 05, 2014 at 10:44:55PM +0200, Ludovic Courtès wrote:
>> Comments welcome!
[...]
> When I do a "./configure" of mpc, none of the standard headers are recognised;
> I obtain something like:
>
> configure:12920: checking for ANSI C header files
> configure:13024
On Sat, Apr 05, 2014 at 10:44:55PM +0200, Ludovic Courtès wrote:
> Comments welcome!
This could be a useful package! Do I need to set any more environment
variables in my .bashrc? So far, I have
export PATH=$HOME/.guix-profile/bin:$PATH
export LIBRARY_PATH=$HOME/.guix-profile/lib
export CPATH=$HOM
Mark H Weaver skribis:
> l...@gnu.org (Ludovic Courtès) writes:
>
>> To install a working C environment in your profile, run:
>>
>> guix package -i gcc binutils ld-wrapper glibc
>
> [...]
>
>> I believe this could be addressed by having a simple “toolchain”
>> meta-package with the sole purpose
l...@gnu.org (Ludovic Courtès) writes:
> To install a working C environment in your profile, run:
>
> guix package -i gcc binutils ld-wrapper glibc
[...]
> I believe this could be addressed by having a simple “toolchain”
> meta-package with the sole purpose of propagating these 4 inputs, and b
On 01/27/2014 10:53 AM, Ludovic Courtès wrote:
>
> I believe this could be addressed by having a simple “toolchain”
> meta-package with the sole purpose of propagating these 4 inputs, and by
> documenting it in the manual.
Yes, a toolchain package would be nice. Debian does similarly: it has
bui
Sree Harsha Totakura skribis:
> On 01/26/2014 08:30 PM, Ludovic Courtès wrote:
>> To summarize: ‘propagated-inputs’ should list libraries 99% of the
>> time. Listing programs in ‘propagated-inputs’ just for the sake of
>> populating $PATH is a bad idea.
>
> I recently found that many library pac
