summaryrefslogtreecommitdiff
path: root/cflags.SH
Commit message (Collapse)AuthorAgeFilesLines
* Exempt clang from -Wunused-value when run as ccFather Chrysostomos2013-07-281-0/+9
| | | | | | | We already have an exception for it when called as clang or clang-1.2.3, but not when called as cc or anything else. Mac OS X Mountain Lion therefore ends up spitting out lots of warnings, as cc is a symlink to clang.
* Use -Wno-unused-value also on other clang compilersReini Urban2013-06-271-1/+1
| | | | clang++ or clang-3.2, ...
* If PERL_NO_INLINE_FUNCTIONS is defined, don't include "inline.h"Nicholas Clark2013-05-031-1/+1
| | | | | | | | | | | | | | This permits test code to include the perl headers for definitions without creating a link dependency on the perl library (which may not exist yet). Some of the static inline functions in inline.h reference functions in the perl object files, and some compilers aren't smart enough to eliminate unused static inline functions, hence including the inline.h in probe code can cause link errors even though the probe code uses none of the functions it declares. When probing, a failed link is taken as meaning that the probed-for function is not present, as the assumption is that the link fails because of it. Hence other causes of link failures cause the probing code to generate incorrect results, and action (and bugs) at a distance.
* add shebangs where missingSawyer X2012-09-221-0/+2
|
* In cflags.SH trim the case statement of file basenames.Nicholas Clark2012-06-191-47/+14
| | | | | | | | | | | | | | Add examples showing how to use cflags.SH to tweak the compiler flags used for individual object files. Previously cflags.SH contained a somewhat stale pre-canned list of file basenames including removed files such as usersub (deleted before 5.000 shipped), and a partial list of 5.000 XS extensions. Whilst it's possible to generate the correct list in cflags by parsing MANIFEST (and adding a few fixups), it's still not actually *useful*, as cflags gets overwritten as soon as config.sh changes. Hence the most end-user useful solution with minimal maintenance is to eliminate the list entirely, and document how the user should add to it as necessary.
* cflags: clang complains a lot about -Wunused-value which are not fixableReini Urban2012-06-081-0/+4
|
* Make everything exec-bit.txt lists executableFlorian Ragwitz2010-08-191-0/+0
| | | | | | | All these files used to be executable in the release tarballs. Apparently things also work without that in the repository, but I'd rather add this possibly unecessary change to blead instead of breaking the upcoming release. This should probably be looked into again afterwards.
* RT #74436: [PATCH] Add -Wwrite-stringsRobin Barker2010-08-141-1/+2
| | | | | | The perl source has for some while been clean to -Wwrite-strings. I suggest this warning be added to cflags. The patch makes the appropriate change to cflags.SH and silences a warning from mg.c
* Global executable bit cleanupDavid Golden2010-07-241-0/+0
| | | | | | | | | | | | | | | | | | | | When porting/makerel runs, all files copied into the directory for the tarball have the executable bit stripped and then only a specific set of files have the executable bit restored. There are many files in the repo that have the executable bit set in the repo that will be stripped. So that the state of files in the repo is as close as possible to the state of files in the release tarball, the executable bit has been stripped from such files. In one recent case, a file added from a dual-life module needed the executable bit set. Because it had the bit in the repo but was not listed in makerel to get an executable bit, tests using it passed in the repo and failed in the tarball. This commit refactors the list into a new file, Porting/exec-bit.txt and add tests to detect a mismatch between files listed there and actual executable bits in the repo.
* Convert xsutils.c and lib/attributes.pm to a regular XS extension.Nicholas Clark2009-04-121-1/+0
|
* eliminate .patchnum and related infrastrcuture from *nix based build processYves Orton2009-01-041-8/+3
| | | | Rename the old "unpushed.h" to "git_version.h" and make it hold the defines that used to come from cflags magic
* cflags also runs under /bin/sh so can't use $()Nicholas Clark2008-12-301-4/+4
|
* much better git related version numbering in our (*nix for now) build processYves Orton2008-12-311-5/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The net result of this patch is to make available via Config.pm and -v/-V the details about the git version info we have available for the build. When built within a git repository git is queried directly. When built from a snapshot or bundle it is assumed that the source is unchanged, and that the required details are avaialble in a file called .patch, whose format current is a four field string in the following format: "$branchname $date.$time $sha1 $describe". The generator of these files currently resides on camel.booking.com. * git-describe is now used more directly with -v. When the prefix of git-describe matches the version number as determined by the defines in patchlevel.h then we use ONLY the git-describe output, otherwise we include the git describe in parenthesis after the version number. Either way the describe text is optionally followed by a star should there be uncommitted changes. eg: This is perl, v5.11.0 (GitLive-blead-136-g58ca560) built for i686-linux or: This is perl, v5.11.0-1-g58ca560 built for i686-linux or: This is perl, v5.11.0 built for i686-linux * include the SHA1 in perl -V summary, and automatically include unpushed commits in the registered patches list * include various git/version/.patch details in %Config, as follows: git_commit_id # sha1 of HEAD git_ancestor # ancestor in $remote/$branch (presumably canonical) git_describe # git describe git_branch # current branch git_uncommitted_changes # "true" if there are any, empty otherwise git_unpushed_commits # List of sha1's of unpushed commits git_commit_id_title # Used to make the perl -V summary output Additionally one more value is added depending on build process used: when building from an rsynced snapshot (or any dist including a file called .patch) then the second field will be used to populate the "git_snapshot_date" field. Otherwise if built in a git directory (as is hopefully recommended these day) then the field will be "git_commit_date" which will be the commit date of HEAD. This patch introduces two new files (on top of .patchnum) that will be generated by make_patchnum.sh: "lib/Config_git.pl" and "unpushed.h", the former is used to make git data available to Config.pm/%Config without rebuilding everything else, and the second is used to expose unpushed commits (if any) via the registered patch facility of patchlevel.h
* forgot that i was modifying a generated fileYves Orton2008-12-271-0/+3
|
* fix broken indentation, and move PERL_PATCHNUM logic to a different place so ↵Yves Orton2008-12-271-35/+37
| | | | it only affects perl.c
* more build dependency changes, we should make sure that cflags is updated ↵Yves Orton2008-12-271-1/+1
| | | | whenever cflags.SH changes
* make sure that the perl -v/-V output corresponds to the latest commitYves Orton2008-12-271-6/+2
|
* /bin/sh isn't /usr/bin/perl :-)Nicholas Clark2008-12-201-2/+4
| | | | | | Change elsif to the correct "else if" construction. I suspect that this slipped by into f6a80292c3db127d1561c118f409c1cffd1b55d9 because cflags.SH doesn't seem to be re-expanded if it's newer than cflags.
* make perl use git-describe for PATCHNUMYves Orton2008-12-201-2/+4
| | | | | | | | | | | This is just an initial attempt at getting something more useful into the -v / -V output. Currently "patchlevel" is really "version", and PATCHNUM is just a special string added to the patchlevel in perl.c via defines created by cflags.SH and its product file cflags, which happens very early in the build process. This means that for committers the -v output is likely to not be upto date unless they run make clean. Anyway, IMO we should rethink a reasonable amount about how we do this, this is just a crude step forward.
* Make struct regexp the body of SVt_REGEXP SVs, REGEXPs become SVs,Nicholas Clark2008-01-021-1/+1
| | | | | | and regexp reference counting is via the regular SV reference counting. This was not as easy at it looks. p4raw-id: //depot/perl@32804
* A new try at getting -fstack-protector working, by adding it to theNicholas Clark2007-12-201-1/+1
| | | | | | gcc link flags so that any implementation dependant libraries are also linked in. p4raw-id: //depot/perl@32669
* Teach cflags.SH about -fstack-protector, and add it to gcc compiler flagsSteve Peters2007-12-191-1/+1
| | | | | when possible. p4raw-id: //depot/perl@32647
* typo?Robin Barker2007-12-171-1/+1
| | | | | | From: "Robin Barker" <Robin.Barker@npl.co.uk> Message-ID: <46A0F33545E63740BC7563DE59CA9C6D09398B@exchsvr2.npl.ad.local> p4raw-id: //depot/perl@32623
* Re: [perl #46725] v5.10.0 util.c and pp_sys.c fail to compile under Mac OS XAndy Dougherty2007-10-231-9/+9
| | | | | | Message-ID: <Pine.LNX.4.64.0710230817250.18303@fractal.phys.lafayette.edu> Date: Tue, 23 Oct 2007 08:54:51 -0400 (EDT) p4raw-id: //depot/perl@32181
* FreeBSD atoll() warning (Was Re: Code freezeAndy Dougherty2007-10-221-3/+31
| | | | | | Message-ID: <Pine.LNX.4.64.0710221246340.31725@fractal.phys.lafayette.edu> Date: Mon, 22 Oct 2007 12:49:25 -0400 (EDT) p4raw-id: //depot/perl@32174
* get rid of cygwin perlld and ld2Reini Urban2007-08-141-0/+1
| | | | | Message-Id: <46C15106.9080003@x-ray.at> p4raw-id: //depot/perl@31710
* cflags.SH: 30327 wasn't portable Bourne (avoid '!: not found')Jarkko Hietaniemi2007-03-301-1/+1
| | | | | Message-Id: <200703300144.l2U1iBSA490663@kosh.hut.fi> p4raw-id: //depot/perl@30779
* Make gcc warn in case code is not C++ compatible.Steve Peters2007-03-211-1/+1
| | | p4raw-id: //depot/perl@30672
* Avoid to run config_h.SH twice during configuration.Rafael Garcia-Suarez2007-02-161-1/+2
| | | p4raw-id: //depot/perl@30327
* Quote fix by JarkkoRafael Garcia-Suarez2007-02-051-1/+1
| | | p4raw-id: //depot/perl@30125
* cflags.SH was broken: it was compiling a C file for testing availableRafael Garcia-Suarez2007-01-261-0/+4
| | | | | | | command-line options, but this C file was including perl.h, which in turn includes config.h, which might not be present at that time. So force the generation of config.h. p4raw-id: //depot/perl@30019
* If we have specified -Dgccansipedantic on the Configure command-line,Rafael Garcia-Suarez2007-01-261-10/+12
| | | | | assume we really want it p4raw-id: //depot/perl@30016
* Typo fix (by Dominic Dunlop)Rafael Garcia-Suarez2006-11-281-2/+2
| | | p4raw-id: //depot/perl@29400
* Re: [PATCH] perlhack: some portability updatesDominic Dunlop2006-11-281-1/+1
| | | | | Message-Id: <253514EB-BA57-4A43-93FA-75D6F3CF27BC@mac.com> p4raw-id: //depot/perl@29398
* cflags.SH: strip -std=c89 for g++Jarkko Hietaniemi2006-10-071-21/+26
| | | | | Message-ID: <45278350.8020707@iki.fi> p4raw-id: //depot/perl@28955
* Re: [PATCH] cflags.SH: rethink of the gcc -std=c89 and -pedanticJarkko Hietaniemi2006-10-021-47/+109
| | | | | Message-ID: <4520E41E.8040300@iki.fi> p4raw-id: //depot/perl@28914
* C++: add -Wno-used-parameter, and drop ODBM_FileJarkko Hietaniemi2006-09-191-4/+8
| | | | | Message-ID: <450F8BEA.1010802@iki.fi> p4raw-id: //depot/perl@28867
* (1) g++ 4.x (or Mac OS X) (2) Solaris g++ or CCJarkko Hietaniemi2006-09-141-1/+20
| | | | | | | Message-ID: <45083D88.7050207@iki.fi> Plus a tweak to the name of CC. p4raw-id: //depot/perl@28842
* g++ stage 1 reachedJarkko Hietaniemi2006-08-081-0/+4
| | | | | Message-ID: <44D7AA6B.4040802@iki.fi> p4raw-id: //depot/perl@28674
* g++ large patchJarkko Hietaniemi2006-08-071-8/+4
| | | | | Message-ID: <44D2E203.5050201@iki.fi> p4raw-id: //depot/perl@28662
* g++ heavy shovelingJarkko Hietaniemi2006-08-021-2/+18
| | | | | Message-ID: <44CFC1EA.2050702@iki.fi> p4raw-id: //depot/perl@28645
* Remove the C89 checking with gccRafael Garcia-Suarez2006-07-171-15/+0
| | | | | (but leave a note in perlhack) p4raw-id: //depot/perl@28595
* Cygwin doesn't cope (yet) with gcc flags -std=c89H.Merijn Brand2006-07-171-1/+4
| | | p4raw-id: //depot/perl@28592
* cflags.SH: add missing C filesJarkko Hietaniemi2006-07-151-0/+8
| | | | | Message-ID: <44B8B5B1.2050902@iki.fi> p4raw-id: //depot/perl@28577
* Re: [PATCH] cflags.SH: add -std=c89Jarkko Hietaniemi2006-07-151-5/+22
| | | | | Message-ID: <44B8B331.8090009@iki.fi> p4raw-id: //depot/perl@28576
* Don't add extra warning flags for gcc versions < 3.Rafael Garcia-Suarez2006-07-051-0/+1
| | | p4raw-id: //depot/perl@28483
* cflags.SH: scan the gcc warning flags only once, during .SH expansionJarkko Hietaniemi2006-06-271-70/+75
| | | | | Message-Id: <20060626191237.8A0936CF04@seth.hut.fi> p4raw-id: //depot/perl@28434
* RE: [PATCH] cflags.SH: rework the gcc warnings selectionPaul Green2006-06-191-1/+3
| | | | | | From: "Green, Paul" <Paul.Green@stratus.com> Message-ID: <F5F42E77A43DD944B6D664B00A5401CB02026106@EXNA.corp.stratus.com> p4raw-id: //depot/perl@28402
* cflags.SH: rework the gcc warnings selectionJarkko Hietaniemi2006-06-151-3/+29
| | | | | Message-ID: <4490FA65.70006@iki.fi> p4raw-id: //depot/perl@28397
* Experiment with putting the F<.patch>level into patchlevel.hNicholas Clark2005-09-101-0/+4
| | | | | (a sure way to accelerate any change to subversion) p4raw-id: //depot/perl@25374
View Lorry Controller Status