mmap error (?) when building clisp-2.38 in freebsd-6.1-release for amd64
Hi I am trying to the the clisp-2.38 port to build on freebsd-6.1-release of amd64. However, it does not build and I found a post saying that it was marked as broken. So far I have tried the following. 1, After running make, the first error that comes up is gmake: *** No rule to make target `avcall-amd64.lo', needed by `avcall.lo'. Stop. In the Makefile in 'work/clisp-2.38/amd64-portbld-freebsd6.1/avcall', CPU is set to amd64 and avcall-$(CPU).lo expands to avcall-amd.lo, when the actual source file is avcall-x64_64.c. Setting CPU to x86_64 fixes this error 2. The next error is gmake[1]: *** No rule to make target `vacall-amd64.lo', needed by `vacall.lo'. Stop. There is a similar error in 'work/clisp-2.38/amd64-portbld-freebsd6.1/callback/vacall_r/Makefile' and is easily fixed 3. However, the third error is beyond me. ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -Emisc 1:1 -norc -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) (ext::exit t)" Cannot map memory to address 0x4 . [spvw_mmap.d:359] errno = EINVAL: Invalid argument. ./lisp.run: Not enough memory for Lisp. *** Error code 1 Is there any way to fix this? Is this for using mmap? The Makefile for the port enables the '--disable-mmap' option for amd64 Regards Gautham ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Using darcs to retrieve source in ports
Hi there, I'm trying to build a port of PacketForth, (https://packets.goto10.org/) and it's going pretty well. However, as it's still in the early stages of development, there are no tarfiles available online, and the preferred method of fetching the source is by using the darcs version control system. The single command I ran to get the source was "darcs get http://url"; and I was wondering it's possible for a port to retrieve files in this way. I've been following the porters handbook, but it assumes use fetch(1) for everything. Should I tar up the sources periodically and host them on a webserver somewhere? Is that the preferred way of doing things? Thanks for any help guys, ian ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Using darcs to retrieve source in ports
On 7/29/06, Ian Morrison <[EMAIL PROTECTED]> wrote: Hi there, I'm trying to build a port of PacketForth, (https://packets.goto10.org/) and it's going pretty well. However, as it's still in the early stages of development, there are no tarfiles available online, and the preferred method of fetching the source is by using the darcs version control system. The single command I ran to get the source was "darcs get http://url"; and I was wondering it's possible for a port to retrieve files in this way. The net/obnc port uses CVS to fetch its files; that might be a good place to start looking. Dave. -- "Strange women lying in ponds distributing swords is no basis for a system of government." ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Using darcs to retrieve source in ports
On Sat, 29 Jul 2006 13:52:20 +0100 Ian Morrison <[EMAIL PROTECTED]> mentioned: > Hi there, > > I'm trying to build a port of PacketForth, (https://packets.goto10.org/) > and it's going pretty well. However, as it's still in the early stages > of development, there are no tarfiles available online, and the > preferred method of fetching the source is by using the darcs version > control system. The single command I ran to get the source was "darcs > get http://url"; and I was wondering it's possible for a port to retrieve > files in this way. I've been following the porters handbook, but it > assumes use fetch(1) for everything. Should I tar up the sources > periodically and host them on a webserver somewhere? Is that the > preferred way of doing things? > > Thanks for any help guys, It would be better to create a snapshot and upload it somewhere. Although it is impossible to redefine do-fetch target and get files from CVS/darcs it would be hard to check files consistency, since their sizes will vary depending on snapshot date/time/revision, so you should provide tag/date switch to repository checkout program. Additionally, you should issue own checksum checking code or add every file in distinfo/DISTFILES. -- Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]> Россия, Москва http://mbsd.msk.ru If the facts don't fit the theory, change the facts. -- A. Einstein PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 signature.asc Description: PGP signature
Re: Using darcs to retrieve source in ports
On Sat, 29 Jul 2006 23:16:55 +1000 "David Symonds" <[EMAIL PROTECTED]> mentioned: > > The net/obnc port uses CVS to fetch its files; that might be a good > place to start looking. > It uses CVS to prepare tarball for maintainer, not for checkouting distfiles itself. -- Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]> Россия, Москва http://mbsd.msk.ru If the facts don't fit the theory, change the facts. -- A. Einstein PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581 signature.asc Description: PGP signature
Re: Using darcs to retrieve source in ports
The net/asterisk-devel fetchs out sources from SVN -- Best regards, Arseny Nasokin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ruby vulnerability?
On Fri, Jul 28, 2006 at 03:03:43PM +1000, Joel Hatton wrote: > > FYI, Red Hat released an advisory today about a vulnerability in Ruby. So > far it doesn't appear in the VuXML, but am I correct in presuming it will > soon? > I've added it; thanks for the report. -- Shaun Amott [ PGP: 0x6B387A9A ] Scientia Est Potentia. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ruby vulnerability?
Shaun Amott wrote: > On Fri, Jul 28, 2006 at 03:03:43PM +1000, Joel Hatton wrote: >> FYI, Red Hat released an advisory today about a vulnerability in Ruby. So >> far it doesn't appear in the VuXML, but am I correct in presuming it will >> soon? >> > > I've added it; thanks for the report. > Can we get patches somewhere? I can't find any. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ruby vulnerability?
Sergey Matveychuk wrote: Shaun Amott wrote: On Fri, Jul 28, 2006 at 03:03:43PM +1000, Joel Hatton wrote: FYI, Red Hat released an advisory today about a vulnerability in Ruby. So far it doesn't appear in the VuXML, but am I correct in presuming it will soon? I've added it; thanks for the report. Can we get patches somewhere? I can't find any. It is said that the patches are available through the CVSweb but all the information I could fine was in japanese, which is a bit difficult to read for me (read: i do not speak nor read japanese at all). We might have a shot on how different vendors resolved this issue and generate patches from that.. -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ruby vulnerability?
On Sat, Jul 29, 2006 at 07:54:16PM +0200, Remko Lodder wrote: > > Sergey Matveychuk wrote: > >Shaun Amott wrote: > >>On Fri, Jul 28, 2006 at 03:03:43PM +1000, Joel Hatton wrote: > >>>FYI, Red Hat released an advisory today about a vulnerability in Ruby. So > >>>far it doesn't appear in the VuXML, but am I correct in presuming it will > >>>soon? > >>> > >>I've added it; thanks for the report. > >> > > > >Can we get patches somewhere? I can't find any. > > > > It is said that the patches are available through the CVSweb > but all the information I could fine was in japanese, which is > a bit difficult to read for me (read: i do not speak nor read > japanese at all). The CVE report seemed to imply that there was a fix in 1.8.5, which I assumed had therefore been released. But it seems this isn't the case. The Ruby folks say they don't publish advisories until there is a fix ready; and there is no mention of this vulnerability on the website. -- Shaun Amott [ PGP: 0x6B387A9A ] Scientia Est Potentia. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
Andrey Chernov wrote: > On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote: >> The port graphics/png does not honour the CC Variable. > > I can't reproduce that, it honors CC for me. > Here's what I get: [EMAIL PROTECTED] cd /usr/ports/graphics/png [EMAIL PROTECTED] make -V CC /usr/local/bin/distcc cc [EMAIL PROTECTED] make ===> Extracting for png-1.2.12_1 => MD5 Checksum OK for libpng-1.2.12.tar.bz2. => SHA256 Checksum OK for libpng-1.2.12.tar.bz2. ===> Patching for png-1.2.12_1 ===> Applying FreeBSD patches for png-1.2.12_1 ===> Configuring for png-1.2.12_1 ===> Building for png-1.2.12_1 ( cat scripts/libpng-config-head.in; echo prefix=\"/usr/local\"; echo libdir=\"/usr/local/lib\"; echo ccopts=\"-O2 -fno-strict-aliasing -pipe -march=pentium-m\"; echo cppflags=\"\"; echo I_opts=\"-I/usr/local/include/libpng\"; echo L_opts=\"-L/usr/local/lib\"; echo libs=\"-lpng -lz -lm\"; echo ldopts=\"\"; cat scripts/libpng-config-body.in ) > libpng-config chmod +x libpng-config cc -O2 -fno-strict-aliasing -pipe -march=pentium-m -c png.c cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=pentium-m -c png.c -o png.So cc -O2 -fno-strict-aliasing -pipe -march=pentium-m -c pngset.c cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=pentium-m -c pngset.c -o pngset.So cc -O2 -fno-strict-aliasing -pipe -march=pentium-m -c pngget.c cc -fpic -DPIC -O2 -fno-strict-aliasing -pipe -march=pentium-m -c pngget.c -o pngget.So ... ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]> wrote: On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote: The port graphics/png does not honour the CC Variable. I can't reproduce that, it honors CC for me. I can, CC=gcc will not change the CC when it compiles. Cheers, Mezz -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote: > On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]> > wrote: > > >On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote: > >>The port graphics/png does not honour the CC Variable. > > > >I can't reproduce that, it honors CC for me. > > I can, CC=gcc will not change the CC when it compiles. It is hard to imagine how it is ever possible. There is standard BSD makefile.freebsd which not owervrites CC as you can see in the file. -- http://ache.pp.ru/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
Andrey Chernov wrote: > On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote: >> On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]> >> wrote: >> >>> On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote: The port graphics/png does not honour the CC Variable. >>> I can't reproduce that, it honors CC for me. >> I can, CC=gcc will not change the CC when it compiles. > > It is hard to imagine how it is ever possible. There is standard BSD > makefile.freebsd which not owervrites CC as you can see in the file. > Is it possible that make.conf is read again? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mmap error (?) when building clisp-2.38 in freebsd-6.1-release for amd64
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Sat, 29 Jul 2006 13:24:54 +0530 Gautham Ganapathy <[EMAIL PROTECTED]> wrote: > Hi > > I am trying to the the clisp-2.38 port to build on freebsd-6.1-release > of amd64. However, it does not build and I found a post saying that it > was marked as broken. > > So far I have tried the following. > > 1, After running make, the first error that comes up is > > gmake: *** No rule to make target `avcall-amd64.lo', needed by > `avcall.lo'. Stop. > > In the Makefile in 'work/clisp-2.38/amd64-portbld-freebsd6.1/avcall', > CPU is set to amd64 and avcall-$(CPU).lo expands to avcall-amd.lo, when > the actual source file is avcall-x64_64.c. Setting CPU to x86_64 fixes > this error > > 2. The next error is > > gmake[1]: *** No rule to make target `vacall-amd64.lo', needed by > `vacall.lo'. Stop. > > There is a similar error in > 'work/clisp-2.38/amd64-portbld-freebsd6.1/callback/vacall_r/Makefile' > and is easily fixed > > 3. However, the third error is beyond me. > > ./lisp.run -B . -N locale -Efile UTF-8 -Eterminal UTF-8 -Emisc 1:1 -norc > -m 1400KW -x "(and (load \"init.lisp\") (sys::%saveinitmem) (ext::exit)) > (ext::exit t)" > Cannot map memory to address 0x4 . > [spvw_mmap.d:359] errno = EINVAL: Invalid argument. > ./lisp.run: Not enough memory for Lisp. > *** Error code 1 > > Is there any way to fix this? Is this for using mmap? The Makefile for > the port enables the '--disable-mmap' option for amd64 > > Regards > Gautham > Hello. I think you are using an old version of the lang/clisp port (current one is clisp-2.38_1, where building on amd64 was fixed). Could you please update your ports and try again? Best Regards, Ale P.S.: please CC me the next time (or mail me directly). -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.4 (FreeBSD) iD8DBQFEy6+XiV05EpRcP2ERApJLAJ9cU8q5fkfRFuDgnr9C8uMnE7BXtACaA+AG MPCP4acZWD36Mm2JazZB+tE= =vlVq -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: mmap error (?) when building clisp-2.38 in freebsd-6.1-release for amd64
Hello;
I had the same problems building clisp on amd64, but I reported the amd64 vs
x86_64 issue on sourceforge: I think they fixed it.
The mmap issue is AFAICT, well known. The port has these lines:
.if ${ARCH} == "amd64" || ${ARCH} == "ia64"
CONFIGURE_ARGS+=--disable-mmap
MAKEMAKE_ARGS+= --disable-mmap
.endif
hope that helps,
Pedro.
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
OCaml language support in ports
We have a lot of OCaml ports that provides additional language
packages for OCaml language. Installing of such pacakge requites
a lot of steps, e.g. running ocamlfind utility on install/deinstall
with correct enviropment, updating OCaml-specific ld.conf on
install/deinstall and other. As result ports become a bit complex
and very large. You can see working examples in devel/ocaml-equeue,
devel/ocaml-sem etc. This ports do similar work "by-hand" via
pmake constructs and pkg-install script.
I have submitted include to support OCaml language recently
(http://www.freebsd.org/cgi/query-pr.cgi?pr=101029).
This include simplifies creation on such ports. For example, the
port for ocaml-xstr might look like this (this port isn't in
ports collection yet):
PORTNAME= xstr
PORTVERSION=0.2.1
CATEGORIES= devel
MASTER_SITES= http://www.ocaml-programming.de/packages/
PKGNAMEPREFIX= ocaml-
MAINTAINER= [EMAIL PROTECTED]
COMMENT=Thread-safe implementation of string searching/matching
WRKSRC= ${WRKDIR}/${PORTNAME}
USE_GMAKE= yes
USE_OCAML= yes
USE_OCAML_FINDLIB= yes
USE_OCAML_LDCONFIG= yes
.include
And pkg-plist:
%%OCAML_SITELIBDIR%%/xstr/META
%%OCAML_SITELIBDIR%%/xstr/xstr.cma
%%OCAML_SITELIBDIR%%/xstr/xstr_match.cmi
%%OCAML_SITELIBDIR%%/xstr/xstr_match.mli
%%OCAML_SITELIBDIR%%/xstr/xstr_search.cmi
%%OCAML_SITELIBDIR%%/xstr/xstr_search.mli
%%OCAML_SITELIBDIR%%/xstr/xstr_split.cmi
%%OCAML_SITELIBDIR%%/xstr/xstr_split.mli
Simple, isn't it? Compare with ocaml-sem - it does the same steps.
The include doesn't interfere with ports available, and sufficient
for ocaml-* ports needs (hopely).
I paid a great deal of attention to make ports to honor PREFIX -
current findlib ports doesn't do this. This include will automatically
honor PREFIX - but in case of non-standard on you should handle
SITELIBDIR deletion by hand. Additionally, include automatically
adds OCAML_SITELIBDIR to PLIST_SUB.
It would be nice to have your opinions/suggestions/blames/flames
here. Especially, ocaml-* ports maintainers.
Thanks!
--
Stanislav Sedov MBSD labs, Inc. <[EMAIL PROTECTED]>
Россия, Москва http://mbsd.msk.ru
If the facts don't fit the theory, change the facts. -- A. Einstein
PGP fingerprint: F21E D6CC 5626 9609 6CE2 A385 2BF5 5993 EB26 9581
signature.asc
Description: PGP signature
Re: Ruby vulnerability?
Shaun Amott wrote: > On Sat, Jul 29, 2006 at 07:54:16PM +0200, Remko Lodder wrote: >> Sergey Matveychuk wrote: >>> Shaun Amott wrote: On Fri, Jul 28, 2006 at 03:03:43PM +1000, Joel Hatton wrote: > FYI, Red Hat released an advisory today about a vulnerability in Ruby. So > far it doesn't appear in the VuXML, but am I correct in presuming it will > soon? > I've added it; thanks for the report. >>> Can we get patches somewhere? I can't find any. >>> >> It is said that the patches are available through the CVSweb >> but all the information I could fine was in japanese, which is >> a bit difficult to read for me (read: i do not speak nor read >> japanese at all). > > The CVE report seemed to imply that there was a fix in 1.8.5, which I > assumed had therefore been released. But it seems this isn't the case. > > The Ruby folks say they don't publish advisories until there is a fix > ready; and there is no mention of this vulnerability on the website. > CVE report is very unpleasant: "Multiple unspecified vulnerabilities". Secunia has more professional report. RedHat is only vendor who released updates, but they are binary. So, there is no known fix now. I hope ruby team will release 1.8.5 ASAP. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze <[EMAIL PROTECTED]>
wrote:
Andrey Chernov wrote:
On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]>
wrote:
On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
The port graphics/png does not honour the CC Variable.
I can't reproduce that, it honors CC for me.
I can, CC=gcc will not change the CC when it compiles.
It is hard to imagine how it is ever possible. There is standard BSD
makefile.freebsd which not owervrites CC as you can see in the file.
No idea, I don't know png's build system so that cc must be come from
somewhere.
Is it possible that make.conf is read again?
I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31 line
should do.
Cheers,
Mezz
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
Jeremy Messenger wrote:
> On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze <[EMAIL PROTECTED]>
> wrote:
>
>> Andrey Chernov wrote:
>>> On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]>
wrote:
> On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
>> The port graphics/png does not honour the CC Variable.
> I can't reproduce that, it honors CC for me.
I can, CC=gcc will not change the CC when it compiles.
>>>
>>> It is hard to imagine how it is ever possible. There is standard BSD
>>> makefile.freebsd which not owervrites CC as you can see in the file.
>
> No idea, I don't know png's build system so that cc must be come from
> somewhere.
>
>> Is it possible that make.conf is read again?
>
> I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31 line
> should do.
>
CC="${CC}"
Would do better. CC can contain spaces. BTW, yes that works. I just wonder why
it's necessary.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Sat, Jul 29, 2006 at 02:59:19PM -0500, Jeremy Messenger wrote:
> On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze <[EMAIL PROTECTED]>
> wrote:
>
> >Andrey Chernov wrote:
> >>On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
> >>>On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]>
> >>>wrote:
> >>>
> On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
> >The port graphics/png does not honour the CC Variable.
> I can't reproduce that, it honors CC for me.
> >>>I can, CC=gcc will not change the CC when it compiles.
> >>
> >>It is hard to imagine how it is ever possible. There is standard BSD
> >>makefile.freebsd which not owervrites CC as you can see in the file.
>
> No idea, I don't know png's build system so that cc must be come from
> somewhere.
>
> >Is it possible that make.conf is read again?
>
> I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31 line
> should do.
It will be hack for reason unknown, I prefer to avoid that.
I normally set CC to anything and it honors.
I never heard from somebody other than you about that problem.
You should inspect your build path step by step to find real reason of
that bag, only after that we can find the real fix.
--
http://ache.pp.ru/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Sat, 29 Jul 2006 15:20:02 -0500, Andrey Chernov <[EMAIL PROTECTED]>
wrote:
On Sat, Jul 29, 2006 at 02:59:19PM -0500, Jeremy Messenger wrote:
On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze <[EMAIL PROTECTED]>
wrote:
>Andrey Chernov wrote:
>>On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
>>>On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]>
>>>wrote:
>>>
On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
>The port graphics/png does not honour the CC Variable.
I can't reproduce that, it honors CC for me.
>>>I can, CC=gcc will not change the CC when it compiles.
>>
>>It is hard to imagine how it is ever possible. There is standard BSD
>>makefile.freebsd which not owervrites CC as you can see in the file.
No idea, I don't know png's build system so that cc must be come from
somewhere.
>Is it possible that make.conf is read again?
I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31 line
should do.
It will be hack for reason unknown, I prefer to avoid that.
It is not a hack and it is known reason that you need to honor CC.
I normally set CC to anything and it honors.
How did you set? The graphics/png doesn't honor it when you add CC=foobar
in make.conf or graphics/png/Makefile.
http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/dads-cc.html
I never heard from somebody other than you about that problem.
I don't tweak CC, so it's why I never have seen it until LoN_Kamikaze
report it. Not many people do that, but it's good to honor CC for icc,
choice versions of gcc and other compilers.
You should inspect your build path step by step to find real reason of
that bag, only after that we can find the real fix.
I already have gave you a solution. If you don't like it then it's your
job to figure another solution as you are maintaining for this port.
Cheers,
Mezz
--
[EMAIL PROTECTED] - [EMAIL PROTECTED]
FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src)
http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED]
http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Sat, Jul 29, 2006 at 03:54:44PM -0500, Jeremy Messenger wrote: > >It will be hack for reason unknown, I prefer to avoid that. > > It is not a hack and it is known reason that you need to honor CC. It is not a reason, it is a goal. The reason is the bug true nature discovered. > >I normally set CC to anything and it honors. > > How did you set? The graphics/png doesn't honor it when you add CC=foobar > in make.conf or graphics/png/Makefile. /usr/ports/graphics/png ttyp2 73_# setenv CC "gcc -g" /usr/ports/graphics/png ttyp2 74_# make ===> Extracting for png-1.2.12_1 => MD5 Checksum OK for libpng-1.2.12.tar.bz2. => SHA256 Checksum OK for libpng-1.2.12.tar.bz2. ===> Patching for png-1.2.12_1 ===> Applying FreeBSD patches for png-1.2.12_1 ===> Configuring for png-1.2.12_1 ===> Building for png-1.2.12_1 gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c png.c ^^ gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngset.c gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngget.c gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngrutil.c ^C > >You should inspect your build path step by step to find real reason of > >that bag, only after that we can find the real fix. > > I already have gave you a solution. If you don't like it then it's your > job to figure another solution as you are maintaining for this port. Solution for what? You don't describe where the bug is exactly. Since I can't reproduce this situation on my machine, I can only relay upon your inspecting to maintain this port in this matter. -- http://ache.pp.ru/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
Andrey Chernov wrote: On Sat, Jul 29, 2006 at 03:54:44PM -0500, Jeremy Messenger wrote: It will be hack for reason unknown, I prefer to avoid that. It is not a hack and it is known reason that you need to honor CC. It is not a reason, it is a goal. The reason is the bug true nature discovered. I normally set CC to anything and it honors. How did you set? The graphics/png doesn't honor it when you add CC=foobar in make.conf or graphics/png/Makefile. /usr/ports/graphics/png ttyp2 73_# setenv CC "gcc -g" /usr/ports/graphics/png ttyp2 74_# make ===> Extracting for png-1.2.12_1 => MD5 Checksum OK for libpng-1.2.12.tar.bz2. => SHA256 Checksum OK for libpng-1.2.12.tar.bz2. ===> Patching for png-1.2.12_1 ===> Applying FreeBSD patches for png-1.2.12_1 ===> Configuring for png-1.2.12_1 ===> Building for png-1.2.12_1 gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c png.c ^^ gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngset.c gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngget.c gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngrutil.c ^C You should inspect your build path step by step to find real reason of that bag, only after that we can find the real fix. I already have gave you a solution. If you don't like it then it's your job to figure another solution as you are maintaining for this port. Solution for what? You don't describe where the bug is exactly. Since I can't reproduce this situation on my machine, I can only relay upon your inspecting to maintain this port in this matter. I can't reproduce it either. [EMAIL PROTECTED] /home/tux/wrk/ports/graphics/png]# cat /etc/make.conf | head -n 6 PERL_VER=5.8.8 PERL_VERSION=5.8.8 # Kernel & Userland CC=/usr/local/bin/gcc42 [EMAIL PROTECTED] /home/tux/wrk/ports/graphics/png]# make ===> Extracting for png-1.2.8_3 => MD5 Checksum OK for libpng-1.2.8.tar.bz2. => SHA256 Checksum OK for libpng-1.2.8.tar.bz2. ===> Patching for png-1.2.8_3 ===> Applying FreeBSD patches for png-1.2.8_3 ===> Configuring for png-1.2.8_3 ===> Building for png-1.2.8_3 /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c png.c /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c pngset.c /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c pngget.c /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c pngrutil.c [...snip...] -- Cheers, Gabor ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
Andrey Chernov wrote:
> On Sat, Jul 29, 2006 at 02:59:19PM -0500, Jeremy Messenger wrote:
>> On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze <[EMAIL PROTECTED]>
>> wrote:
>>
>>> Andrey Chernov wrote:
On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
> On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]>
> wrote:
>
>> On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
>>> The port graphics/png does not honour the CC Variable.
>> I can't reproduce that, it honors CC for me.
> I can, CC=gcc will not change the CC when it compiles.
It is hard to imagine how it is ever possible. There is standard BSD
makefile.freebsd which not owervrites CC as you can see in the file.
>> No idea, I don't know png's build system so that cc must be come from
>> somewhere.
>>
>>> Is it possible that make.conf is read again?
>> I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31 line
>> should do.
>
> It will be hack for reason unknown, I prefer to avoid that.
> I normally set CC to anything and it honors.
> I never heard from somebody other than you about that problem.
> You should inspect your build path step by step to find real reason of
> that bag, only after that we can find the real fix.
>
The problem is there, without doubt. Normally bsd.port.mk only forwards CC to
the configure script (look for the do-configure target). Since the configure
target is omitted the port will not receive CC. This is why it has to be
included into the make environment. I.e. with
MAKE_ENV+= CC="${CC}"
This is not a hack, but a necessity, due to the lack of a configure step.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
[LoN]Kamikaze wrote:
Andrey Chernov wrote:
On Sat, Jul 29, 2006 at 02:59:19PM -0500, Jeremy Messenger wrote:
On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze <[EMAIL PROTECTED]>
wrote:
Andrey Chernov wrote:
On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov <[EMAIL PROTECTED]>
wrote:
On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
The port graphics/png does not honour the CC Variable.
I can't reproduce that, it honors CC for me.
I can, CC=gcc will not change the CC when it compiles.
It is hard to imagine how it is ever possible. There is standard BSD
makefile.freebsd which not owervrites CC as you can see in the file.
No idea, I don't know png's build system so that cc must be come from
somewhere.
Is it possible that make.conf is read again?
I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31 line
should do.
It will be hack for reason unknown, I prefer to avoid that.
I normally set CC to anything and it honors.
I never heard from somebody other than you about that problem.
You should inspect your build path step by step to find real reason of
that bag, only after that we can find the real fix.
The problem is there, without doubt. Normally bsd.port.mk only forwards CC to
the configure script (look for the do-configure target). Since the configure
target is omitted the port will not receive CC. This is why it has to be
included into the make environment. I.e. with
MAKE_ENV+= CC="${CC}"
This is not a hack, but a necessity, due to the lack of a configure step.
Then tell me why it works for me and for Andrey.
--
Cheers,
Gabor
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Your message to freebsd-ports awaits moderator approval
Your mail to 'freebsd-ports' with the subject Subscribe Is being held until the list moderator can review it for approval. The reason it is being held: SpamAssassin identified this message as possible spam Either the message will get posted to the list, or you will receive notification of the moderator's decision. If you would like to cancel this posting, please visit the following URL: http://lists.freebsd.org/mailman/confirm/freebsd-ports/fa30e9eb067cf13ba0a48d64f52e27a75bca82aa PLEASE NOTE! If you would like to post freely to the list, please subscribe first. If you post from multiple addresses, you can subscribe each address and go into the options page and select 'no mail' for all but one address. This will allow you to post without delay in the future. Sorry for the hassle, but certain immature people made this necessary.
Re: graphics/png - CC
Gábor Kövesdán wrote:
> [LoN]Kamikaze wrote:
>> Andrey Chernov wrote:
>>
>>> On Sat, Jul 29, 2006 at 02:59:19PM -0500, Jeremy Messenger wrote:
>>>
On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze
<[EMAIL PROTECTED]> wrote:
> Andrey Chernov wrote:
>
>> On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
>>
>>> On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov
>>> <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>
On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
> The port graphics/png does not honour the CC Variable.
>
I can't reproduce that, it honors CC for me.
>>> I can, CC=gcc will not change the CC when it compiles.
>>>
>> It is hard to imagine how it is ever possible. There is standard BSD
>> makefile.freebsd which not owervrites CC as you can see in the file.
>>
No idea, I don't know png's build system so that cc must be come
from somewhere.
> Is it possible that make.conf is read again?
>
I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31
line should do.
>>> It will be hack for reason unknown, I prefer to avoid that.
>>> I normally set CC to anything and it honors.
>>> I never heard from somebody other than you about that problem.
>>> You should inspect your build path step by step to find real reason
>>> of that bag, only after that we can find the real fix.
>>>
>>>
>>
>> The problem is there, without doubt. Normally bsd.port.mk only
>> forwards CC to the configure script (look for the do-configure
>> target). Since the configure target is omitted the port will not
>> receive CC. This is why it has to be included into the make
>> environment. I.e. with
>>
>> MAKE_ENV+= CC="${CC}"
>>
>> This is not a hack, but a necessity, due to the lack of a configure step.
>>
>>
> Then tell me why it works for me and for Andrey.
>
Because your make.conf settings are not location sensitive. Remove the setting
from your make.conf and or environment. Then try:
# make CC=/usr/local/bin/gcc42
You will see, it will not have an effect.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
[LoN]Kamikaze wrote:
Gábor Kövesdán wrote:
[LoN]Kamikaze wrote:
Andrey Chernov wrote:
On Sat, Jul 29, 2006 at 02:59:19PM -0500, Jeremy Messenger wrote:
On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze
<[EMAIL PROTECTED]> wrote:
Andrey Chernov wrote:
On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov
<[EMAIL PROTECTED]>
wrote:
On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
The port graphics/png does not honour the CC Variable.
I can't reproduce that, it honors CC for me.
I can, CC=gcc will not change the CC when it compiles.
It is hard to imagine how it is ever possible. There is standard BSD
makefile.freebsd which not owervrites CC as you can see in the file.
No idea, I don't know png's build system so that cc must be come
from somewhere.
Is it possible that make.conf is read again?
I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31
line should do.
It will be hack for reason unknown, I prefer to avoid that.
I normally set CC to anything and it honors.
I never heard from somebody other than you about that problem.
You should inspect your build path step by step to find real reason
of that bag, only after that we can find the real fix.
The problem is there, without doubt. Normally bsd.port.mk only
forwards CC to the configure script (look for the do-configure
target). Since the configure target is omitted the port will not
receive CC. This is why it has to be included into the make
environment. I.e. with
MAKE_ENV+= CC="${CC}"
This is not a hack, but a necessity, due to the lack of a configure step.
Then tell me why it works for me and for Andrey.
Because your make.conf settings are not location sensitive. Remove the setting
from your make.conf and or environment. Then try:
# make CC=/usr/local/bin/gcc42
You will see, it will not have an effect.
It does have.
[EMAIL PROTECTED] /home/tux/wrk/ports/graphics/png]# make
CC=/usr/local/bin/gcc42
===> Extracting for png-1.2.8_3
=> MD5 Checksum OK for libpng-1.2.8.tar.bz2.
=> SHA256 Checksum OK for libpng-1.2.8.tar.bz2.
===> Patching for png-1.2.8_3
===> Applying FreeBSD patches for png-1.2.8_3
===> Configuring for png-1.2.8_3
===> Building for png-1.2.8_3
/usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD
-DPNG_NO_ASSEMBLER_CODE -c png.c
/usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD
-DPNG_NO_ASSEMBLER_CODE -c pngset.c
/usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD
-DPNG_NO_ASSEMBLER_CODE -c pngget.c
The CC line in make.conf is commented out this time.
--
Cheers,
Gabor
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Sat, Jul 29, 2006 at 11:34:52PM +0200, [LoN]Kamikaze wrote: > Because your make.conf settings are not location sensitive. Remove the > setting from your make.conf and or environment. Then try: > > # make CC=/usr/local/bin/gcc42 > > You will see, it will not have an effect. /usr/ports/graphics/png ttyp0 74_# make CC="gcc -g" ===> Extracting for png-1.2.12_1 => MD5 Checksum OK for libpng-1.2.12.tar.bz2. => SHA256 Checksum OK for libpng-1.2.12.tar.bz2. ===> Patching for png-1.2.12_1 ===> Applying FreeBSD patches for png-1.2.12_1 ===> Configuring for png-1.2.12_1 ===> Building for png-1.2.12_1 gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c png.c gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngset.c -- http://ache.pp.ru/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
Gábor Kövesdán wrote:
> [LoN]Kamikaze wrote:
>> Gábor Kövesdán wrote:
>>
>>> [LoN]Kamikaze wrote:
>>>
Andrey Chernov wrote:
> On Sat, Jul 29, 2006 at 02:59:19PM -0500, Jeremy Messenger wrote:
>
>> On Sat, 29 Jul 2006 13:27:08 -0500, [LoN]Kamikaze
>> <[EMAIL PROTECTED]> wrote:
>>
>>
>>> Andrey Chernov wrote:
>>>
On Sat, Jul 29, 2006 at 01:16:47PM -0500, Jeremy Messenger wrote:
> On Fri, 28 Jul 2006 18:35:14 -0500, Andrey Chernov
> <[EMAIL PROTECTED]>
> wrote:
>
>
>> On Fri, Jul 28, 2006 at 11:40:10AM +0200, [LoN]Kamikaze wrote:
>>
>>> The port graphics/png does not honour the CC Variable.
>>>
>> I can't reproduce that, it honors CC for me.
>>
> I can, CC=gcc will not change the CC when it compiles.
>
It is hard to imagine how it is ever possible. There is standard
BSD
makefile.freebsd which not owervrites CC as you can see in the
file.
>> No idea, I don't know png's build system so that cc must be come
>> from somewhere.
>>
>>
>>> Is it possible that make.conf is read again?
>>>
>> I think, add "CC=${CC}" in graphics/png/Makefile's MAKE_ENV at 31
>> line should do.
>>
> It will be hack for reason unknown, I prefer to avoid that.
> I normally set CC to anything and it honors.
> I never heard from somebody other than you about that problem.
> You should inspect your build path step by step to find real reason
> of that bag, only after that we can find the real fix.
>
>
The problem is there, without doubt. Normally bsd.port.mk only
forwards CC to the configure script (look for the do-configure
target). Since the configure target is omitted the port will not
receive CC. This is why it has to be included into the make
environment. I.e. with
MAKE_ENV+= CC="${CC}"
This is not a hack, but a necessity, due to the lack of a configure
step.
>>> Then tell me why it works for me and for Andrey.
>>>
>>>
>>
>> Because your make.conf settings are not location sensitive. Remove the
>> setting from your make.conf and or environment. Then try:
>>
>> # make CC=/usr/local/bin/gcc42
>>
>> You will see, it will not have an effect.
>>
> It does have.
>
> [EMAIL PROTECTED] /home/tux/wrk/ports/graphics/png]# make
> CC=/usr/local/bin/gcc42
> ===> Extracting for png-1.2.8_3
> => MD5 Checksum OK for libpng-1.2.8.tar.bz2.
> => SHA256 Checksum OK for libpng-1.2.8.tar.bz2.
> ===> Patching for png-1.2.8_3
> ===> Applying FreeBSD patches for png-1.2.8_3
> ===> Configuring for png-1.2.8_3
> ===> Building for png-1.2.8_3
> /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD
> -DPNG_NO_ASSEMBLER_CODE -c png.c
> /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD
> -DPNG_NO_ASSEMBLER_CODE -c pngset.c
> /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD
> -DPNG_NO_ASSEMBLER_CODE -c pngget.c
>
>
> The CC line in make.conf is commented out this time.
>
Now I am confused, it works for me as well. Only my settings in make.conf are
ignored.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: graphics/png - CC
On Sat, 29 Jul 2006 16:07:40 -0500, Gábor Kövesdán <[EMAIL PROTECTED]> wrote: Andrey Chernov wrote: On Sat, Jul 29, 2006 at 03:54:44PM -0500, Jeremy Messenger wrote: It will be hack for reason unknown, I prefer to avoid that. It is not a hack and it is known reason that you need to honor CC. It is not a reason, it is a goal. The reason is the bug true nature discovered. I normally set CC to anything and it honors. How did you set? The graphics/png doesn't honor it when you add CC=foobar in make.conf or graphics/png/Makefile. /usr/ports/graphics/png ttyp2 73_# setenv CC "gcc -g" /usr/ports/graphics/png ttyp2 74_# make ===> Extracting for png-1.2.12_1 => MD5 Checksum OK for libpng-1.2.12.tar.bz2. => SHA256 Checksum OK for libpng-1.2.12.tar.bz2. ===> Patching for png-1.2.12_1 ===> Applying FreeBSD patches for png-1.2.12_1 ===> Configuring for png-1.2.12_1 ===> Building for png-1.2.12_1 gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c png.c ^^ gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngset.c gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngget.c gcc -g -O2 -fno-strict-aliasing -pipe -march=pentium4 -march=pentium4 -c pngrutil.c ^C You should inspect your build path step by step to find real reason of that bag, only after that we can find the real fix. I already have gave you a solution. If you don't like it then it's your job to figure another solution as you are maintaining for this port. Solution for what? You don't describe where the bug is exactly. Since I can't reproduce this situation on my machine, I can only relay upon your inspecting to maintain this port in this matter. I can't reproduce it either. Forgive me, guys. I mixed up with between my system and jail make.conf. Now I can't reproduce it. # cat /etc/make.conf | grep CC CC=gcc # pwd /usr/ports/graphics/png # make ===> Extracting for png-1.2.12_1 => MD5 Checksum OK for libpng-1.2.12.tar.bz2. => SHA256 Checksum OK for libpng-1.2.12.tar.bz2. ===> Patching for png-1.2.12_1 ===> Applying FreeBSD patches for png-1.2.12_1 ===> Configuring for png-1.2.12_1 ===> Building for png-1.2.12_1 gcc -O2 -fno-strict-aliasing -pipe -g -c png.c [...] Cheers, Mezz [EMAIL PROTECTED] /home/tux/wrk/ports/graphics/png]# cat /etc/make.conf | head -n 6 PERL_VER=5.8.8 PERL_VERSION=5.8.8 # Kernel & Userland CC=/usr/local/bin/gcc42 [EMAIL PROTECTED] /home/tux/wrk/ports/graphics/png]# make ===> Extracting for png-1.2.8_3 => MD5 Checksum OK for libpng-1.2.8.tar.bz2. => SHA256 Checksum OK for libpng-1.2.8.tar.bz2. ===> Patching for png-1.2.8_3 ===> Applying FreeBSD patches for png-1.2.8_3 ===> Configuring for png-1.2.8_3 ===> Building for png-1.2.8_3 /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c png.c /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c pngset.c /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c pngget.c /usr/local/bin/gcc42 -O -pipe -I. -DPNG_USE_PNGGCCRD -DPNG_NO_ASSEMBLER_CODE -c pngrutil.c [...snip...] -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Errors in net/gnat
On Sat, 29 Jul 2006 11:35:12 +1000 Nick Withers <[EMAIL PROTECTED]> wrote: Dear Nick Withers With the below answer you have hit the nail right on the head! Thank you very much for this information. Dear Daniel Eischen Thank you for looking into the problem after all. I believe this problem will be solved for all future users :-) Best and kind regards Rico > On Fri, 28 Jul 2006 18:04:55 -0400 (EDT) > Daniel Eischen <[EMAIL PROTECTED]> wrote: > > > I just upgraded one of our production servers to 6.1-stable > > from sources last night. The ports tree was also updated. > > lang/gnat built and installed just fine on this box. > > > > My /etc/make.conf: > > > > CFLAGS+=-O -pipe > > # added by use.perl 2006-05-25 14:04:34 > > PERL_VER=5.8.8 > > PERL_VERSION=5.8.8 > > > > The way I built it was: > > > > bash $ cd /usr/ports/lang/gnat > > Ah, see, you're using a Bourne-compatible shell, bash. Your > SHELL environment variable will be set to "/usr/local/bin/bash" > or some such and the GNAT port will invoke it to execute > the "/usr/ports/lang/gnat/work/gcc-34/gcc/fixinc/genfixes" > script, which'll work, since bash (as a Bourne-style shell) > recognises input like 'SHELL="/bin/sh"', whereas csh doesn't. > > I reckon if you set your SHELL environment variable to > "/bin/csh" you'll run into problems with the make. > > > bash $ sudo make > > bash $ sudo make install > -- > Nick Withers > email: [EMAIL PROTECTED] > Web: http://www.nickwithers.com > Mobile: +61 414 397 446 > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
mplayer port, compliation error
Hi, When compiling mplayer, I get the following error(s): font_load_ft.c:30:35: fontconfig/fontconfig.h: No such file or directory font_load_ft.c:93:1: warning: "ALIGN" redefined In file included from /usr/include/sys/param.h:109, from ../bswap.h:5, from font_load_ft.c:33: /usr/include/machine/param.h:79:1: warning: this is the location of the previous definition font_load_ft.c: In function `decode_char': font_load_ft.c:745: warning: passing arg 2 of `libiconv' from incompatible pointer type font_load_ft.c: In function `load_font_ft': font_load_ft.c:1133: error: `FcPattern' undeclared (first use in this function) font_load_ft.c:1133: error: (Each undeclared identifier is reported only once font_load_ft.c:1133: error: for each function it appears in.) font_load_ft.c:1133: error: `fc_pattern' undeclared (first use in this function) font_load_ft.c:1134: error: `FcChar8' undeclared (first use in this function) font_load_ft.c:1134: error: `s' undeclared (first use in this function) font_load_ft.c:1135: error: syntax error before "scalable" font_load_ft.c:1153: error: `FcMatchPattern' undeclared (first use in this function) font_load_ft.c:1156: error: `FC_SCALABLE' undeclared (first use in this function) font_load_ft.c:1156: error: `scalable' undeclared (first use in this function) font_load_ft.c:1157: error: `FcTrue' undeclared (first use in this function) font_load_ft.c:1164: error: `FC_FILE' undeclared (first use in this function) gmake[1]: *** [font_load_ft.o] Error 1 gmake[1]: Leaving directory `/usr/ports/multimedia/mplayer/work/MPlayer-1.0pre8/libvo' gmake: *** [libvo/libvo.a] Error 2 *** Error code 2 System: FreeBSD 6.1-RELEASE i386 This appears to be the exact same error as this guy: http://lists.freebsd.org/pipermail/freebsd-ports/2006-March/030048.html However, I have tried the suggested patch (and of course fontconfig is installed) with no luck. I am installing this without x11 / GUI. I'm guessing I have to copy the fontconfig directory somewhere or something? Any ideas? Thanks in advance, Adam McCann -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.394 / Virus Database: 268.10.5/403 - Release Date: 28/07/2006 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Ruby vulnerability?
Dear Sirs, > CVE report is very unpleasant: "Multiple unspecified vulnerabilities". > Secunia has more professional report. > > RedHat is only vendor who released updates, but they are binary. So, > there is no known fix now. Following information maybe help you: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=378029 But matz(ruby creator) has not mentioned about this yet. And he has said that he has no will to release patch for the vulnerabilites. http://blade.nagaokaut.ac.jp/cgi-bin/scat.rb/ruby/ruby-list/42575 The message is in Japanese and the content is as follows. At present, a patch for these vulnerabilites is not ready because the problems occur only with $SAFE=4. So the vulnerabilities will be serious only when alll the following conditions are satisfied. * You use $SAFE=4 sandbox * You run untrusted codes > I hope ruby team will release 1.8.5 ASAP. On 18th July, ruby 1.8.5 preview2 was released and release date of 1.8.5 will be near middle of August if they works on schedule. Best regards. - UEDA Hiroyuki <[EMAIL PROTECTED]> ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
