GNU Pascal (GPC) v2.0 beta FreeBSD port.
Responsible Changed From-To: freebsd-ports->will i'll look at this.
On Fri, Mar 24, 2000 at 02:14:50PM +0200, antonz@library.ntu-kpi.kiev.ua wrote: > >Description: > > GNU Pascal (GPC) v2.0 beta FreeBSD port. I'm still having trouble resolving this port's PLIST problems. I've fixed the install-info errors, however, the port still installs GCC info and manpages. I've tried hacking the Makefiles to make them work right. Since you submitted this port, I figured maybe you would know a little more about how this whole thing works, and would therefore be more able to solve this sort of problem. BTW: I'm leaving the original creator of this port as the submitter of the original PR, since you mostly copied his Makefile and didn't make any portlint fixes. -- Will Andrews <andrews@technologist.com> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y?
On Fri, 31 Mar 2000, Will Andrews wrote: Sorry that my English so bad. :-) :-( > On Fri, Mar 24, 2000 at 02:14:50PM +0200, antonz@library.ntu-kpi.kiev.ua wrote: > > >Description: > > > > GNU Pascal (GPC) v2.0 beta FreeBSD port. > > I'm still having trouble resolving this port's PLIST problems. I've fixed > the install-info errors, however, the port still installs GCC info and > manpages. I've tried hacking the Makefiles to make them work right. > I corrected this by placing 'INSTALL_TARGET= pascal.install' line in main Makefile. Is this correct? Can i receive PLIST and Makefile with fixed install-info errors? > Since you submitted this port, I figured maybe you would know a little more > about how this whole thing works, and would therefore be more able to solve > this sort of problem. > > BTW: I'm leaving the original creator of this port as the submitter of the > original PR, since you mostly copied his Makefile and didn't make any > portlint fixes. > :-(((. Yes, Makefile was mostly copied from previous port prerelease, but patches that derived from 'gcc-2.8.1.diff' was all rehacked by hands, because original GPC patch does not applies after applying gcc FreeBSD patches and have fatal incompatibilities in 'record_function_format', for example. Now i'm working on: 1. Fixing problems in 'units' directory. I'm send new patches in one week. 2. Writing post-install target and POST-INSTALL script to automatically compile units after installing port/package. 3. Is target directory like 'i386--freebsd3.4' in '/usr/local/' and '/usr/local/gcc-lib/' correct? Or it must looks 'i386-portbld-freebsd3.4'? How to correct it if 4. I was 'portlint'ed port and all FATAL and WARN errors fixed. -- Anton N. Breusov 'Antonz'. antonz@i.am, antonz@library.ntu-kpi.kiev.ua
On Mon, Apr 03, 2000 at 10:59:49AM +0300, Anton N. Breusov wrote: > Sorry that my English so bad. :-) :-( Please don't apologize, everyone has faults (including myself). > I corrected this by placing 'INSTALL_TARGET= pascal.install' line in main > Makefile. Is this correct? > Can i receive PLIST and Makefile with fixed install-info errors? I will test this in the Makefile, and send you my current copy of the port. > > BTW: I'm leaving the original creator of this port as the submitter of the > > original PR, since you mostly copied his Makefile and didn't make any > > portlint fixes. > > > :-(((. > Yes, Makefile was mostly copied from previous port prerelease, but > patches that derived from 'gcc-2.8.1.diff' was all rehacked by hands, > because original GPC patch does not applies after applying gcc FreeBSD > patches and have fatal incompatibilities in 'record_function_format', for > example. I'm sorry, but it still seems the original submitter did most of the legwork, and therefore deserves to be mentioned in the Whom comment line. However, you would still get credit as the submitter of this PR and also in the commit message. You would also become the first maintainer. > Now i'm working on: > 1. Fixing problems in 'units' directory. > I'm send new patches in one week. What problems? > 3. Is target directory like 'i386--freebsd3.4' in '/usr/local/' and > '/usr/local/gcc-lib/' correct? Or it must looks > 'i386-portbld-freebsd3.4'? How to correct it if I am not sure.. you probably should ask obrien@FreeBSD.org since he maintains the gcc-devel and egcs ports. > 4. I was 'portlint'ed port and all FATAL and WARN errors fixed. I already fixed them in my local copy. -- Will Andrews <andrews@technologist.com> GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y?
State Changed From-To: open->closed Committed, thanks! Sorry it took so long for me to review this port submission.