public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Re: ++ illegal in VMS filenames
@ 2001-12-08 14:14 Bruce Korb
  0 siblings, 0 replies; 2+ messages in thread
From: Bruce Korb @ 2001-12-08 14:14 UTC (permalink / raw)
  To: rupp; +Cc: gcc, aoliva

> cp/g++spec.c is an illegal filename on VMS, and there's no way to prevent
> "make LANGUAGES=c" from trying to compile it short of hacking the
> Makefile or completely removing the cp subdirectory before configure.

I would recommend grepping through the source tree for
non-posix file name characters, then finding those files
in the Makefile's & posting a rename + patch.

POSIX file name characters:  [a-zA-Z0-9_.-]
It's pretty constrained.  I thought this was
resolved, but I guess it has reared its head again.

^ permalink raw reply	[flat|nested] 2+ messages in thread

* ++ illegal in VMS filenames
@ 2001-12-08  9:38 Douglas B. Rupp
  0 siblings, 0 replies; 2+ messages in thread
From: Douglas B. Rupp @ 2001-12-08  9:38 UTC (permalink / raw)
  To: gcc

cp/g++spec.c is an illegal filename on VMS, and there's no way to prevent
"make LANGUAGES=c" from trying to compile it short of hacking the
Makefile or completely removing the cp subdirectory before configure.

Any flexibility on making the name configurable somehow? I'm not sure how to approach
this and would like some ideas,

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2001-12-08 17:38 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-12-08 14:14 ++ illegal in VMS filenames Bruce Korb
  -- strict thread matches above, loose matches on Subject: below --
2001-12-08  9:38 Douglas B. Rupp

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).