Re: maintenance of gcc cross ports
I do think it probably makes sense to divorce the baremetal GCC ports from
powerpc64-gcc and let powerpc64-gcc just be the basis for FreeBSD-specific
toolchains.
On 5/19/19 10:48 AM, James Shuriff wrote:
> I have a Raspberry Pi 3 model b. I use the LLVM toolchain to build the system
> but the GNU toolchain is required to build U-Boot. U-Boot uses global
> register variables and LLVM doesn't support this. sysutils/u-boot-pine64 does
> use aarch64-none-elf-gcc, for the same reason. The family is allwinner64 and
> that's set to use aarch64-none-elf-gcc. Here is an article explaining the
> feature U-Boot uses that's not in LLVM (the reason GNU is required for
> building it):
>
> https://gcc.gnu.org/onlinedocs/gcc/Global-Register-Variables.html
>
> Aarch64 is a Tier 2 architecture. The toolchain should have an active
> maintainer (the maintainer is listed as po...@freebsd.org). I've opened a bug
> report for the bugs in the Makefile. We should be using a newer toolchain or
> separate arm-none-eabi and aarch64-none-elf from powerpc64. I am guessing the
> Makefile bugs occurred because the original designer didn't intend on
> powerpc64-gcc being used for targets like arm-none-eabi and aarch64-none-elf.
> The patches you pointed out before don't even have any effect on the bare
> metal ports. The arm and aarch64 bare metal ports are the oddballs in the
> group. The difference being: powerpc64-gcc, aarch64-gcc, amd64-gcc, i386-gcc,
> mips*-gcc, and sparc64-gcc are all intended for, as you said Mark, alternate
> toolchain work with FreeBSD. These are not the official toolchains for
> FreeBSD and I can see why they don't have the same level of care as the
> official toolchain. But the side effect of this is arm-none-eabi-gcc and
> aarch64-none-elf-gcc recei
ve the same level of support, though they are *required* to build most FreeBSD
systems on those platforms.
>
> - James Shuriff
>
> -Original Message-
> From: Mark Millard
> Sent: Sunday, May 19, 2019 11:46 AM
> To: James Shuriff
> Cc: ports-list freebsd ; b...@freebsd.org;
> j...@freebsd.org
> Subject: Re: maintenance of gcc cross ports
>
>
>
> On 2019-May-19, at 07:40, James Shuriff wrote:
>
>> I didn't/don't plan on touching binutils. Binutils is okay. I made new
>> patches as well. What I'm really concerned with bringing up to date is
>> aarch64-none-elf-gcc.
>
>> The GNU toolchain is unfortunately required for building an Aarch64
>> system
>
> Are you specifically referencing contexts that need to build u-boot? (My
> guess is: yes.)
>
> I've done buildworld buildkernel based on system clang and lld many times in
> the past, though not very recently. (I currently do not have access to the
> environment but will again, eventually.)
>
> For aarch64 I'd mostly recently built for and used:
>
> A) a Pine64+ 2GB (needs: sysutils/u-boot-pine64 )
> B) an OverDrive 1000 (no u-boot build needed)
>
> I've done amd64->aarch64 cross builds and self hosted ones for/on such. The
> OverDrive 1000 builds did not involve devel/aarch64-none-elf-gcc at all as
> far as I can remember.
>
>> and is a prereq for a bunch of sysutils arm ports.
>
> Yep.
>
> Are there sysutils/u-boot-* 's that no longer build under gcc 6.4.0?
> Other things?
>
>> At worst we can do something like what's done with the lang ports gcc6,
>> gcc7, gcc8. I've CC'd the maintainers so hopefully they can give us some
>> input and we can come up with a solution.
>>
>> As for Makefile issues, this is only an issue for the arm-none-eabi-gcc and
>> aarch64-none-elf-gcc ports because they have multiple hyphens. It's mostly a
>> cosmetic issue. Each port has its own plist because gcc generates different
>> headers depending on the platform so the PLIST TARGETARCH regex doesn't
>> really affect all that much. There are some clang flags dependent on
>> TARGETARCH but whoever wrote the aarch64-none-elf-gcc port must have known
>> it wasn't working in the master because the check is in the bare metal port
>> as well. The stripping out of all hyphens causes things like "gcc version
>> 6.4.0 (FreeBSD Ports Collection for aarch64noneelf)". I use
>> ${PKGNAMEPREFIX:C/-$//} for the comment and version and
>> ${PKGNAMEPREFIX:C/-.*//} for TARGETARCH. The original regex for all of those
>> is ${PKGNAMEPREFIX:C/-//g} and I'm sure you can see how that's a problem
>> when there's multiple hyphens.
>
> Thanks for the notes.
>
>> - James Shuriff
>>
>> -Original Message-
>> From: Mark Millard
>> Sent: Sunday, May 19, 2019 1:33 AM
>> To: James Shuriff ; ports-list freebsd
>>
>> Subject: Re: maintenance of gcc cross ports
>>
>> James Shuriff james at opentech.cc wrote on Sat May 18 12:29:22 UTC 2019 :
>>
>>> The powerpc64-gcc port and all the ports that use it as a master
>>> (aarch64-gcc, aarch64-none-elf-gcc, amd64-gcc, arm-none-eabi-gcc, i386-gcc,
>>> mips-gcc, mips64-gcc, and sparc64-gcc) are very old and use buggy
>>> makefiles. I would like to
Re: Looking to port weasyprint
Hi! > Thanks, but it does not work, yet: > > $ weasyprint http://weasyprint.org /tmp/weasyprint-website.pdf [...] I tried, and it looks difficult to fix quickly. It needs www/py-cssselect2 (which does not yet exist) and graphics/py-cairocffi (same problem), both have further dependencies, like textproc/py-tinycss2 (not existing, either). There are probably more things like that. So this will take a while. -- p...@opsec.eu+49 171 3101372One year to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Looking to port weasyprint
Hi! > > > A simple testbuild in poudriere after some cleanup seems to work. > > > I'm testbuilding right now. > > > > Committed as r502116, print/py-weasyprint, with the following > > description: [...] > Thanks, but it does not work, yet: > > $ weasyprint http://weasyprint.org /tmp/weasyprint-website.pdf Ah, thanks! I'll have a look now. -- p...@freebsd.org +49 171 3101372 One year to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Looking to port weasyprint
looks like it's not installing CairoSVG Sent from my a tiny pocket computer. > On May 20, 2019, at 07:28, Lars Engels wrote: > >> On Mon, May 20, 2019 at 04:00:00PM +0200, Kurt Jaeger wrote: >> Hi! >> >>> A simple testbuild in poudriere after some cleanup seems to work. >>> I'm testbuilding right now. >> >> Committed as r502116, print/py-weasyprint, with the following >> description: >> >> WeasyPrint helps web developers to create PDF documents. It turns simple >> HTML pages into gorgeous PDF. >> >> WWW: https://weasyprint.org/ >> > > Thanks, but it does not work, yet: > > $ weasyprint http://weasyprint.org /tmp/weasyprint-website.pdf > > Traceback (most recent call last): > File "/usr/local/bin/weasyprint", line 6, in >from pkg_resources import load_entry_point > File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 3241, in >@_call_aside > File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 3225, in _call_aside >f(*args, **kwargs) > File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 3254, in _initialize_master_working_set >working_set = WorkingSet._build_master() > File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 583, in _build_master >ws.require(__requires__) > File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 900, in require >needed = self.resolve(parse_requirements(requirements)) > File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", > line 786, in resolve >raise DistributionNotFound(req, requirers) > pkg_resources.DistributionNotFound: The 'CairoSVG>=1.0.20' distribution was > not found and is required by WeasyPrint > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Looking to port weasyprint
On Mon, May 20, 2019 at 04:00:00PM +0200, Kurt Jaeger wrote: > Hi! > > > A simple testbuild in poudriere after some cleanup seems to work. > > I'm testbuilding right now. > > Committed as r502116, print/py-weasyprint, with the following > description: > > WeasyPrint helps web developers to create PDF documents. It turns simple > HTML pages into gorgeous PDF. > > WWW: https://weasyprint.org/ > Thanks, but it does not work, yet: $ weasyprint http://weasyprint.org /tmp/weasyprint-website.pdf Traceback (most recent call last): File "/usr/local/bin/weasyprint", line 6, in from pkg_resources import load_entry_point File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3241, in @_call_aside File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3225, in _call_aside f(*args, **kwargs) File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 3254, in _initialize_master_working_set working_set = WorkingSet._build_master() File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 583, in _build_master ws.require(__requires__) File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 900, in require needed = self.resolve(parse_requirements(requirements)) File "/usr/local/lib/python3.6/site-packages/pkg_resources/__init__.py", line 786, in resolve raise DistributionNotFound(req, requirers) pkg_resources.DistributionNotFound: The 'CairoSVG>=1.0.20' distribution was not found and is required by WeasyPrint ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Looking to port weasyprint
Hi! > A simple testbuild in poudriere after some cleanup seems to work. > I'm testbuilding right now. Committed as r502116, print/py-weasyprint, with the following description: WeasyPrint helps web developers to create PDF documents. It turns simple HTML pages into gorgeous PDF. WWW: https://weasyprint.org/ -- p...@opsec.eu+49 171 3101372One year to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Looking to port weasyprint
Hi! > I tried creating this port butI am new to FreeBSD ports (I am a NetBSD > committer) and I can't seem to make this work. I can get the package > built but it has lots of errors. What type of errors do you get ? Did you test the build using poudriere ? > Here is my attempt. Can anyone help > and, once working, commit it? A simple testbuild in poudriere after some cleanup seems to work. I'm testbuilding right now. -- p...@opsec.eu+49 171 3101372One year to go ! ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Looking to port weasyprint
I tried creating this port butI am new to FreeBSD ports (I am a NetBSD
committer) and I can't seem to make this work. I can get the package
built but it has lots of errors. Here is my attempt. Can anyone help
and, once working, commit it?
# Created by: D'Arcy Cain
# $FreeBSD$
PORTNAME= weasyprint
PORTVERSION=47
CATEGORIES= print python
MASTER_SITES= CHEESESHOP
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
DISTNAME= WeasyPrint-${PORTVERSION}
MAINTAINER= da...@druid.net
COMMENT=Converts HTML/CSS documents to PDF
LICENSE=BSD3CLAUSE
USE_GNOME= pango
RUN_DEPENDS+=
${PYTHON_PKGNAMEPREFIX}cssselect>=0.1:www/py-cssselect@${PY_FLAVOR}
RUN_DEPENDS+=
${PYTHON_PKGNAMEPREFIX}html5lib>=0.9:www/py-html5lib@${PY_FLAVOR}
RUN_DEPENDS+= ${PYTHON_PKGNAMEPREFIX}pdfrw>=0.4:textproc/py-pdfrw@${PY_FLAVOR}
RUN_DEPENDS+= ${PYTHON_PKGNAMEPREFIX}pyphen>=0.8:textproc/py-pyphen@${PY_FLAVOR}
RUN_DEPENDS+=
${PYTHON_PKGNAMEPREFIX}tinycss>=0.4:textproc/py-tinycss@${PY_FLAVOR}
USES= python
USE_PYTHON= distutils autoplist
.include
--
D'Arcy J.M. Cain | Democracy is three wolves
http://www.druid.net/darcy/| and a sheep voting on
+1 416 788 2246 (DoD#0082)(eNTP) | what's for dinner.
IM: da...@vex.net, VoIP: sip:da...@druid.net
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: games/dMagnetic: A new Port (Need help)
Hello. SInce the ports@ mailinglist seems to strip away attachments (as it should), I uploaded the port to my website. Please download it at http://www.dettus.net/dMagnetic/freebsd_games_dMagnetic.tar.gz sha256: df886bd85e30dc983ae7ab8d441db779355c63fe14c2117797c9889f23a9a00a, size=987 bytes. Thomas Dettbarn On 5/20/19 4:17 AM, dettus wrote: Hello. My name is Thomas Dettbarn. Two of my projects editors/dhex and games/nInvaders have already found their way into the FreeBSD ports. Currently, I am working on dMagnetic, A Magic Scrolls Interpreter. This one lets you play classic text adventures such as "The Pawn" or "The Guild of Thieves" in a terminal. (As well as "Fish!", "Myth", "Corruption", "Jinxter" and "Wonderland") You can see some of the BEAUTIFUL screenshots on my website: http://www.dettus.net/dMagnetic. Please have a look. For this, I created the inkling of an already working FreeBSD port. You should find it attached to this email. Since I primarily see myself as a "developer", rather than a "maintainer", I would like to hand this one of to someone more experienced. Plus, I had some issues when I tried adding extra files such as the README.txt or an .ini file to the do-install target. so, please please help me out here guys! It would be an honor. Thomas Dettbarn ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
