From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6292 invoked by alias); 6 Jun 2014 14:21:32 -0000 Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org Received: (qmail 6281 invoked by uid 89); 6 Jun 2014 14:21:31 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-4.4 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 06 Jun 2014 14:21:29 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s56ELRQf011046 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Fri, 6 Jun 2014 10:21:27 -0400 Received: from host2.jankratochvil.net (ovpn-116-48.ams2.redhat.com [10.36.116.48]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id s56ELOCf011386 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NO); Fri, 6 Jun 2014 10:21:26 -0400 Date: Fri, 06 Jun 2014 14:21:00 -0000 From: Jan Kratochvil To: Sergio Durigan Junior Cc: Yao Qi , gdb-patches@sourceware.org Subject: Re: [patch] Fix TLS access for -static -pthread Message-ID: <20140606142123.GB5187@host2.jankratochvil.net> References: <20140410115204.GB16411@host2.jankratochvil.net> <539018F9.5060307@codesourcery.com> <20140605080639.GA32146@host2.jankratochvil.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-IsSubscribed: yes X-SW-Source: 2014-06/txt/msg00328.txt.bz2 On Fri, 06 Jun 2014 07:34:17 +0200, Sergio Durigan Junior wrote: > On Thursday, June 05 2014, Jan Kratochvil wrote: > > Sergio said he saw some problem with mktemp symbol on some Fedora but I do not > > have that reproducible so I cannot fix it. > > I saw this: > > Executing on host: gcc ../../../gdb/testsuite/gdb.threads/staticthreads.c -static -DHAVE_TLS -g -lpthread -lm -o /patch/to/gdb/testsuite/gdb.threads/staticthreads (timeout = 300) > spawn -ignore SIGHUP gcc ../../../gdb/testsuite/gdb.threads/staticthreads.c -static -DHAVE_TLS -g -lpthread -lm -o /patch/to/gdb/testsuite/gdb.threads/staticthreads^M > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':^M > (.text+0x774d): warning: the use of `mktemp' is dangerous, better use `mkstemp'^M > output is: > /usr/lib/gcc/x86_64-redhat-linux/4.4.7/../../../../lib64/libpthread.a(libpthread.o): In function `sem_open':^M > (.text+0x774d): warning: the use of `mktemp' is dangerous, better use `mkstemp'^M > > This is on RHEL-6.5, with gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-4). > > I had to do a small workaround in gdb_compile_pthreads (from > testsuite/lib/gdb.exp) in order to make the compilation succeed. OK, that may be nice to also submit upstream - but according to the Yao's mail Message-ID: <53915C44.3010904@codesourcery.com> it is unrelated to the problem being discussed in this thread. Sorry for my wrong expectation. Jan