[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Autoconf 2.69 bug

From: Steve Glaser
Subject: RE: Autoconf 2.69 bug
Date: Tue, 1 Sep 2015 20:48:51 +0000

That's fine. It was pretty easy to work around. Other stuff gets confused by 
Dropbox's convention. I've told them I'm not wild about it.

Just wanted to mention it in case it was something you wanted to look at.

I'll see if anyone on the SystemC forum claims ownership.

> -----Original Message-----
> From: Eric Blake [mailto:address@hidden
> Sent: Tuesday, September 01, 2015 1:46 PM
> To: Steve Glaser; address@hidden
> Cc: address@hidden
> Subject: Re: Autoconf 2.69 bug
> * PGP Signed by an unknown key
> > I created a symbolic link /Users/login/Dropbox-Company to
> /Users/login/Dropbox (Company). When I build in that area, things work as
> expected.
> Then this is what you should do. :)
> >
> > I suspect there's some place that needs double quotes. I don't know whether
> it's in your stuff or in the SystemC customization.
> Autoconf tries to allow for absolute paths that contain spaces and other shell
> metacharacters, as long as the build tree itself does not add any further; 
> but it
> may not always succeed (patches welcome).  But even if autoconf is perfect in
> its use of quoting, many other packages write configure.ac that are not as
> careful.  In this regards, I suspect that it is the SystemC code at fault for 
> not
> handling metacharacters in the absolute path.  In fact, it may be an unfixable
> problem; the 'make'
> language is very unforgiving in its syntax (it lacks double quotes that shell 
> has),
> and any project that uses automake in addition to autoconf to generate the
> configure/Makefile pairs may result in a generated Makefile that cannot deal
> with absolute paths that aren't sane.
> So unless you can point to a specific error message, and prove that it comes
> from autoconf proper and not from SystemC's configure.ac file, I'm inclined to
> think this is not an autoconf bug, but a normal limitation that you'll just 
> have to
> work around via symlink or mount point.
> --
> Eric Blake   eblake redhat com    +1-919-301-3266
> Libvirt virtualization library http://libvirt.org
> * Unknown Key
> * 0x2527436A

reply via email to

[Prev in Thread] Current Thread [Next in Thread]