This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: building gold from release tarball requires bison?


On Wed, Aug 30, 2017 at 5:07 PM, Benjamin Peterson <bp@benjamin.pe> wrote:
> Hi,
> At least the binutils-2.29 tarball, the generated parser for
> gold/yyscript.y is not included, so building gold requires bison. Since
> other bison parsers (e.g., binutils/defparser.c) seem to be generated
> into the release tarball, am I correct in assuming this is an oversight
> in the release process? gold/README does promise "If you are building
> gold from an official binutils release,
> the bison output should already be included."
>

Hmm, I've not exactly pinpointed the problem, but thought I had tested
this before the commit for PR 18200,
https://sourceware.org/bugzilla/show_bug.cgi?id=18200
looking at the tarballs since then it doesn't appear that yyscript.c
has showed up in a release tarball since that was resolved.

Looks like my testing was flawed,

what I notice is that running ./configure; cd gold && ./configure; cd
..; ./src-release.sh -g binutils
seems to include yyscript.c, but running plain old top-level
configure; src-release.sh does not seem to include it in the resulting
tarball.

I have a feeling that the gold/Makefile is not being generated in the
src-release.sh machinery, and so its never hitting the "diststuff"
rule...

my guess is that the release process doesn't configure with both
linkers e.g. --enable-gold --enable-ld


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]