I've downloaded the current GPC tar file, unpacked it, and moved (actually symlinked) the p/ directory into gcc-2.95.2/ (which is the unpacked source of the current gcc).
Now your INSTALL file tells me to patch gcc with the appropriate p/diffs/*** Which one do I need? There are only ones for old gcc's.. Or is it unnecessary to patch 2.95.x at all ?
{{if not, couldn't you have the gcc developers adopt your patches? it would make gpc MUCH MORE reputable if one wouldn't have to patch such a widely used and approved piece of software as gcc .... }}
{Your FAQ dates from 1997, which made me not look at it, at all..}
Thank you for GPC (and your answers..)!
Hallo, Martin!
I've downloaded the current GPC tar file, unpacked it, and moved (actually symlinked) the p/ directory into gcc-2.95.2/ (which is the unpacked source of the current gcc).
I remember some problems with symlinks - better move it.
Furthermore, it belongs into the "gcc" subdirectory of gcc-2.95.2.
Now your INSTALL file tells me to patch gcc with the appropriate p/diffs/*** Which one do I need? There are only ones for old gcc's.. Or is it unnecessary to patch 2.95.x at all ?
You can patch it with the same diff as 2.95.1.
{{if not, couldn't you have the gcc developers adopt your patches? it would make gpc MUCH MORE reputable if one wouldn't have to patch such a widely used and approved piece of software as gcc .... }}
The patch only inserts some
#ifdef GPC /* code for GPC ... */ #endif
into the GCC source. Other languages will not see this code.
But we are working towards full integration (which you can see from the decreasing sizes of the patches).
{Your FAQ dates from 1997, which made me not look at it, at all..}
A new version of the FAQ is in preparation. Please search the list archives for it.
Thank you for GPC (and your answers..)!
:-)
Peter
On Wed, 5 Apr 2000, Peter Gerwinski wrote:
Hallo, Martin!
I've downloaded the current GPC tar file, unpacked it, and moved (actually symlinked) the p/ directory into gcc-2.95.2/ (which is the unpacked source of the current gcc).
I remember some problems with symlinks - better move it.
Furthermore, it belongs into the "gcc" subdirectory of gcc-2.95.2.
Now your INSTALL file tells me to patch gcc with the appropriate p/diffs/*** Which one do I need? There are only ones for old gcc's.. Or is it unnecessary to patch 2.95.x at all ?
You can patch it with the same diff as 2.95.1.
Next question:
I do not see a patch for gpc-2.95.1 in the diffs directory, instead, I see the following:
README gcc-egcs-2.91.60.diff mkdiff gcc-2.8.1.diff gcc-egcs-2.92.27.diff gcc-egcs-2.91.57.diff gcc-egcs-2.92.33.diff
For 2.95.2, do I simply use the most recent of these (gcc-egcs-2.92.33.diff)?
------------------------------------------------------- John L. Ries Salford Systems Phone: (619)543-8880 x25 or (619)667-0056 FAX: (619)543-8888 E-Mail: jries@salford-systems.com _______________________________________________________
John L. Ries wrote:
I do not see a patch for gpc-2.95.1 in the diffs directory, instead, I see the following:
README gcc-egcs-2.91.60.diff mkdiff gcc-2.8.1.diff gcc-egcs-2.92.27.diff gcc-egcs-2.91.57.diff gcc-egcs-2.92.33.diff
For 2.95.2, do I simply use the most recent of these (gcc-egcs-2.92.33.diff)?
No, you need `gcc-2.95.diff' which should come with gpc-19991030 or newer.
Hope this helps,
Peter
-
John L. Ries -
Martin Maechler -
Peter Gerwinski