avr-chat
[Top][All Lists]
Advanced

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

Re: [avr-chat] Can't Install avr-gcc in FreeBSD


From: Joerg Wunsch
Subject: Re: [avr-chat] Can't Install avr-gcc in FreeBSD
Date: Fri, 17 Aug 2007 23:53:51 +0200 (MET DST)

David Brown <address@hidden> wrote:

> But when you step outside of that, you enter the world of dependency
> resolution, patching, ./configure, and make, instead of an
> InstallShield wizard.

C'mon.  The day you start to run ./configure is the day when you would
have to give up on Windows, because nobody went there before, and
prepared you the InstallShield Wizard package at all.

> Thus when trying to install avr-gcc on FreeBSD you have to fiddle
> around with -DNOPORTDOCS flags in the "make install" line, while on
> windows you just download the latest winavr release.

Sorry, this is just avr-libc breakage, caused by the direct use of
ISO8859-1 characters in avr-libc's doxygen source, and uncovered by
FreeBSD upgrading their doxygen so the default changed from
"pass-through" to "handle everything as UTF-8".  If it wasn't
discovered by the FreeBSD build of the avr-libc package, it would
probably have broken the next WinAVR release instead.  We simply need
to fix it, and I just need time for that.

Long story short, this is *not* the normal course of doing things in
the FreeBSD ports system.  The -DNOPORTDOCS option is not there to
work around bugs in the software, but to reduce the number of
prerequisite tools for the mortal user, since doxygen and its
documentation have a *lot* of prerequisites -- Eric Weddington can for
sure tell you, he hasn't been able to build the avr-libc docs himself
for the WinAVR distribution until very recently.  Before that, guess
what he's been relying to for his WinAVR bundled docs?  Those that
I've been creating on my FreeBSD machine...

Instead, normal FreeBSD usage would be that you proceed to your
closest mirror, tell your sysinstall to install packages from it, and
select "avr-gcc", "avr-libc" and maybe "avr-gdb".  Then, you install
binary packages the same way as you would with WinAVR, except you've
got finer control about what to include and what to leave out.

-- 
cheers, J"org               .-.-.   --... ...--   -.. .  DL8DTL

http://www.sax.de/~joerg/                        NIC: JW11-RIPE
Never trust an operating system you don't have sources for. ;-)




reply via email to

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