[LLVMdev] Path to AutoRegen.sh
tonic at nondot.org
Fri May 9 23:21:24 CDT 2008
On May 7, 2008, at 10:57 AM, Alexandre Machado wrote:
> Hy, Tanya
>> Some comments:
>> - Please follow the developers policy for making patches:
> OK. My fault here. Will check some of your observations and resubmit.
>> - I think if we are going to upgrade, we should totally switch to 2.6
>> instead of allowing both. This will make diffs easier to read when
>> regenerate the configure script.
> Agree... but we must be sure if it does not brake anything. I'm
> out of time with the current project, but, after it finishes, can look
>> - Did you read autoconf/README.txt? Were there no changes to the m4
>> macros or configure.ac?
> Well... at least there where no changes in macros used by the sample
> project. But, if we are meant to migrate the whole LLVM to 2.6, I need
> to investigate it further.
Ah, my fault. I thought you were talking about the top level
AutoRegen.h. This is probably much simpler then. LLVM already uses
>> - You should also regenerate the configure script as part of this
Ignore this too. No configure to regenerate.
>> - Does libtool also have to be upgraded?
> Don't know. I'm using 1.5.24, but don't know if it will work with
> versions. It's another think I need to check.
>> - Lastly, I think we should postpone applying this patch until
>> after the
>> 2.3 branch creation. I'm leary of making tool changes so close to the
> Agree. Sent it just because, as a beginner with LLVM, it was a pain to
> start a new project in my environment, and I know there are a lot of
> other ubuntu users out there, but it's not necessary to hurry.
I'll see about getting this integrated after 2.3. Thanks!
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the LLVMdev