A relocated compiler should not look in $prefix.
A relocated compiler should never search the configured prefix for
programs, libraries or start files. A relocated compiler searching for
files in the configured prefix is troublesome. The configured prefix may
contain a conflicting toolchain, or a
"Carlos O'Donell" <[EMAIL PROTECTED]> writes:
> A relocated compiler should not look in $prefix.
I agree.
I can't approve your patches, though.
Ian
Ian Lance Taylor wrote:
"Carlos O'Donell" <[EMAIL PROTECTED]> writes:
A relocated compiler should not look in $prefix.
I agree.
I can't approve your patches, though.
This patch is OK, once we reach Stage 1.
--
Mark Mitchell
CodeSourcery
[EMAIL PROTECTED]
(650) 331-3385 x713
On Mon, Oct 16, 2006 at 03:32:27PM -0700, Mark Mitchell wrote:
> Ian Lance Taylor wrote:
> >"Carlos O'Donell" <[EMAIL PROTECTED]> writes:
> >
> >>A relocated compiler should not look in $prefix.
> >
> >I agree.
> >
> >I can't approve your patches, though.
>
> This patch is OK, once we reach Stage
On Fri, 2006-10-13 at 12:51 -0400, Carlos O'Donell wrote:
> A relocated compiler should not look in $prefix.
> Comments?
> OK for Stage1?
I do have another issue with these set of patches which I did not notice
until today.
I can no longer do inside a just built GCC do:
./cc1 t.c
or
./xgcc -B. t.c
Andrew Pinski wrote:
> On Fri, 2006-10-13 at 12:51 -0400, Carlos O'Donell wrote:
>> A relocated compiler should not look in $prefix.
>> Comments?
>> OK for Stage1?
>
> I do have another issue with these set of patches which I did not notice
> until today.
> I can no longer do inside a just built G
What are the contents of t.c? What if you set GCC_EXEC_PREFIX?
t.c:
#include
int main(void)
{
printf("Hello World\n");
return 0;
}
--
No I did not set GCC_EXEC_PREFIX as I did not know I have to set that now.
Seems like a change like this should be mentioned on
http://gcc.gnu.org/gcc-4
Andrew Pinski wrote:
>> What are the contents of t.c? What if you set GCC_EXEC_PREFIX?
>
> t.c:
>
> #include
> int main(void)
> {
> printf("Hello World\n");
> return 0;
> }
>
> --
> No I did not set GCC_EXEC_PREFIX as I did not know I have to set that now.
> Seems like a change like this
>
> Andrew Pinski wrote:
> >> What are the contents of t.c? What if you set GCC_EXEC_PREFIX?
> >
> > t.c:
> >
> > #include
> > int main(void)
> > {
> > printf("Hello World\n");
> > return 0;
> > }
> >
> > --
> > No I did not set GCC_EXEC_PREFIX as I did not know I have to set that now.
Andrew Pinski wrote:
> But other non user-visible changes are mentioned on changes.html already.
> Forward prop in 4.3.
> Incompatible changes to the build system in 4.2 which seems very related to
> stuff like
> this.
If you want to make a patch, and Gerald approves it, it's fine by me.
But, fw
On Tue, 12 Dec 2006, Mark Mitchell wrote:
> If you want to make a patch, and Gerald approves it, it's fine by me.
> But, fwprop is described as a new feature (faster compiler, better
> code), and the build system affects people building the compiler. The
> change we're talking about seems to affec
11 matches
Mail list logo
