[fpc-devel]Linking problems with fpc cvs

Mattias Gaertner nc-gaertnma at netcologne.de
Tue May 6 17:29:12 CEST 2003


On Tue, 6 May 2003 16:41:59 +0200
Mattias Gaertner <nc-gaertnma at netcologne.de> wrote:

> On Tue, 6 May 2003 16:15:56 +0200 (CEST)
> marcov at stack.nl (Marco van de Voort) wrote:
> 
> > > On Tue, 6 May 2003, Mattias Gaertner wrote:
> > > > > > is. The ppas.sh is executed with the same working directory as
> > > > > > the compiler. Therefore the -L. can't find the library.
> > > > > >
> > > > > > Any ideas?
> > > > >
> > > > > Yes, remove the -XX -CX -Xs options.
> > > > > Then it should work fine (At least here it does).
> > > >
> > > > Thx. I will try. Although I don't know where they were added.
> > > > Maybe the docs know ...
> > > 
> > > Probably setting RELEASE=1 does this.
> 
> The spec file also compiles smart. 
> 
>  
> > I think this is simply a fault, the platform building doesn't seem to
> > be included. RELEASE_1_0_8_PRE1 works fine.
> > 
> > I can't build FIXES_1_0_0 because of this either, on *BSD, however
> > simply
> > 
> > OPT="-Fu/full/path/to/fpc/fcl/freebsd" solves it for me.
> 
> I solved it, by adding -Fl../$(OS_TARGET) to the fcl/net/Makefile.fpc
> options.
> Now I'm trying to compile a fpc rpm under RH9. First bug is the deprecated
> rpm call to build the package. This can easily be fixed in the
> Makefile.fpc with 
> rpm <options> || rpmbuild <options>
> 
> Then I'm getting the next error:
> 
> error: Installed (but unpackaged) file(s) found:
>   /usr/doc/fpc-1.0.8/examples/...
> 
> Somehow the examples went to /usr/doc instead of /usr/share/doc.

It seems that fpcmake creates a lot of code like the following:

ifdef BSDhier
DOCPREFIXDIR=share/doc
else
DOCPREFIXDIR=doc
endif

I will leave this to the fpc-team.

Also the yylexacc is put under /usr/lib/fpc/. 


Mattias





More information about the fpc-devel mailing list