| Summary: | ppp-2.4.1-r14 fails with unescaped multi-line string | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Jim Bray <jb> |
| Component: | [OLD] Core system | Assignee: | Chuck Brewer <cbrewer> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 1.4_rc2 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Jim Bray
2003-05-23 10:17:19 UTC
I hate to say this, but gcc 3.3 is still most of a hack, which is why it's still in packages.mask. Have you gotten any version to build with 3.3? The source hasn't changed since before -r6 and everything I've done to it lately has been cosmetic, really, besides adding in the pppoatm plugin (which is why I committed r14).My only suggestion atm is to roll back to gcc-3.2.3-20030422 which is the latest Ive gotten it to build with. Well, the code will need to be changed sooner or later. Might want to tell upstream. http://gcc.gnu.org/gcc-3.3/changes.html GCC 3.3 Release Series Changes, New Features, and Fixes Caveats * The preprocessor no longer accepts multi-line string literals. They were deprecated in 3.0, 3.1, and 3.2. http://bugs.gentoo.org/show_bug.cgi?id=21551 Jim, if you get a chance, can you try out the redone r14? lu_zero added a gcc 3.3 patch for that, and I could use the input:) Built and installed without incident. I suspect you'll see a lot of these string bugs with gcc-3.3. Lots of code-cleanups will be triggered by this. gcc-3.3 seems to be solid as far as c is concerned. I'm not sure about the g++ yet. Building the Lizard should be revealing. Okay, I'm gonna close this one then. As soon I get a chance I really need to revamp this whole pckage, and push upstream for a new release, sicne theres atleast 15 patches against it so far I'd like to see in a new release. I'll give r14 the customary 2 weeks and push it stable, thanks:) |