Re: 'porting' AMD compiler suite
On 14/04/2016 05:38, William A. Mahaffey III wrote: > All seems OK w/ the system headers (I know, shocking ), the required files > defining a '__uintptr_t' are in fact unconditionally included, so it must be > something else (bad defines somewhere, or ). I am still chasing Apologies, but are you serious?.. $ fgrep -r __uintptr_t /usr/include/ ... /usr/include/x86/_types.h:typedef __uint64_t __uintptr_t; /usr/include/x86/_types.h:typedef __uint32_t __uintptr_t; ... This is on an amd64 head system. -- Andriy Gapon ___ 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: FreeBSD Port: apache24-2.4.20
On 2016-04-14 05:22, Ken J. wrote: > Is it possible to update/patch Apache24 with the latest backport? > > As it stands now, mod_status is completely useless without this patch. > > http://svn.apache.org/viewvc?view=revision&revision=1739008 > > Ken Hi Ken, I have to investigate the patch. However in case you build your own ports you can grep the patch from here http://people.freebsd.org/~ohauer/diffs/patch-scoreboard-r1739008 copy it to ports/www/apache24/files/ and rebuild the port. -- Regards, olli ___ 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: FreeBSD Port: tcc-0.9.26_3
On Wed, Apr 13, 2016 at 5:21 PM, Ben Wiederhake
wrote:
> Hello,
>
> "#include " seems to be impossible with tcc on FreeBSD.
>
> Steps to reproduce:
> Try to compile the following program:
> """
> #include
> #include
> int main(void){printf("Hello world\n");}
> """
>
> Excepted results:
> Compilation finishes with no errors.
>
> Actual results:
> """
> In file included from foo.c:1:
> In file included from /usr/include/stdint.h:33:
> In file included from /usr/include/sys/_types.h:33:
> In file included from /usr/include/machine/_types.h:6:
> /usr/include/x86/_types.h:161: error: too many basic types
> """
> And compilation fails.
> In a real life project, it fails at exactly the same spot [2]
>
> Diagnostics from the meatbag (hello!):
> - Using gcc and clang instead works fine. This must be tcc's fault, not
> system-headers'.
> - On Ubuntu and Debian, tcc 0.9.26 works fine, too. This must be some
> fault in the compilation, environment, or libraries of tcc, not tcc's code
> itself.
> - The error message stems from line 2510 in tccgen.c [1]. However, I don't
> understand how it got there and where it "counts".
> - This might also be due to a forgotten semicolon [3], which I deem
> inlikely for a system header.
> - Note that tcc is one-pass, so it doesn't even know anything except the
> first line of foo.c. Thus, tcc is currently unusable for me.
>
> Versions, as far as I can tell:
> - 'tcc -dumpversion' says '0.9.26'.
> - `pkg upgrade` says 'Your packages are up to date.'
> - `uname -a` says 'FreeBSD 10.3-RELEASE FreeBSD 10.3-RELEASE #0 r297264:
> Fri Mar 25 02:10:02 UTC 2016'
>
> Regards,
> Ben Wiederhake
>
>
You want to be using the headers provided with tcc?
# tcc -run -I/usr/local/lib/tcc/include test.c
Hello world
--
Waitman Gobble
Los Altos California USA
510-830-7975
___
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 Port: phamm-0.5.18_1
Hi Gustavo and FreeBSD Ports Team, Since I am a FreeBSD beginner, I do not know how to properly flag ports as outdated. Today, I stumbled upon a heavily outdated port of net/phamm (PHP LDAP Virtual Hosting Manager). As per http://www.phamm.org/docs/CHANGELOG, the provided version 0.5.18 is from 20100331, LOL. If possible, please update the port with the current version 0.6.5 (20160106). Thanks a million for your great job with FreeBSD. Zeroflag ___ 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 Port: apache24-2.4.20
Is it possible to update/patch Apache24 with the latest backport? As it stands now, mod_status is completely useless without this patch. http://svn.apache.org/viewvc?view=revision&revision=1739008 Ken ___ 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: 'porting' AMD compiler suite
On 04/13/16 02:51, Mehmet Erol Sanliturk wrote: On Wed, Apr 13, 2016 at 12:02 AM, William A. Mahaffey III wrote: On 04/12/16 21:05, Kevin P. Neal wrote: On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote: A bit of poking around yields a 'typedef __uintptr_t uintptr_t;' statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t isn't defined anywhere Any clues ? TIA & have a good one. *C'mon* Someone throw me a bone :-). Whassup here, this can't be the 1st time this has happened where is __uintptr_t defined/typedef'ed ? % find /usr/include/ -type f -print | xargs grep __uintptr_t You'll need to follow the includes backwards until you get to an include that looks like it is meant to be directly included. That particular command is left as an exercise to the reader. *Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks again. -- William A. Mahaffey III -- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. ___ There are differences between FreeBSD and Linux include directory places . Assume , it it is possible to build Open64 in Linux , but it is failing in FreeBSD due to unfound files : There is a need to specify include directories ( -I ) in make files correctly for the FreeBSD being equivalent to Linux include directories . For example , some files are specified in Linux as #include , but in FreeBSD as #include . Mehmet Erol Sanliturk . ___ 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" All seems OK w/ the system headers (I know, shocking ), the required files defining a '__uintptr_t' are in fact unconditionally included, so it must be something else (bad defines somewhere, or ). I am still chasing -- William A. Mahaffey III -- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. ___ 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: FreeBSD Port: tcc-0.9.26_3
On 04/13/16 19:27, Ben Wiederhake wrote:
Hello,
"#include " seems to be impossible with tcc on FreeBSD.
Steps to reproduce:
Try to compile the following program:
"""
#include
#include
int main(void){printf("Hello world\n");}
"""
Excepted results:
Compilation finishes with no errors.
Actual results:
"""
In file included from foo.c:1:
In file included from /usr/include/stdint.h:33:
In file included from /usr/include/sys/_types.h:33:
In file included from /usr/include/machine/_types.h:6:
/usr/include/x86/_types.h:161: error: too many basic types
"""
And compilation fails.
In a real life project, it fails at exactly the same spot [2]
Diagnostics from the meatbag (hello!):
- Using gcc and clang instead works fine. This must be tcc's fault,
not system-headers'.
- On Ubuntu and Debian, tcc 0.9.26 works fine, too. This must be some
fault in the compilation, environment, or libraries of tcc, not tcc's
code itself.
- The error message stems from line 2510 in tccgen.c [1]. However, I
don't understand how it got there and where it "counts".
- This might also be due to a forgotten semicolon [3], which I deem
inlikely for a system header.
- Note that tcc is one-pass, so it doesn't even know anything except
the first line of foo.c. Thus, tcc is currently unusable for me.
Versions, as far as I can tell:
- 'tcc -dumpversion' says '0.9.26'.
- `pkg upgrade` says 'Your packages are up to date.'
- `uname -a` says 'FreeBSD 10.3-RELEASE FreeBSD 10.3-RELEASE #0
r297264: Fri Mar 25 02:10:02 UTC 2016'
Regards,
Ben Wiederhake
[1]
https://github.com/search?utf8=%E2%9C%93&q=%22too+many+basic+types%22&type=Code&ref=searchresults
[2] https://gitlab.com/BenWiederhake/endian-ci/builds/1077867
[3] https://lists.gnu.org/archive/html/tinycc-devel/2008-09/msg00033.html
___
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"
Interesting. I am seeing (almost) the same error in another thread
('porting' open64 compiler), same issue, some problem w/ getting some
basic system types defined, same type of error, same system header
files. I am on 9.3R, not 10.3, but interesting coincidence
--
William A. Mahaffey III
--
"The M1 Garand is without doubt the finest implement of war
ever devised by man."
-- Gen. George S. Patton Jr.
___
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 Port: tcc-0.9.26_3
Hello,
"#include " seems to be impossible with tcc on FreeBSD.
Steps to reproduce:
Try to compile the following program:
"""
#include
#include
int main(void){printf("Hello world\n");}
"""
Excepted results:
Compilation finishes with no errors.
Actual results:
"""
In file included from foo.c:1:
In file included from /usr/include/stdint.h:33:
In file included from /usr/include/sys/_types.h:33:
In file included from /usr/include/machine/_types.h:6:
/usr/include/x86/_types.h:161: error: too many basic types
"""
And compilation fails.
In a real life project, it fails at exactly the same spot [2]
Diagnostics from the meatbag (hello!):
- Using gcc and clang instead works fine. This must be tcc's fault, not
system-headers'.
- On Ubuntu and Debian, tcc 0.9.26 works fine, too. This must be some
fault in the compilation, environment, or libraries of tcc, not tcc's
code itself.
- The error message stems from line 2510 in tccgen.c [1]. However, I
don't understand how it got there and where it "counts".
- This might also be due to a forgotten semicolon [3], which I deem
inlikely for a system header.
- Note that tcc is one-pass, so it doesn't even know anything except the
first line of foo.c. Thus, tcc is currently unusable for me.
Versions, as far as I can tell:
- 'tcc -dumpversion' says '0.9.26'.
- `pkg upgrade` says 'Your packages are up to date.'
- `uname -a` says 'FreeBSD 10.3-RELEASE FreeBSD 10.3-RELEASE #0
r297264: Fri Mar 25 02:10:02 UTC 2016'
Regards,
Ben Wiederhake
[1]
https://github.com/search?utf8=%E2%9C%93&q=%22too+many+basic+types%22&type=Code&ref=searchresults
[2] https://gitlab.com/BenWiederhake/endian-ci/builds/1077867
[3] https://lists.gnu.org/archive/html/tinycc-devel/2008-09/msg00033.html
___
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"
linux-c6 ports maintainership
Hey guys, I'm looking for someone to give tender loving care to the CentOS ports we're using on FreeBSD to run Skype and many more. I've started this project in early 2014 and I've been enjoying the ride through 6.4, 6.5, 6.6 and now 6.7, alas it's time for new priorities. CentOS follows the RHEL release schedule more or less closely. When that happens, everything that CentOS updates needs to be updated in ports as well, including small pkg-plist and distinfo changes. Developing the PR for the last upgrade -- 6.6 through 6.7 -- took me four hours, so it's actually much less work than it sounds. CentOS also occasionally releases security fixes for things that have had outstanding vulnerabilities (think openssl, glibc, and friends). This entails every now and then updating one port. Given that CentOS 6 will be maintained upstream until 30 November 2020 we still have some time to go before everything becomes as old and rusty as it was before. This takes someone to do it, and much as I'd like there's other things on my plate. If you'd be interested in doing this and have some more specific questions, drop me a line or two and we'll sort it out Thanks, -- -xmj http://xmj.me signature.asc Description: OpenPGP digital signature
➽ Забрал? ➽ 7 Готовых Воронок Продаж
11 http://link.2butusa.ru/campaigns/jg992kt9d2bc3/track-url/jn967zqe1z0b6/808497c905143c83d62500712c0aeab9c4db7f96 , ! , . ocooc ? , ? , http://link.2butusa.ru/campaigns/jg992kt9d2bc3/track-url/jn967zqe1z0b6/7f21df4a59677e1c658a9f345bbd5e3975779e55 , , - , ,? , , , ! , , pe epe ece? ?? ,: , http://link.2butusa.ru/campaigns/jg992kt9d2bc3/track-url/jn967zqe1z0b6/7f21df4a59677e1c658a9f345bbd5e3975779e55 P.S. Если Вы хотите более подробной информации, то смотрите -> ЗДЕСЬ HTTP://MAIL.BESTRASS.RU/CAMPAIGNS/JG992KT9D2BC3/TRACK-URL/JN967ZQE1Z0B6/A2D1BAFAC58CD9C60FDC0AC5776A2479E839238D Всего Вам доброго и успехов. E-mail, http://link.2butusa.ru/campaigns/jg992kt9d2bc3/track-url/jn967zqe1z0b6/946d3616b15aaede37414fed5150b93be19bf2ba@2016 -- , , . -- - ___ http://link.2butusa.ru/campaigns/jg992kt9d2bc3/track-url/jn967zqe1z0b6/808497c905143c83d62500712c0aeab9c4db7f96_ _ http://link.2butusa.ru/campaigns/jg992kt9d2bc3/track-url/jn967zqe1z0b6/33caa10cbc9feee913055910995766d0dee8a019_ ___ 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: libwraster (and therefore windowmaker) refuse to build
On Mon, Apr 11, 2016 at 02:18:38PM +0100, tech-lists wrote: Hello list, portupgrade is having a problem updating libwraster and therefore windowmaker. I'm on -current r297389, ports is 413029. here's the failing output: [...] I've fixed this with a portupgrade libwraster -fr and then portupgrade libwraster -fR, sorry for the noise. -- J. ___ 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: 'porting' AMD compiler suite
On Wed, Apr 13, 2016 at 12:02 AM, William A. Mahaffey III wrote: > On 04/12/16 21:05, Kevin P. Neal wrote: > >> On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote: >> >>> A bit of poking around yields a 'typedef __uintptr_t uintptr_t;' statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t isn't defined anywhere Any clues ? TIA & have a good one. >>> *C'mon* Someone throw me a bone :-). Whassup here, this can't be >>> the 1st time this has happened where is __uintptr_t >>> defined/typedef'ed ? >>> >> % find /usr/include/ -type f -print | xargs grep __uintptr_t >> >> You'll need to follow the includes backwards until you get to an include >> that looks like it is meant to be directly included. That particular >> command >> is left as an exercise to the reader. >> > > > *Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks > again. > > -- > > William A. Mahaffey III > > -- > > "The M1 Garand is without doubt the finest implement of war > ever devised by man." >-- Gen. George S. Patton Jr. > > ___ > > The following page perhaps may contain some useful information : http://grokbase.com/t/sc/osunix-dev/0932bgy1rs/opensolaris-open64-port-1st-round-patch-review Mehmet Erol Sanliturk ___ 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"
SugarCRM
Hi, I know SugarCRM is in the ports. And I installed a FAMP stack in a VM. Does anyone know how to set up the CRM and configure it? Thanks, Jonathan Moore ___ 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"
СКЛАДЫ И ОФИСЫ В АРЕНДУ
СКЛАДЫ И ОФИСЫ В АРЕНДУ СКЛАД 500 кв.м. – 225 т.р. в месяц (1 этаж, потолки 5 м., круглосуточный доступ, пандус для фур) СКЛАД 90 кв.м. – 41 т.р. в месяц (1 этаж, потолки 5 м., окна, отопление) ОФИС 42 кв.м. – 32 т.р. в месяц ( 3 кабинета, свой санузел, 2 этаж, отдельный вход) СПЕЦПРЕДЛОЖЕНИЕ ДЛЯ ИНТЕРНЕТ-МАГАЗИНОВ !!! ОФИС 22 кв.м. – 20 т.р. в месяц (1 этаж, отдельный вход, круглосуточный доступ) ОТВЕТСТВЕННОЕ ХРАНЕНИЕ (от 15 руб. кв.м./сутки) ПОГРУЗО-РАЗГРУЗОЧНЫЕ РАБОТЫ СКЛАДСКИЕ УСЛУГИ ( комплектация, маркировка, упаковка, перегруз на пандусе) Круглосуточная охрана территории, бесплатный въезд, пропускной режим, удобный пандус, видеонаблюдение. (495) 726-17-77, (495) 798-55-05 ЮАО, м. Кантемировская Извините, если письмо доставлено не по адресу. ___ 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 you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ devel/py-event | 0_3 | 0.4 +-+ www/nostromo| 1.9.5 | 1.9.6 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt Thanks. ___ 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: 'porting' AMD compiler suite
On Wed, Apr 13, 2016 at 12:02 AM, William A. Mahaffey III wrote: > On 04/12/16 21:05, Kevin P. Neal wrote: > >> On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote: >> >>> A bit of poking around yields a 'typedef __uintptr_t uintptr_t;' statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t isn't defined anywhere Any clues ? TIA & have a good one. >>> *C'mon* Someone throw me a bone :-). Whassup here, this can't be >>> the 1st time this has happened where is __uintptr_t >>> defined/typedef'ed ? >>> >> % find /usr/include/ -type f -print | xargs grep __uintptr_t >> >> You'll need to follow the includes backwards until you get to an include >> that looks like it is meant to be directly included. That particular >> command >> is left as an exercise to the reader. >> > > > *Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks > again. > > -- > > William A. Mahaffey III > > -- > > "The M1 Garand is without doubt the finest implement of war > ever devised by man." >-- Gen. George S. Patton Jr. > > ___ > > There are differences between FreeBSD and Linux include directory places . Assume , it it is possible to build Open64 in Linux , but it is failing in FreeBSD due to unfound files : There is a need to specify include directories ( -I ) in make files correctly for the FreeBSD being equivalent to Linux include directories . For example , some files are specified in Linux as #include , but in FreeBSD as #include . Mehmet Erol Sanliturk . ___ 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: 'porting' AMD compiler suite
On Wed, Apr 13, 2016 at 12:02 AM, William A. Mahaffey III wrote: > On 04/12/16 21:05, Kevin P. Neal wrote: > >> On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote: >> >>> A bit of poking around yields a 'typedef __uintptr_t uintptr_t;' statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t isn't defined anywhere Any clues ? TIA & have a good one. >>> *C'mon* Someone throw me a bone :-). Whassup here, this can't be >>> the 1st time this has happened where is __uintptr_t >>> defined/typedef'ed ? >>> >> % find /usr/include/ -type f -print | xargs grep __uintptr_t >> >> You'll need to follow the includes backwards until you get to an include >> that looks like it is meant to be directly included. That particular >> command >> is left as an exercise to the reader. >> > > > *Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks > again. > > -- > > William A. Mahaffey III > > -- > > "The M1 Garand is without doubt the finest implement of war > ever devised by man." >-- Gen. George S. Patton Jr. > > ___ > 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" > If you search __uintptr_t in Google , you will find many links about its possible places . Mehmet Erol Sanliturk ___ 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: 'porting' AMD compiler suite
On 04/12/16 21:05, Kevin P. Neal wrote: On Tue, Apr 12, 2016 at 03:32:21PM -0453, William A. Mahaffey III wrote: A bit of poking around yields a 'typedef __uintptr_t uintptr_t;' statement as line 78 of /usr/include/sys/_stdint.h, where __uintptr_t isn't defined anywhere Any clues ? TIA & have a good one. *C'mon* Someone throw me a bone :-). Whassup here, this can't be the 1st time this has happened where is __uintptr_t defined/typedef'ed ? % find /usr/include/ -type f -print | xargs grep __uintptr_t You'll need to follow the includes backwards until you get to an include that looks like it is meant to be directly included. That particular command is left as an exercise to the reader. *Boooyah*, thanks. It looks like some GNU-ism, still chasing ;-). Thanks again. -- William A. Mahaffey III -- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr. ___ 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"
