mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Didier Kryn <kryn@in2p3.fr>
To: musl@lists.openwall.com
Subject: Re: Building musl-cross-make with gnat in musl environement
Date: Wed, 13 Dec 2017 10:29:04 +0100	[thread overview]
Message-ID: <6ed07b18-e7ce-fc54-9498-d3123a506cc2@in2p3.fr> (raw)
In-Reply-To: <20171130170605.GK1627@brightrain.aerifal.cx>

[-- Attachment #1: Type: text/plain, Size: 464 bytes --]

Le 30/11/2017 à 18:06, Rich Felker a écrit :
> Just patch out the poisoning instead. It's only meaningful to GCC
> developers and should_not_  be used in deployment for reasons exactly
> like what you discovered here, pretty much the same reasons -Werror
> should not be enabled in deployment.

     Here is a new set of patches in this spirit. Posionning of calloc 
is removed and compilation switches are changed for gnattools.

     Didier


[-- Attachment #2: gnat63-no-poison.diff --]
[-- Type: text/x-patch, Size: 317 bytes --]

--- gcc-6.3.0-A/gcc/system.h
+++ gcc-6.3.0-B/gcc/system.h
@@ -819,7 +819,8 @@
 #ifndef USES_ISL
 #undef calloc
 #undef strdup
- #pragma GCC poison calloc strdup
+/* Do not poison calloc because it is declared in musl's sched.h */
+ #pragma GCC poison strdup
 #endif
 
 #if !defined(FLEX_SCANNER) && !defined(YYBISON)

[-- Attachment #3: gnat63-gnattools.diff --]
[-- Type: text/x-patch, Size: 451 bytes --]

diff -rupN gcc-6.3.0-A/gnattools/Makefile.in gcc-6.3.0-B/gnattools/Makefile.in
--- gcc-6.3.0-A/gnattools/Makefile.in	2016-04-04 18:37:58.000000000 +0200
+++ gcc-6.3.0-B/gnattools/Makefile.in	2017-12-06 15:15:01.000000000 +0100
@@ -52,7 +52,7 @@ WARN_CFLAGS = @warn_cflags@
 ADA_CFLAGS=@ADA_CFLAGS@
 
 # Variables for gnattools.
-ADAFLAGS= -gnatpg -gnata
+ADAFLAGS= -gnata
 
 # For finding the GCC build dir, which is used far too much
 GCC_DIR=../gcc

[-- Attachment #4: gnat63-terminals.diff --]
[-- Type: text/x-patch, Size: 597 bytes --]

diff -rupN gcc-6.3.0-A/gcc/ada/terminals.c gcc-6.3.0-B/gcc/ada/terminals.c
--- gcc-6.3.0-A/gcc/ada/terminals.c	2016-02-12 00:53:54.000000000 +0100
+++ gcc-6.3.0-B/gcc/ada/terminals.c	2017-10-13 08:17:35.000000000 +0200
@@ -1068,12 +1068,6 @@ __gnat_setup_winsize (void *desc, int ro
 #include <stdio.h>
 #include <stdlib.h>
 
-/* On some system termio is either absent or including it will disable termios
-   (HP-UX) */
-#if !defined (__hpux__) && !defined (BSD) && !defined (__APPLE__) \
-  && !defined (__rtems__)
-#   include <termio.h>
-#endif
 
 #include <sys/ioctl.h>
 #include <termios.h>

      parent reply	other threads:[~2017-12-13  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-02  9:44 Successfull build of gnat-6.3.0 with musl-cross-make Didier Kryn
2017-11-05 18:01 ` Rich Felker
2017-11-05 20:35   ` Didier Kryn
2017-11-30 16:30 ` Building musl-cross-make with gnat in musl environement Didier Kryn
2017-11-30 17:06   ` Rich Felker
2017-12-01  7:31     ` Didier Kryn
2017-12-13  9:29     ` Didier Kryn [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ed07b18-e7ce-fc54-9498-d3123a506cc2@in2p3.fr \
    --to=kryn@in2p3.fr \
    --cc=musl@lists.openwall.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).