On 11/19/13 2:44 PM, Peter Balling wrote:
> Hi
>
> The lyx2-x11 compilation failure remains both in Fink-0.36.0 and after
> upgrading to Fink-0.36.1.
>
> I tried temporarily to add gradually the symbolic links
>
> /sw/include/tr1 -> /usr/include/c++/4.2.1/tr1
> /sw/include/bits -> /usr/include/c++/4.2.1/bits
> /sw/include/ext -> /usr/include/c++/4.2.1/ext
>
> to provide missing header files. But this generated several other
> errors. So more help is needed. to bring LyX back in Fink for 10.9.
>
> Best regards
> Peter Balling
>
> ------------------------------------------------------------
> Peter Balling
> ASC, Antenna Systems Consulting ApS
> Selsmosevej 12
> DK-2630 Taastrup
> Denmark
>
> Tel.: +45 4352 1952
> GSM: +45 2149 2382
> Fax: +45 4352 0172
> E-mail: pball...@asc-consult.dk <mailto:pball...@asc-consult.dk>
> WWW: http://www.asc-consult.dk
>
>

It works here on 10.9.

The update to the "fink" tool is irrelevant to this issue.  Check 
whether your Fink installation sees lyx2-x11-2.0.6-64 as the current 
version, since that's where the fix got implemented.  If not, do a 
selfupdate.

If you're still having problems, then make sure to undo any manual 
changes you made in your /sw directory, because Fink most definitely is 
not robust against that.
-- 
Alexander Hansen, Ph.D.
Fink User Liaison
My package updates: http://finkakh.wordpress.com/

------------------------------------------------------------------------------
Shape the Mobile Experience: Free Subscription
Software experts and developers: Be at the forefront of tech innovation.
Intel(R) Software Adrenaline delivers strategic insight and game-changing 
conversations that shape the rapidly evolving mobile landscape. Sign up now. 
http://pubads.g.doubleclick.net/gampad/clk?id=63431311&iu=/4140/ostg.clktrk
_______________________________________________
Fink-users mailing list
Fink-users@lists.sourceforge.net
List archive:
http://news.gmane.org/gmane.os.macosx.fink.user
Subscription management:
https://lists.sourceforge.net/lists/listinfo/fink-users

Reply via email to