Perl compile error - not yet resolved

Adam Trilling agt10 at columbia.edu
Tue Oct 1 09:29:02 PDT 2002


No, these are not false warnings.  They are a result of the symlinks.

This is a good one, if I understand it correctly...

cc1 searches for /opt/local/include.  But /opt -> /usr, so
/opt/local/include -> /usr/local/include.  But since /usr/local -> /usr,
/opt/local -> /usr and /opt/local/include -> /usr/include.  Is anyone else
having scary visions of circular symlinks?

Perl's configure script is written for OSes which are much more
FHS-compliant than Linux.  Therefore /opt/local/include may be necessary.
But when it's a symlink to /usr/include, and cc1 is already searching
/usr/include by default, it complains.

I think the answer is to find a configure option for Perl that doesn't
search /opt/local/include by default.

And this gives more credence to the proposal that this failure to compile
is a header problem.

adam

On Tue, 1 Oct 2002, Gerard Beekmans wrote:

> On October 1, 2002 02:33 am, Greg Schafer wrote:
> > What's with the "-I/opt/local/include" ? Not sure where that came from. The
>
> I don't like the /opt and /usr/local directories so I always remove them and
> make them symlink to /usr - so these are false warnings from GCC. Whatever
> search order it uses, it'll always find the proper files in /usr/include
>
> I'll have another look at my kernel headers and get back you guys later today.
>
> --
> Gerard Beekmans
> www.linuxfromscratch.org
>
> -*- If Linux doesn't have the solution, you have the wrong problem -*-
> --
> Unsubscribe: send email to listar at linuxfromscratch.org
> and put 'unsubscribe lfs-dev' in the subject header of the message
>
>


Adam Trilling
agt10 at columbia.edu


char m[9999],*n[99],*r=m,*p=m+5000,**s=n,d,c;main(){for(read(0,r,4000);c=*r;
r++)c-']'||(d>1||(r=*p?*s:(--s,r)),!d||d--),c-'['||d++||(*++s=r),d||(*p+=c==
'+',*p-=c=='-',p+=c=='>',p-=c=='<',c-'.'||write(2,p,1),c-','||read(2,p,1));}

-- 
Unsubscribe: send email to listar at linuxfromscratch.org
and put 'unsubscribe lfs-dev' in the subject header of the message



More information about the lfs-dev mailing list