Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Request to remove dependance on sed/flex/bison #986

Closed
llvmbot opened this issue Aug 5, 2005 · 4 comments
Closed

Request to remove dependance on sed/flex/bison #986

llvmbot opened this issue Aug 5, 2005 · 4 comments
Labels
bugzilla Issues migrated from bugzilla enhancement Improving things as opposed to bug fixing, e.g. new or missing feature quality-of-implementation

Comments

@llvmbot
Copy link
Collaborator

llvmbot commented Aug 5, 2005

Bugzilla Link 614
Resolution FIXED
Resolved on Feb 22, 2010 12:48
Version trunk
OS All
Reporter LLVM Bugzilla Contributor
CC @lattner

Extended Description

I posted this to the list, and also talked to you guys on irc, and was asked to
submit a feature request. Here is my original message:

At the moment, LLVM includes the .l, .y sources that are compiled by
flex and biston via make. This is fine for most unix developers. For
windows developers, it's a bit more of a pain to download flex/bison,
but is still a one-time thing.

However, anyone releasing an llvm frontend will require their users to
have flex/bison. Most (but not all) unix boxes have them, but almost
no windows boxes have them. This requires either

  1. Forcing the user to dowload flex/bison (bad)

  2. Distributing flex/bison with the front-end (not as bad, but a pain)

  3. or, and this seems like a simple fix, just distribute the output of
    flex and bison along with the source. This is analagous to
    distributing "configure" along with "configure.ac".

The right solution is obviosly the 3'd one
@lattner
Copy link
Collaborator

lattner commented Aug 5, 2005

FWIW, I totally agree. We just need someone to whip up a patch :)

@llvmbot
Copy link
Collaborator Author

llvmbot commented Aug 11, 2005

Mine

@llvmbot
Copy link
Collaborator Author

llvmbot commented Aug 11, 2005

A quick look at this indicates that it isn't completely trivial to save the
output of flex/bison in the sources. When OBJDIR != SRCDIR, flex gets confused
and code changes are required. This is going to take some monkeying around so
I'll have to wait until the weekend to resolve this.

Reid.

@llvmbot
Copy link
Collaborator Author

llvmbot commented Aug 27, 2005

Implemented. Patches are here:

http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050822/027982.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050822/027983.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050822/027984.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050822/027985.html
http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20050822/027986.html

@llvmbot llvmbot transferred this issue from llvm/llvm-bugzilla-archive Dec 3, 2021
@Endilll Endilll added enhancement Improving things as opposed to bug fixing, e.g. new or missing feature and removed new-feature labels Aug 15, 2023
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugzilla Issues migrated from bugzilla enhancement Improving things as opposed to bug fixing, e.g. new or missing feature quality-of-implementation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Endilll @lattner @llvmbot