Re: lang/gcc48 fails to build [on HEAD]

[Rainer Hurling]

Am 09.11.15 um 11:06 schrieb Gerald Pfeifer:
> Hi Rainer,
> 
> On Mon, 9 Nov 2015, Rainer Hurling wrote:
>> I am using lang/gcc48 for a long time now on FreeBSD 11.0-CURRENT. From 
>> time to time I have to rebuild the port. This is the first time, that I 
>> get the following error:
> 
> I have no idea where this is coming from.  In fact, I rebuilt
> the lang/gcc port just last night (which is pretty much the same)
> and did not run into this.
> 
>> Is this a known error? It seems, there is something odd with C++ mode 
>> and C files?
> 
> GCC now is built as C++ code, even though most source files have
> not been renamed from .c.  So this warning is expected and can be
> ignored.
> 
> This being an old port, nothing has changed on the GCC side.  Which
> means something in -CURRENT must have broken it.
> 
> Gerald
> 

I think I found the problem.

In my initial mail of this thread, I reported, that after upgrading
Freebsd 11.0-CURRENT to r290538 (including locale and localedef updates)
I am not able to build lang/gccXX any more. All I get are errors like
that in usr/ports/lang/gccXX/work/build/gcc:


In file included from .././../gcc-4.8.5/gcc/genflags.c:26:
In file included from ./tm.h:16:
./options.h:4293:3: error: redefinition of enumerator 'OPT_C'
  OPT_C = 129,   /* -C */
  ^


After more than 20 of them the build stops with
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.


This is with locale for Germany:
LANG=de_DE.UTF-8
LC_CTYPE="de_DE.UTF-8"
LC_COLLATE="de_DE.UTF-8"
LC_TIME="de_DE.UTF-8"
LC_NUMERIC="de_DE.UTF-8"
LC_MONETARY="de_DE.UTF-8"
LC_MESSAGES="de_DE.UTF-8"
LC_ALL=


If I use 'LC_COLLATE="C"' for the build, the build works fine again:

cd /usr/ports/lang/gcc48
env LC_COLLATE="C" make
...


So it seems, that something with the new 'locale' code in base of HEAD
is not working as expected here? (At least for other locales than US?)

I added bapt@, because he is the author introducing the new code into HEAD.

Hope, my explanations are clear enough to get the problem. Please feel
free to ask for more information, if needed.

Regards,
Rainer Hurling

___
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: Suggestion for FreeBSD ports - Autokey

[Chris H]

On Tue, 10 Nov 2015 12:12:35 -0800 "Chris H"  wrote

> On Tue, 10 Nov 2015 11:38:09 +0200 PeerCorps Trust Fund
>  wrote
> 
> > Hi All,
> > 
> > One extremely useful keyboard automation utility that has existed for Linux
> > for quite some time has been Autokey: https://code.google.com/p/autokey/
> Looks interesting.
> > 
> > I am not sure how suggesting ports works,
> You're on the right track. :)
> > but I'd like to suggest this one for inclusion.
> So noted. I'm going to clone it to my gitlab account, and contact
> the author(s). To see how best I might direct my efforts from (t)here.

Oh! Looks like koobs@ beat me to it. :)
Revealing https://github.com/guoci/autokey-py3

Good job koobs!
> 
> >
> > -- 
> > Mike
> > 
--Chris


___
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: Suggestion for FreeBSD ports - Autokey

[Chris H]

On Tue, 10 Nov 2015 11:38:09 +0200 PeerCorps Trust Fund
 wrote

> Hi All,
> 
> One extremely useful keyboard automation utility that has existed for Linux
> for quite some time has been Autokey: https://code.google.com/p/autokey/
Looks interesting.
> 
> I am not sure how suggesting ports works,
You're on the right track. :)
> but I'd like to suggest this one for inclusion.
So noted. I'm going to clone it to my gitlab account, and contact
the author(s). To see how best I might direct my efforts from (t)here.

>
> -- 
> Mike
> 
--Chris


___
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: Hi, I'd like to update the coreos-etcd port!

[Mark Linimon]

On Tue, Nov 10, 2015 at 09:36:48AM -0500, John Barker wrote:
> I went through the earlier steps about finding any outstanding issues, I
> can't see any pending PRs here:
> http://portsmon.freebsd.org/portoverview.py?category=devel=etcd=
> am I looking for it wrong?

No, that should be correct.  You can always use bugzilla to make sure
that portsmon has gotten it right:

  https://bugs.freebsd.org/bugzilla/query.cgi

