Mailing List Archive: Perl: porters

[RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp.

Index | Next | Previous | View Threaded

impulze at impulze

Nov 3, 2009, 1:03 PM

Post #1 of 9 (338 views)
Permalink

[RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp.

Hi I wanted to propose a patch to use the supplied preprocessor "-Dcpp"
instead of a hardcoded "cpp" binary. Say when you want to use clang or
something else you can use the clang C preprocessor instead of the most
likely system-wide gcc C preprocessor.
Is this a reasonable change or does it need some other tweaks? I'm all
open for discussion, thanks for reading.

--
Mierswa, Daniel

If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22

Attachments:

perl-66387e83d.patch (0.96 KB)

t.jenness at jach

Nov 3, 2009, 1:25 PM

Post #2 of 9 (324 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On Nov 3, 2009, at 11:03 AM, Daniel Mierswa wrote:

> Hi I wanted to propose a patch to use the supplied preprocessor "-
> Dcpp" instead of a hardcoded "cpp" binary. Say when you want to use
> clang or something else you can use the clang C preprocessor instead
> of the most likely system-wide gcc C preprocessor.

Does that explain why clang completely fails to build perl? I had
tried it when I got my Snow Leopard system but it broke almost
immediately and I hadn't gotten around to asking about it.

--
Tim Jenness
Joint Astronomy Centre

h.m.brand at xs4all

Nov 3, 2009, 2:19 PM

Post #3 of 9 (324 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On Tue, 3 Nov 2009 11:25:22 -1000, Tim Jenness
<t.jenness [at] jach> wrote:

>
> On Nov 3, 2009, at 11:03 AM, Daniel Mierswa wrote:
>
> > Hi I wanted to propose a patch to use the supplied preprocessor "-
> > Dcpp" instead of a hardcoded "cpp" binary. Say when you want to use
> > clang or something else you can use the clang C preprocessor instead
> > of the most likely system-wide gcc C preprocessor.
>
> Does that explain why clang completely fails to build perl? I had
> tried it when I got my Snow Leopard system but it broke almost
> immediately and I hadn't gotten around to asking about it.

Sounds sane anyway, so I applied it to meta. Will be in the next
generated Configure.

I've got two open issues: 8/9bit characters, and another piece being
dragged in by something yet unknown to me.

--
H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, OpenSuSE 10.3, 11.0, and 11.1, AIX 5.2 and 5.3.
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/
http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/

doughera at lafayette

Nov 3, 2009, 2:49 PM

Post #4 of 9 (320 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On Tue, 3 Nov 2009, Tim Jenness wrote:

>
> On Nov 3, 2009, at 11:03 AM, Daniel Mierswa wrote:
>
> > Hi I wanted to propose a patch to use the supplied preprocessor "-Dcpp"
> > instead of a hardcoded "cpp" binary. Say when you want to use clang or
> > something else you can use the clang C preprocessor instead of the most
> > likely system-wide gcc C preprocessor.
>
> Does that explain why clang completely fails to build perl? I had tried it
> when I got my Snow Leopard system but it broke almost immediately and I hadn't
> gotten around to asking about it.

I doubt it. I think that part is only building the list of cpp symbols,
which I don't think we end up using anyway.
Of course it's a long time since I looked at that part of Configure, so I
could be completely wrong.

--
Andy Dougherty doughera [at] lafayette

doughera at lafayette

Nov 3, 2009, 2:50 PM

Post #5 of 9 (322 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On Tue, 3 Nov 2009, H.Merijn Brand wrote:

> On Tue, 3 Nov 2009 11:25:22 -1000, Tim Jenness
> <t.jenness [at] jach> wrote:
>
> >
> > On Nov 3, 2009, at 11:03 AM, Daniel Mierswa wrote:
> >
> > > Hi I wanted to propose a patch to use the supplied preprocessor "-
> > > Dcpp" instead of a hardcoded "cpp" binary. Say when you want to use
> > > clang or something else you can use the clang C preprocessor instead
> > > of the most likely system-wide gcc C preprocessor.
> >
> > Does that explain why clang completely fails to build perl? I had
> > tried it when I got my Snow Leopard system but it broke almost
> > immediately and I hadn't gotten around to asking about it.
>
> Sounds sane anyway, so I applied it to meta. Will be in the next
> generated Configure.

Sounds good.

> I've got two open issues: 8/9bit characters, and another piece being
> dragged in by something yet unknown to me.

I also was working on moving the ldlibpth stuff from Makefile.SH to
metaconfig, but I got stalled and ran out of time, so I hope you're not
waiting on anything from me.

--
Andy Dougherty doughera [at] lafayette

impulze at impulze

Nov 3, 2009, 4:39 PM

Post #6 of 9 (319 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On 03.11.2009 22:25, Tim Jenness wrote:
> Does that explain why clang completely fails to build perl? I had tried
> it when I got my Snow Leopard system but it broke almost immediately and
> I hadn't gotten around to asking about it.

Builds and runs fine here.

--
Mierswa, Daniel

If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22

t.jenness at jach

Nov 3, 2009, 5:20 PM

Post #7 of 9 (316 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On Nov 3, 2009, at 2:39 PM, Daniel Mierswa wrote:

> On 03.11.2009 22:25, Tim Jenness wrote:
>> Does that explain why clang completely fails to build perl? I had
>> tried
>> it when I got my Snow Leopard system but it broke almost
>> immediately and
>> I hadn't gotten around to asking about it.
>
> Builds and runs fine here.

with blead?

This was with straight Snow Leopard and blead of the day. Had a
problem with cv.h.

Sorry, can't dig out the error message at the moment but if it all
works fine then I'm happy.

--
Tim Jenness
Joint Astronomy Centre

impulze at impulze

Nov 3, 2009, 5:22 PM

Post #8 of 9 (316 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On 04.11.2009 02:20, Tim Jenness wrote:
> with blead?
Sorry if I caused confusion on that matter, but I was merely refering to
clang building perl. I'm not even on MacOS, but Linux here. I was merely
trying to state that clang builds Perl just fine, at least here. :)

--
Mierswa, Daniel

If you still don't like it, that's ok: that's why I'm boss. I simply
know better than you do.
--- Linus Torvalds, comp.os.linux.advocacy, 1996/07/22

h.m.brand at xs4all

Nov 3, 2009, 11:36 PM

Post #9 of 9 (308 views)
Permalink

Re: [RFC][PATCH] Use supplied C preprocessor instead of hardcoded cpp. [In reply to]

On Tue, 3 Nov 2009 17:50:32 -0500 (EST), Andy Dougherty
<doughera [at] lafayette> wrote:

> On Tue, 3 Nov 2009, H.Merijn Brand wrote:
> > On Tue, 3 Nov 2009 11:25:22 -1000, Tim Jenness <t.jenness [at] jach> wrote:
> > > On Nov 3, 2009, at 11:03 AM, Daniel Mierswa wrote:
> > >
> > > > Hi I wanted to propose a patch to use the supplied preprocessor "-
> > > > Dcpp" instead of a hardcoded "cpp" binary. Say when you want to use
> > > > clang or something else you can use the clang C preprocessor instead
> > > > of the most likely system-wide gcc C preprocessor.
> > >
> > > Does that explain why clang completely fails to build perl? I had
> > > tried it when I got my Snow Leopard system but it broke almost
> > > immediately and I hadn't gotten around to asking about it.
> >
> > Sounds sane anyway, so I applied it to meta. Will be in the next
> > generated Configure.
>
> Sounds good.
>
> > I've got two open issues: 8/9bit characters, and another piece being
> > dragged in by something yet unknown to me.
>
> I also was working on moving the ldlibpth stuff from Makefile.SH to
> metaconfig, but I got stalled and ran out of time, so I hope you're not
> waiting on anything from me.

No, I'm not.

--
H.Merijn Brand http://tux.nl Perl Monger http://amsterdam.pm.org/
using & porting perl 5.6.2, 5.8.x, 5.10.x, 5.11.x on HP-UX 10.20, 11.00,
11.11, 11.23, and 11.31, OpenSuSE 10.3, 11.0, and 11.1, AIX 5.2 and 5.3.
http://mirrors.develooper.com/hpux/ http://www.test-smoke.org/
http://qa.perl.org http://www.goldmark.org/jeff/stupid-disclaimers/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads