On Tue, Nov 18, 2014 at 11:25 PM, John Marino <[email protected]> wrote:
> On 11/19/2014 07:57, Mehmet Erol Sanliturk wrote: > > As a principle , assume that I can help you as much as possible to make > > Free Pascal and Lazarus a working port in DragonFly BSD . > > > Free Pascal is a working port. I am wondering how well it works. It > must work fairly well since it can build itself and most packages. > > > > For this I need your help because I do not know DragonFly BSD > > sufficiently well . > > Due to this I need explicit instructions about what to do . > > Assume I have sufficient time to apply steps . > > > Given that you specifically inquired about, and then requested Free > Pascal be available via ports, I assumed that you were user of Free > Pascal, DragonFly BSD, and dports. Instructing you how to use any of > those three is basically out of scope of this activity. > > > > Another point is if we can document what we did to generate these ports , > > such a document would be used as a guide for other ports . > > > The Free Pascal organization has published a cross-compile instruction > document. The work involved is modifying to Free Pascal base to support > DragonFly. Anybody wanting a port of Free Pascal will have to do the > same, even more if it's a new CPU. Even if there were something new to > document (there isn't), I don't have time. > > > > > Testing is important . Let's include all testing steps applicable to > > verify usability of Free Pascal and Lazarus . > > > Yes, very good. What are test steps? Is there a test suite available? > > > > Assume I have installed 4.0 RC3 and it is booted and the computer is > > shutdown and rebooted to start working on Free Pascal port . > > > > There is the following page , but it is not clear for me > > because of assumptions about pkgsrc which is not applicable for 4.0 RC3 : > > > > http://www.dragonflybsd.org/docs/howtos/HowToDPorts/ > > > I don't know what you mean. There are only 2 references to pkgsrc on > that page and it says "if you have pkgsrc do this". You don't, so skip > those steps. That guide is still fully applicable, and DragonFly 4 > comes with pkg already configured and installed. > > > > > > Let also assume that DragonFlyBSD repository is cloned here and updates > > will be applied quickly . > > > Would you please > > > > make a list of steps > > what I should note > > > > which > > > > I can apply , > > Take notes and > > reply to you at the end . > > > Read "Installing DPorts tree" section of the guide. > then > cd /usr/dports/lang/fpc && make install > > > > > I do not know kyua , > > > > http://pkg.wolfpond.org/dragonfly:4.0:x86:64/LATEST/All/kyua-0.11,2.txz > > > > but can we apply it for testing steps of this port . In that way , we > > can also enlarge testing facility for DragonFly BSD . > > > You are thinking very grand. > All I want to know is if Free Pascal compiles what it is supposed to, > and that the executables it produces work as expected. If you made a > testing framework, you should donate that to the Free Pascal group so > they can test all their FPC ports. > > John > # cd /usr # make dports-create-shallow Error code 120 occurred . # rm -rf dports # make dports-create-shallow Succeeded ... # cd /usr/dports/lang/fpc # make Many coretemp1:PROCHOT asserted messages are displayed among make listing . gmake[1]:Entering directory '/usr/obj/dports/lang/fpc/work/fpc-2.6.4/utils/fpcm' /bin/mkdir -p units/x86_64-dragonfly coretemp1:PROCHOT asserted __missing_command_DATA2INC -b -s fpcmake.ini fpcmake.inc fpcmakeini gmake[1]:__missing_command_DATA2INC : Command not found Makefile: 2411 : recipe for target 'fpcmake.inc' failed gmake[1]: ** [fpcmake.inc] Error 127 gmake[1]: Leaving directory '/usr/obj/dports/lang/fpc/work/fpc-2.6.4/utils/fpcm' ** Error code 2 Stop . make : stopped in /usr/dports/lang/fpc . Coming up to this point is showing that the compiler is working . Thank you very much . Mehmet Erol Sanliturk