> The next step in the guide is:
> 
> > If there is no pending PR, the next step is to send an email to the
> > port's maintainer, as shown by make maintainer.

I've always hated that advice :-)  I'd say open a PR.  It gives much
more information as an audit trail.

There is another reference you might want to look at:

  https://wiki.freebsd.org/KubilayKocak/ThePerfectPortsIssue

mcl
___
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: Hi, I'd like to update the coreos-etcd port!

[Big Lebowski]

Hi John,

There's a bit more in that than simply updating the port, and it simply
needs some more of my time. Also, mind, that emailing the maintainer
directly is not the best way of communication, you'd be better if you've
created a PR and/or review for it (one already exists and waits for me to
have some more time).

Said all that, I am working on it ;)

Cheers!

On Mon, Nov 9, 2015 at 8:25 PM, John Barker  wrote:

> Hi there,
>
> I'm interested in updating the coreos-etcd package of FreeBSD and it seems
> like the current maintainer (ro...@freebsd.org) is not responding to email
> right now.
>
> I tried to do this with port submit, but got this:
>
> > # port submit
> > Port submit is currently broken
>
> See forwarded email below.
>
> Cheers,
> John
>
> -- Forwarded message --
> From: John Barker 
> Date: Tue, Nov 3, 2015 at 5:07 PM
> Subject: Hi, I'd like to update the coreos-etcd port!
> To: ro...@freebsd.org
>
>
> Hey there,
>
> This is my first time contributing anything to FreeBSD so I hope I’ve done
> everything right.
>
> The port coreos-etcd is currently building 0.4.6 and I’d like to update
> this to 2.2.1. I’ve included a patch, which I’ve tested on my FreeBSD 10.2
> instance. I didn’t see any evidence of any intention to update, and it
> looks like the last change to the makefile was from 2014.
>
> This may require a manual upgrade to one’s local etcd data if they’ve been
> running 0.4.6. Is that a concern we need to address via ports?
>
> Any thing I’ve missed?
>
> Hope to hear back from you soon!
>
> Cheers,
> John
>
>
>
>
>
> --
>
>
> *John Barker*
>
> Enigma  | Software Engineer
>
> (954) 205-6472 <9542056472>
>
> ___
> 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"

Suggestion for FreeBSD ports - Autokey

[PeerCorps Trust Fund]

Hi All,

One extremely useful keyboard automation utility that has existed for Linux for 
quite some time has been Autokey: https://code.google.com/p/autokey/

I am not sure how suggesting ports works, but I'd like to suggest this one for 
inclusion.

-- 
Mike

___
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: Suggestion for FreeBSD ports - Autokey

[Kubilay Kocak]

On 10/11/2015 8:38 PM, PeerCorps Trust Fund wrote:
> Hi All,
> 
> One extremely useful keyboard automation utility that has existed for Linux 
> for quite some time has been Autokey: https://code.google.com/p/autokey/
> 
> I am not sure how suggesting ports works, but I'd like to suggest this one 
> for inclusion.
> 

Hi Mike,

It looks like an updated verion of autokey (ported to Python 3) exists here:

https://github.com/guoci/autokey-py3

It's also available in PyPI as:

https://pypi.python.org/pypi/autokey-py3

This means it should be `pip install`able and that it should be pretty
easy to create a port for.

If you can provide confirmation that it functions on FreeBSD as is (via
pip install) I'd be happy to look at creating a port for it.

You can find me and other FreeBSD/Python folks on IRC:

#freebsd-python @ freenode

See you there!

./koobs
___
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: Hi, I'd like to update the coreos-etcd port!

[John Barker]

On Tue, Nov 10, 2015 at 4:51 AM, Big Lebowski 
wrote:

> Hi John,
>
> There's a bit more in that than simply updating the port, and it simply
> needs some more of my time. Also, mind, that emailing the maintainer
> directly is not the best way of communication, you'd be better if you've
> created a PR and/or review for it (one already exists and waits for me to
> have some more time).
>

Ahh, I'm looking at this here:
https://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/port-upgrading.html

I went through the earlier steps about finding any outstanding issues, I
can't see any pending PRs here:
http://portsmon.freebsd.org/portoverview.py?category=devel=etcd=
am I looking for it wrong?

The next step in the guide is:

> If there is no pending PR, the next step is to send an email to the
port's maintainer, as shown by make maintainer.

perhaps it could be revised to indicate that you should prefer to open a PR
first?


>
> Said all that, I am working on it ;)
>

Thank you, it's appreciated!


