[lldb-dev] Compiling LLDB on Linux, certain types don't exist at all?

austin seipp as at hacks.yi.org
Tue Dec 14 18:32:24 PST 2010


I've replaced & forked your repository on github and have a change
that will let it LLDB compile under gcc 4.5. Also tested your branch
with this change on OS X snow leopard with xcodebuild.
Also I fixed a build failure for gcc 4.3 on my linux machine and
tested it w/ xcodebuild on OS X.

I'll also be putting warning cleanups and whatnot on my lldb-linux
branch. I suppose the easiest way would be for you to just pull them
(pull requests?) into your branch so they can be put into SVN trunk
soon. Git doesn't seem to track the git-svn metadata associated with
the original svn repository, since I am working from a clone of your
repository (since I want your changes,) so I can't easily 'svn rebase'
my master branch and then merge to update my trunk - I'm basically
left to tracking your repository at the moment. I'll have to figure
that one out until the svn trunk builds cleanly on linux.


On Tue, Dec 14, 2010 at 6:15 PM, Stephen Wilson <wilsons at start.ca> wrote:
> Hi Austin,
> austin seipp <as at hacks.yi.org> writes:
>> Stephen,
>> Thank you for the follow-up, I figured I was not the only person
>> interested in this. re: the build issue, I assume the Makefiles on
>> linux just blindly compile all *.cpp files in the current directory,
>> whereas xcode project configurations will explicitly enumerate the
>> files that need to be built, so unused files are not a problem. I
>> assume nobody has used the makefiles for quite some time, so they've
>> fallen out of date (indeed, the commit logs say they have not been
>> touched for a while.)
>> Hopefully your changes can get merged soon. If you publish your git
>> repository before then (or after, if you plan on continuing working on
>> linux support,) please be sure to follow up with a URL so we could
>> collaborate in the future if you don't mind. I'd like to see LLDB on
>> Linux as I have gradually been moving all my personal code and
>> machines to Clang, and I do most of my development on Linux, not on OS
>> X. Once your changes are merged, more interesting things can be worked
>> on (and hopefully kept in sync with the tree.)
> I pushed the current state of my tree onto the lldb-linux branch here:
>   https://github.com/eightcien/lldb/tree/lldb-linux
> I have not thoroughly reviewed all of the changes myself -- but the tree
> does build.  Will be picking the critical commits out and sending them
> to the list for review over the next few days (I hope).
> I probably will not be looking at adding any features to the linux side
> of things for a while -- just concentrate on getting the build working
> and cleaning up as many compilation warnings as I can.  Will keep the
> github tree up to date as I work.
> Take care,
>>> If you use master to track the svn repo I would recommend that you do
>>> not rebase your "linux" branch -- just update master using 'git svn
>>> rebase' which should always be a simple fast-forward and pull those
>>> changes into the "linux" branch using a merge commit.  That way you have
>>> a proper history that others using git can pull from while staying up to
>>> date.  Of course, you would need to manage any merge-conflicts, etc.
>> This sounds like a much better idea and I can't believe I hadn't
>> thought of it, thanks.
>> Regards,
>> Austin
> --
> steve

More information about the lldb-dev mailing list