Hi,
It seems our libftdi is several versions behind (current is 0.17).
I'm no expert, but I got 0.17 to build by adding the following to
/usr/ports/devel/libftdi/Makefile:
WITH_BOOST=yes
CONFIGURE_ARGS+=--with-boost=/usr/local/include/boost
CFLAGS+=-I${LOCALBASE}/include -L${LOCALBAS
I've got a project to port that doesn't do releases, just puts out the
git. I know we've got alot of ports that pull strait from cvs or svn,
is there a good corresponding example for git?
Thanks,
Steve
___
freebsd-ports@freebsd.org mailing list
http://l
On Wed, Jan 28, 2009 at 12:54 AM, Florent Thoumie wrote:
> On Wed, Jan 28, 2009 at 4:56 AM, Dmitry Marakasov wrote:
>> * Florent Thoumie (f...@xbsd.org) wrote:
>>
>>> > You are lucky guys you have not lived in USSR. otherwise you'd surely like
>>> > alternative ways :)
>>>
>>> In soviet russia, a
I presume Florent's preferred method is "INSTALL_PROGRAM"? So far,
the only doc I've found is that it exists. So I put INSTALL_PROGRAM
$(WORKDIR)/$(PORTNAME) (portname just happens to be the name of the
executable) in the port Makefile, or what? I've never been able to
'read' makefiles, so I'm n
>>
>>> and of course you must have "bin/program_name" in pkg-plist.
>>
>> If it's just a single file, the preferred way is to add
>>
>> PLIST_FILES=bin/program_name
>>
>> to the Makefile and not use pkg-plist at all.
>
> No, no, no.
>
> This is not *preferred*.
>
Well, what is, then? ...
Stev
If a distfile on sourceforge is lpc21isp.1.63.tar.gz instead of
lpc21isp-1.63.tar.gz, how do I tweak the port makefile to pull it in?
Thanks,
Steve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsu
I got me a port that just builds a single executable. What's the
proper way to set up the port makefile to copy that to /usr/local/bin?
Thanks,
Steve
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To u
Bruce,
I've been playing with your makefile for openocd. Awhile back I was
told that the *right* way to do this as a real port was to get the
svn, make a tgz in distfiles, and then build the port from that.
Looks like you did the svn->distfiles part manually in your origonal
makefile, right?
I w
In maintaining devel/urjtag, I've added a dependancy to textproc/flex.
On some systems, however, I've found that when textproc/flex gets
installed, it lands in /usr/local/bin, as expected, but there's a
/usr/bin/flex which precedes it in the path - is there a canonical way
to resolve this? I've j
Hi,
There are two embedded software tools
I've been wanting to port for some time. Both have inconsistent/funky
downloads, so I have no idea how to get them into a port. Both are
very active projects, and used by pretty much all embedded ARM7/9
developers (embedded as in microwaves & thermostats
I *think* (and I'm no guru) that googleearth needs the
ONLYFORARCHS=i386 flag set. I can't for the life of me get it to run
on amd64 with either linux_base-fc4 or base-f7 - it installs, but
complains about missing libGL.so.1:
./googleearth-bin: error while loading shared libraries:
libGL.so.1
I've been around the bend for several weeks beating this thing. This
can't just be a problem on my vanilla system.
First, the preliminaries:
FreeBSD dystant.dyndns.biz 7.0-STABLE FreeBSD 7.0-STABLE #1: Mon
May 12 14:09:43 MST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/DYSTANT amd64
mel
On Wed, Aug 6, 2008 at 6:50 PM, Edwin Groothuis <[EMAIL PROTECTED]> wrote:
>
>> I thought someone would want to know a "portupgrade -a" just broke my
>> qemu installation. Suddenly no libSDL.so.11 was found so qemu
>> wouldn't start. I was smart enough to link libSDL-1.2.so.11 to
>> libSDL.so.11
I thought someone would want to know a "portupgrade -a" just broke my
qemu installation. Suddenly no libSDL.so.11 was found so qemu
wouldn't start. I was smart enough to link libSDL-1.2.so.11 to
libSDL.so.11 in /usr/local/lib, so I have no issues, but I suspect
this reflects some kid of failed de
I proposed some changes to ezload in march. I've not heard from the
maintainer or author, and the download site is offline today.
ezload is important because it loads firmware on usb devices, many of
which are fairly common. unfortunately, support for newer (< 3-4
years old) devices still has no
I'm making a new port of a linux program.
I've figured out how to get the dependenices for wx so it's installed,
but now I get an error when configure is called, because it's looking
for the script wx-config, which is getting installed by the dependancy
as wxgtk2-2.8-config. Should I be making a
On Wed, May 21, 2008 at 5:28 AM, bridd <[EMAIL PROTECTED]> wrote:
> Hi Steve,
>
> I saw your thread
> http://lists.freebsd.org/pipermail/freebsd-usb/2008-April/004753.html
> via googling for FreeBSD fxload equivalents. Did you get any further
> with it?
>
> I'm wondering, because I've got an m-aud
I'm trying to build the devel/arm-elf-gcc295 port for the more modern gcc4.2.3.
What I've done: edited devel/arm-elf-gcc295/Makefile to change version
2.95 to 4.2.3, removed patches for v295, ran make makesum, ran "make".
This error seems like something pretty obvious, not having done it
before,
Just built /devel/clint on my vanilla 7.0 system. Appears to build
and install fine, but #clint or #clint --help freezes the console, and
ctrl-C initiates a core-dump. Python appears to run just fine.
Info:
[EMAIL PROTECTED] /usr/home/steve]$ pkg_info | grep clint
clint-0.1.2_4 A static s
19 matches
Mail list logo
