Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / fpc-devel / 2001-01

`make install` builds 1.0.4-RELEASE?

5 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Roderick van Domburg

Hi there,

I've succesfully built all of the sources from the FIXES_1_0_0 branch, and indeed the `fpc` executable in the compiler directory displays version 1.0.5. But if I then execute a `make install` in the top-level directory, 1.0.4 is installed. What is up with that?

(Actually, I'm building on a FreeBSD box, so I'm issuing a `gmake`, version 3.79.1. Speaking of which, are there any known limitations to the FreeBSD port? I couldn't find any documented in the package.)

Thanks in advance,
Roderick

Reply by email

Peter Vreman
Show quoted text 10 lines
Hi there, I've succesfully built all of the sources from the FIXES_1_0_0 branch, and indeed the `fpc` executable in the compiler directory displays version 1.0.5. But if I then execute a `make install` in the top-level directory, 1.0.4 is installed. What is up with that? (Actually, I'm building on a FreeBSD box, so I'm issuing a `gmake`, version 3.79.1. Speaking of which, are there any known limitations to the FreeBSD port? I couldn't find any documented in the package.)

The top-level makefile finds the 1.0.4 compiler and takes that as start compiler. There are two solutions, define to use compiler/ppc386 or add the version yourself:

make install PP=$(BASEDIR)/compiler/ppc386

or

make install FPC_VERSION=1.0.5

Reply by email

Marco van de Voort
to Roderick van Domburg: I've succesfully built all of the sources from the FIXES_1_0_0 branch, and indeed the…
Show quoted text 8 lines
I've succesfully built all of the sources from the FIXES_1_0_0 branch, and indeed the `fpc` executable in the compiler directory displays version 1.0.5. But if I then execute a `make install` in the top-level directory, 1.0.4 is installed. What is up with that? (Actually, I'm building on a FreeBSD box, so I'm issuing a `gmake`, version 3.79.1. Speaking of which, are there any known limitations to the FreeBSD port? I couldn't find any documented in the package.)

All questions about the FreeBSD port to me.

- Only 4.x is tested. 3.x worked before signalhandling introducing, but I can't test that version anymore. Probably only the syscalls for signalhandling are slightly different.
- I'm still not 100% sure about readdir.
- The IDE only works over telnet.
- alarm and time don't work yet. nanosleep does.
- Really a lot is untested in general.

If you use the FreeBSD port, do a CVS checkout, and try to build 1.0.5.

It contains header translations of console.h and mouse.h, which needs a small patch to packrecords which is post 1.0.4

Reply by email

Roderick van Domburg
to Marco van de Voort
Marco van de Voort wrote 12 lines
- Only 4.x is tested. 3.x worked before signalhandling introducing, but I can't test that version anymore. Probably only the syscalls for signalhandling are slightly different. - I'm still not 100% sure about readdir. - The IDE only works over telnet. - alarm and time don't work yet. nanosleep does. - Really a lot is untested in general. If you use the FreeBSD port, do a CVS checkout, and try to build 1.0.5. It contains header translations of console.h and mouse.h, which needs a small patch to packrecords which is post 1.0.4

Thanks for all the quick answers. I'll be sure to keep you updated on all my FreeBSD-related findings, it will be my main platform for development.

The solution offered on this mailing list also solved my `make install` problem, thanks a lot. A single curiosity is that it install the new compiler in [pptest]/lib/(etc.) and places a copy of the old one in [pptest]/bin. Or is that the default behavior, allowing you to run both the release and stable versions in parallel?

Reply by email

Marco van de Voort
to Roderick van Domburg
Thanks for all the quick answers. I'll be sure to keep you updated on all my FreeBSD-related findings, it will be my main platform for development.

Thanks.

Show quoted text 5 lines
The solution offered on this mailing list also solved my `make install` problem, thanks a lot. A single curiosity is that it install the new compiler in [pptest]/lib/(etc.) and places a copy of the old one in [pptest]/bin. Or is that the default behavior, allowing you to run both the release and stable versions in parallel?

Usually it should be in [prefixdir]/lib/fpc/[version]/ with a symlink to it in [prefixdir]/bin

I always move the files of the snapshots by hand or script, and I don't use the make targets for it.

Reply by email