>
> Cheers!
>
> On Mon, Nov 9, 2015 at 8:25 PM, John Barker  wrote:
>
>> Hi there,
>>
>> I'm interested in updating the coreos-etcd package of FreeBSD and it seems
>> like the current maintainer (ro...@freebsd.org) is not responding to
>> email
>> right now.
>>
>> I tried to do this with port submit, but got this:
>>
>> > # port submit
>> > Port submit is currently broken
>>
>> See forwarded email below.
>>
>> Cheers,
>> John
>>
>> -- Forwarded message --
>> From: John Barker 
>> Date: Tue, Nov 3, 2015 at 5:07 PM
>> Subject: Hi, I'd like to update the coreos-etcd port!
>> To: ro...@freebsd.org
>>
>>
>> Hey there,
>>
>> This is my first time contributing anything to FreeBSD so I hope I’ve done
>> everything right.
>>
>> The port coreos-etcd is currently building 0.4.6 and I’d like to update
>> this to 2.2.1. I’ve included a patch, which I’ve tested on my FreeBSD 10.2
>> instance. I didn’t see any evidence of any intention to update, and it
>> looks like the last change to the makefile was from 2014.
>>
>> This may require a manual upgrade to one’s local etcd data if they’ve been
>> running 0.4.6. Is that a concern we need to address via ports?
>>
>> Any thing I’ve missed?
>>
>> Hope to hear back from you soon!
>>
>> Cheers,
>> John
>>
>>
>>
>>
>>
>> --
>>
>>
>> *John Barker*
>>
>> Enigma  | Software Engineer
>>
>> (954) 205-6472 <9542056472>
>>
>> ___
>> 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"
>>
>
>


-- 


*John Barker*

Enigma  | Software Engineer

(954) 205-6472 <9542056472>
___
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: Call for Help: need script for patching ports tree, building with poudriere

[Ricky G]

 Almost finished with this, just wanted to give an update. I named this script 
portest, I still need to add a few more things and do some bug testing but so 
far it seems to work pretty well. This is the usage page for the script.
Usage: portest [-f bulkfile] [-apPrRtv] patchfile
Options:-a --  Do everything except revert (-ptf build.ports.txt)-f 
--  Generate a poudiere usable bulk file-p --  Patch and give 
output-P --  Do not exit on failed patch-r --  Revert the files 
listed in patchfile-R --  Paranoid revert, will remove and restore 
anything and   everything the patchfile may have changed or added   
 -t --  Test with portlint-v --  Show version of portest
By default, (no options) portest shows the ports that will be modified

 Decided to add the -a option to do the task you asked for specifically. So far 
every option works on the patch you supplied and several others I had laying 
around. One thing that it will not detect is if slave port will be affected by 
the change, also changes to Uses or any other non CAT/PORT directory will not 
be detected. I'm still trying to figure out how to solve these problem. Are 
they important? or not so much?
 Right now on my todo is to add a config file to change the default settings, 
Add a -T option that will do port test or poudrieretesting depending on what 
was selected in the config file. Also later on choose between svn, git or 
portsnap. Once i'm finished adding the config file ill post it for some testing 
and if you can give me some feedback on what else you need or don't like.
Ultima
Date: Mon, 9 Nov 2015 13:55:38 -0800
Subject: Re: Call for Help: need script for patching ports tree, building with 
poudriere
From: rodr...@freebsd.org
To: ricky1...@hotmail.com
CC: freebsd-test...@freebsd.org; freebsd-ports@freebsd.org

On Sun, Nov 8, 2015 at 6:18 PM, Ricky G  wrote:



Hello, 
 Started working on a simple sh script to do as requested. So far have 1,2,4,5 
complete. There is much error checking to be added still though. Wanted to ask 
a few things first.
2- Does port tree checkout matter? Right now my script assumes svnlite 
generated the patch at the root of the tree5- Does duplicates matter? poudriere 
doesn't care but is this strictly for poudriere?6- How should the output be 
handled?

The script should not worry about the port tree checkout so much,
since that will probably be done outside the script.  For now, if the script
assumes that the port checkout is an SVN tree, and you can run SVN operations 
on it, that should be sufficient.

For duplicates, I don't think it matters so much.  I believe poudriere is smart 
enough so that if you pass it a list of ports with duplicate entries,
it does the right thing.

At this point, the output format is not so important.  For now,
making sure that error status is propagated as a return value from
the script (0 on success, non-zero on failure) is a good start.

The only other suggestion that I have is that when you work on the
script, make sure that you put a proper license in it (BSD license preferred).

Thanks.

--
Craig
  
___
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"