ports-mgmt/bpm deleted port distfile
I use bpm to browse the collection from the ports INDEX file. It's useful because I find the type if info I'm searching for much more quickly when compared to other means. I have to re-build the port after upgrading to 12-Current but I've lost the distfile I was keeping on my disk. Normally I would expect/assume the file to be found somewhere under http://distcache.FreeBSD.org/ports-distfiles/ but that page is unreachable (the primary source page is down also). Is there a policy for distfiles of deleted ports that makes the above problem a "normal thing"? -- FreeBSD_amd64_12-Current_RadeonKMS Please CC my email when responding, mail from list is not delivered. ___ 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: pkg and packages
On 7/5/17 5:14 am, Kevin Oberman wrote: On Fri, May 5, 2017 at 3:11 PM, Sebastian Schwarz wrote: On 2017-05-04, scratch65...@att.net wrote: I can't imagine what code could possibly be in thunar and samba that the xfce desktop would need, (...) Thunar is used to display the icons on the XFCE desktop. It depends on gvfs, which is used for accessing remote file systems and the trash inside Thunar. gvfs in turn depends on samba44 in order to access CIFS/SMB shares. Strictly speaking some of these features might be optional. But as far I know pkg currently doesn't have a concept of optional dependencies. So it's an all or nothing decision, when building the packages. This is the case. If you want to stick with packages, at least until some new packaging features are available, your best bet is to install ports-mgmt/synth. Then you can use it to add a private repository of all ports that you want built with non-standard options. Then have synth create a custom Thunar package that you can then use to avoid samba (44 or 46) or, if supported, build Thunar against the samba version of your choosing. synth(8) has excellent documentation on how to configure and use it. I recommend it for the type of issue you are running into. (N.B. synth is written in ADA and, for that reason, I don't recommend building synth from source as that requires a major installation of the ADA compiler. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ 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" you can do the same with poudriere, by telling it to keep a set of pre-canned configureations. see: PORT_DBDIRDirectory where the results of configuring OPTIONS are stored. Defaults to /var/db/ports. Each port where OPTIONS have been configured will have a uniquely named sub-directory, containing a single file options. ___ 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: pkg and packages
[Default] On Sat, 06 May 2017 00:11:00 +0200, Sebastian Schwarz wrote: >On 2017-05-04, scratch65...@att.net wrote: >> I can't imagine what code could possibly be in thunar and >> samba that the xfce desktop would need, (...) > >Thunar is used to display the icons on the XFCE desktop. It >depends on gvfs, which is used for accessing remote file systems >and the trash inside Thunar. gvfs in turn depends on samba44 in >order to access CIFS/SMB shares. > >Strictly speaking some of these features might be optional. But >as far I know pkg currently doesn't have a concept of optional >dependencies. So it's an all or nothing decision, when building >the packages. It's really not even "strictly speaking". They always should be separate installs, not ever bundled together. What use can someone have for samba who doesn't have any windows boxes? And since samba is the guy who does all the work to make the freebsd filesystems look non-threatening to windows, why, really, is gvfs needed at all? As far as I'm aware, there's no way, short of finding and installing a copy of that old, unsupported windows nfs client, for freebsd to access a windows box.. And thunar doesn't seem to require the desktop (when are icons placed on the desktop? I can't recall ever seeing that), since after my desktop was discarded during the general upgrade, the panels, icons, and thunar all continued to function as before, which since xfce is a modular, loosely-coupled system, was not unexpected. ___ 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: pkg and packages
[Default] On Thu, 4 May 2017 14:18:46 +0100, RW via freebsd-ports wrote: >AFAIK samba isn't a dependency of XFCE. I don't have it and it's not in >the output of make all-depends-list. Thanks, you beat me to it. I thought such a dependency would be pretty unreasonable. > >Thunar is scarcely "unrelated", it's the XFCE integrated file manager. >XFCE uses the libthunarx library if built with the Thunar option. Sorry, I meant unrelated to the desktop. Thunar kept going normally even after my desktop was discarded by pkg during the general ports upgrade. ___ 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/lua-posix | 33.4.0 | v34.0 +-+ 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"
need help with upgrade of virtualbox-ose
from 5.0.26 to 5.1.latest. every attempt ends with virtual machine crash just when it should switch from windows loading screen to normal screen. all VMs are windows 7 pro. Logs doesn't give any hint. Any help? ___ 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: need help with upgrade of virtualbox-ose
> On May 7, 2017, at 9:38 AM, Wojciech Puchar wrote: > > from 5.0.26 to 5.1.latest. > > every attempt ends with virtual machine crash just when it should switch from > windows loading screen to normal screen. all VMs are windows 7 pro. > > Logs doesn't give any hint. I had a similar problem running FreeBSD current on OSX machine. I had to downgrade the xorg-server from 1.18.4,1 to 1.17.4,1 the rebuild virtualbox-ose-additions and kernel. It worked again. Not sure if this is the same problem for yo ___ 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: need help with upgrade of virtualbox-ose
> On May 7, 2017, at 9:38 AM, Wojciech Puchar wrote: > > from 5.0.26 to 5.1.latest. > > every attempt ends with virtual machine crash just when it should switch from > windows loading screen to normal screen. all VMs are windows 7 pro. > > Logs doesn't give any hint. I had a similar problem running FreeBSD current on OSX machine. I had to downgrade the xorg-server from 1.18.4,1 to 1.17.4,1 the rebuild virtualbox-ose-additions and kernel. It worked again. Not sure if this is the same problem for you. Manfred -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. ___ 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: need help with upgrade of virtualbox-ose
finally "succeeded" - i was able to upgrade to latest 10-stable while keeping vbox 5.0.26. portdowngrade helped and one patch in kernel. thanks. Still i would like to go to 5.1 I had a similar problem running FreeBSD current on OSX machine. I had to downgrade the xorg-server from 1.18.4,1 to 1.17.4,1 the rebuild virtualbox-ose-additions and kernel. it's certainly not X dependent as i don't run X on this server. headless or from VNC "x server" - both cases same result. ___ 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: Lack of TARGET_ARCH=powerpc support in kgdb from devel/gdb (e.g., -r440115 of /usr/ports): "ABI doesn't support a vmcore target"
[This update just notes that it appears that combination
${MK_GDB} == no && ${MK_GDB_LIBEXEC} == yes is not intended
to be used, effectively eliminating "THING #1" of 0-2.]
On 2017-May-6, at 10:03 PM, Mark Millard wrote:
> On 2017-May-6, at 5:21 PM, Mark Millard wrote:
>
>> On:
>>
>> # uname -apKU
>> FreeBSD FBSDG4S 12.0-CURRENT FreeBSD 12.0-CURRENT r317820M powerpc powerpc
>> 1200030 1200030
>>
>> When I attempt to use:
>>
>> # which kgdb
>> /usr/local/bin/kgdb
>>
>> that was from building devel/gdb for:
>>
>> # svnlite info /usr/ports | grep "Re[plv]"
>> Relative URL: ^/head
>> Repository Root: https://svn.freebsd.org/ports
>> Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
>> Revision: 440115
>> Last Changed Rev: 440115
>>
>> (built via gcc 4.2.1: not via clang: I
>> experiment with clang for powerpc and
>> powerpc64 so I'm being explicit)
>>
>> I end up getting the following sort of result:
>>
>> # kgdb /usr/lib/debug/boot/kernel/kernel.debug /var/crash/vmcore.4
>> . . .
>> Reading symbols from /usr/lib/debug/boot/kernel/kernel.debug...done.
>> ABI doesn't support a vmcore target
>>
>> That message is from: /usr/ports/devel/gdb/files/kgdb/fbsd-kvm.c . . .
>>
>> static void
>> kgdb_trgt_open(const char *arg, int from_tty)
>> {
>> struct fbsd_vmcore_ops *ops = (struct fbsd_vmcore_ops *)
>> gdbarch_data (target_gdbarch(), fbsd_vmcore_data);
>> . . .
>> if (ops == NULL || ops->supply_pcb == NULL || ops->cpu_pcb_addr ==
>> NULL)
>> error ("ABI doesn't support a vmcore target");
>> . . .
>>
>> It appears that there is no kernel debugging
>> supported for TARGET_ARCH=powerpc currently.
>> (The system no longer has its own gdb related
>> materials.)
>
> I've discovered more context and have found
> a few of issues in how things are currently
> set up.
>
> THING #0:
>
> It appears that usr.sbin/crashinfo/crashinfo.sh assumes
> that /usr/local/bin/gdb will work better for all architectures,
> including for kgdb types of activity:
>
> find_gdb()
> {
>local binary
>
>for binary in /usr/local/bin/gdb /usr/libexec/gdb /usr/bin/gdb; do
>if [ -x ${binary} ]; then
>GDB=${binary}
>return
>fi
>done
> }
>
> But it appears that on powerpc /usr/local/bin/gdb and
> /usr/local/bin/kgdb do not support TARGET_ARCH=powerpc
> at all for such activity.
>
>
> THING #1:
>
> Another oddity is for the combination:
>
> ${MK_GDB} == no && ${MK_GDB_LIBEXEC} == yes
>
> where the tools/build/mk/OptionalObsoleteFiles.inc
> logic then adds the libexec gdb and kgdb to
> OLD_FILES :
>
> .if ${MK_GDB} == no || ${MK_GDB_LIBEXEC} == no
> OLD_FILES+=usr/libexec/gdb
> OLD_FILES+=usr/libexec/kgdb
> .endif
>
> so doing a delete-old removes the only system
> gdb and kgdb that are installed for such a
> context. It does this because of:
>
> ${MK_GDB} == no
>
> (And that explains why I thought gdb and kgdb
> were not in the system.)
Looking around at how WITH_GDB and WITH_GDB_LIBEXEC
and the MK_ variants are used it appears that the:
${MK_GDB} == no && ${MK_GDB_LIBEXEC} == yes
combination is not intended to be used.
> THING #2:
>
> /usr/libexec/kgdb (when present) does not support the
> powerpc architecture for head either . . .
>
> On a head -r317820 powerpc I attempted:
>
> # /usr/libexec/kgdb /usr/lib/debug/boot/kernel/kernel.debug
> /var/crash/vmcore.7
> GNU gdb 6.1.1 [FreeBSD]
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "powerpc-marcel-freebsd"...
> Failed to open vmcore: unsupported architecture
===
Mark Millard
markmi at dsl-only.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: need help with upgrade of virtualbox-ose
> On May 7, 2017, at 12:06 PM, Wojciech Puchar wrote: > > finally "succeeded" - i was able to upgrade to latest 10-stable while keeping > vbox 5.0.26. > > portdowngrade helped and one patch in kernel. thanks. > > Still i would like to go to 5.1 > I’m using 5.1.22 on current, I just had to portdowngrade xorg-server and rebuild kernel and virtualbox-ose-additions and its working now. I’m running a FreeBSD virtual machine on a Mac Pro 2012 Manfred ___ 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"
nginx is not linking against libressl
Hello, I tried to upgrade my jail to the latest versions of ports and nginx is not building correctly. objs/src/event/ngx_event_openssl.o: In function `ngx_ssl_get_ciphers': src/event/ngx_event_openssl.c:(.text+0x3de6): undefined reference to `SSL_CIPHER_find' src/event/ngx_event_openssl.c:(.text+0x3e66): undefined reference to `SSL_CIPHER_find' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 make.conf OPTIONS_UNSET+= DOCS EXAMPLES X11 IPV6 DEFAULT_VERSIONS+=ssl=libressl WRKDIRPREFIX= /var/ports DISTDIR= /var/ports/distfiles PACKAGES= /var/ports/packages INDEXDIR= /usr/ports options OPTIONS_FILE_UNSET+=DSO OPTIONS_FILE_UNSET+=DEBUG OPTIONS_FILE_UNSET+=DEBUGLOG OPTIONS_FILE_SET+=FILE_AIO OPTIONS_FILE_UNSET+=IPV6 OPTIONS_FILE_UNSET+=GOOGLE_PERFTOOLS OPTIONS_FILE_SET+=HTTP OPTIONS_FILE_UNSET+=HTTP_ADDITION OPTIONS_FILE_UNSET+=HTTP_AUTH_REQ OPTIONS_FILE_UNSET+=HTTP_CACHE OPTIONS_FILE_UNSET+=HTTP_DAV OPTIONS_FILE_UNSET+=HTTP_FLV OPTIONS_FILE_UNSET+=HTTP_GEOIP OPTIONS_FILE_UNSET+=HTTP_GZIP_STATIC OPTIONS_FILE_UNSET+=HTTP_GUNZIP_FILTER OPTIONS_FILE_UNSET+=HTTP_IMAGE_FILTER OPTIONS_FILE_UNSET+=HTTP_MP4 OPTIONS_FILE_UNSET+=HTTP_PERL OPTIONS_FILE_UNSET+=HTTP_RANDOM_INDEX OPTIONS_FILE_UNSET+=HTTP_REALIP OPTIONS_FILE_UNSET+=HTTP_REWRITE OPTIONS_FILE_UNSET+=HTTP_SECURE_LINK OPTIONS_FILE_UNSET+=HTTP_SLICE OPTIONS_FILE_SET+=HTTP_SSL OPTIONS_FILE_UNSET+=HTTP_STATUS OPTIONS_FILE_UNSET+=HTTP_SUB OPTIONS_FILE_UNSET+=HTTP_XSLT OPTIONS_FILE_UNSET+=MAIL OPTIONS_FILE_UNSET+=MAIL_IMAP OPTIONS_FILE_UNSET+=MAIL_POP3 OPTIONS_FILE_UNSET+=MAIL_SMTP OPTIONS_FILE_UNSET+=MAIL_SSL OPTIONS_FILE_SET+=HTTPV2 OPTIONS_FILE_UNSET+=NJS OPTIONS_FILE_UNSET+=STREAM OPTIONS_FILE_UNSET+=STREAM_SSL OPTIONS_FILE_UNSET+=STREAM_SSL_PREREAD OPTIONS_FILE_UNSET+=THREADS OPTIONS_FILE_UNSET+=WWW OPTIONS_FILE_UNSET+=AJP OPTIONS_FILE_UNSET+=AWS_AUTH OPTIONS_FILE_UNSET+=CACHE_PURGE OPTIONS_FILE_UNSET+=CLOJURE OPTIONS_FILE_UNSET+=CT OPTIONS_FILE_UNSET+=ECHO OPTIONS_FILE_UNSET+=FASTDFS OPTIONS_FILE_UNSET+=HEADERS_MORE OPTIONS_FILE_UNSET+=HTTP_ACCEPT_LANGUAGE OPTIONS_FILE_UNSET+=HTTP_AUTH_DIGEST OPTIONS_FILE_UNSET+=HTTP_AUTH_KRB5 OPTIONS_FILE_UNSET+=HTTP_AUTH_LDAP OPTIONS_FILE_UNSET+=HTTP_AUTH_PAM OPTIONS_FILE_UNSET+=HTTP_DAV_EXT OPTIONS_FILE_UNSET+=HTTP_EVAL OPTIONS_FILE_UNSET+=HTTP_FANCYINDEX OPTIONS_FILE_UNSET+=HTTP_FOOTER OPTIONS_FILE_UNSET+=HTTP_GEOIP2 OPTIONS_FILE_UNSET+=HTTP_JSON_STATUS OPTIONS_FILE_UNSET+=HTTP_MOGILEFS OPTIONS_FILE_UNSET+=HTTP_MP4_H264 OPTIONS_FILE_UNSET+=HTTP_NOTICE OPTIONS_FILE_UNSET+=HTTP_PUSH OPTIONS_FILE_UNSET+=HTTP_PUSH_STREAM OPTIONS_FILE_UNSET+=HTTP_REDIS OPTIONS_FILE_UNSET+=HTTP_RESPONSE OPTIONS_FILE_UNSET+=HTTP_SUBS_FILTER OPTIONS_FILE_UNSET+=HTTP_TARANTOOL OPTIONS_FILE_UNSET+=HTTP_UPLOAD OPTIONS_FILE_UNSET+=HTTP_UPLOAD_PROGRESS OPTIONS_FILE_UNSET+=HTTP_UPSTREAM_CHECK OPTIONS_FILE_UNSET+=HTTP_UPSTREAM_FAIR OPTIONS_FILE_UNSET+=HTTP_UPSTREAM_STICKY OPTIONS_FILE_UNSET+=HTTP_VIDEO_THUMBEXTRACTOR OPTIONS_FILE_UNSET+=HTTP_ZIP OPTIONS_FILE_UNSET+=ARRAYVAR OPTIONS_FILE_UNSET+=BROTLI OPTIONS_FILE_UNSET+=DRIZZLE OPTIONS_FILE_UNSET+=DYNAMIC_UPSTREAM OPTIONS_FILE_UNSET+=ENCRYPTSESSION OPTIONS_FILE_UNSET+=FORMINPUT OPTIONS_FILE_UNSET+=GRIDFS OPTIONS_FILE_UNSET+=ICONV OPTIONS_FILE_UNSET+=LET OPTIONS_FILE_UNSET+=LUA OPTIONS_FILE_UNSET+=MEMC OPTIONS_FILE_UNSET+=MODSECURITY OPTIONS_FILE_UNSET+=NAXSI OPTIONS_FILE_UNSET+=PASSENGER OPTIONS_FILE_UNSET+=POSTGRES OPTIONS_FILE_UNSET+=RDS_CSV OPTIONS_FILE_UNSET+=RDS_JSON OPTIONS_FILE_UNSET+=REDIS2 OPTIONS_FILE_UNSET+=RTMP OPTIONS_FILE_UNSET+=SET_MISC OPTIONS_FILE_UNSET+=SFLOW OPTIONS_FILE_UNSET+=SHIBBOLETH OPTIONS_FILE_UNSET+=SLOWFS_CACHE OPTIONS_FILE_UNSET+=SMALL_LIGHT OPTIONS_FILE_UNSET+=SRCACHE OPTIONS_FILE_UNSET+=X11 OPTIONS_FILE_UNSET+=XSS Anyone has the same problem? ___ 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: nginx is not linking against libressl
> On 7 May, 2017, at 13:55, abi wrote: > > Hello, > > I tried to upgrade my jail to the latest versions of ports and nginx is not > building correctly. > > objs/src/event/ngx_event_openssl.o: In function `ngx_ssl_get_ciphers': > src/event/ngx_event_openssl.c:(.text+0x3de6): undefined reference to > `SSL_CIPHER_find' > src/event/ngx_event_openssl.c:(.text+0x3e66): undefined reference to > `SSL_CIPHER_find' > cc: error: linker command failed with exit code 1 (use -v to see invocation) > *** Error code 1 I have no idea why this is the case, but it will build successfully if you re-enable the IPV6 option. Also, turning off the DSO and THREADS options seems unusual; under normal circumstance you want both those things enabled. # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.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: nginx is not linking against libressl
Hello, On 05/07/2017 03:55 PM, abi wrote: Hello, I tried to upgrade my jail to the latest versions of ports and nginx is not building correctly. objs/src/event/ngx_event_openssl.o: In function `ngx_ssl_get_ciphers': src/event/ngx_event_openssl.c:(.text+0x3de6): undefined reference to `SSL_CIPHER_find' src/event/ngx_event_openssl.c:(.text+0x3e66): undefined reference to `SSL_CIPHER_find' cc: error: linker command failed with exit code 1 (use -v to see invocation) *** Error code 1 It looks like it should build. I don't have much to add, but I'm going to cc the maintainer. make.conf OPTIONS_UNSET+= DOCS EXAMPLES X11 IPV6 DEFAULT_VERSIONS+=ssl=libressl WRKDIRPREFIX= /var/ports DISTDIR= /var/ports/distfiles PACKAGES= /var/ports/packages INDEXDIR= /usr/ports options OPTIONS_FILE_UNSET+=DSO OPTIONS_FILE_UNSET+=DEBUG OPTIONS_FILE_UNSET+=DEBUGLOG OPTIONS_FILE_SET+=FILE_AIO OPTIONS_FILE_UNSET+=IPV6 OPTIONS_FILE_UNSET+=GOOGLE_PERFTOOLS OPTIONS_FILE_SET+=HTTP OPTIONS_FILE_UNSET+=HTTP_ADDITION OPTIONS_FILE_UNSET+=HTTP_AUTH_REQ OPTIONS_FILE_UNSET+=HTTP_CACHE OPTIONS_FILE_UNSET+=HTTP_DAV OPTIONS_FILE_UNSET+=HTTP_FLV OPTIONS_FILE_UNSET+=HTTP_GEOIP OPTIONS_FILE_UNSET+=HTTP_GZIP_STATIC OPTIONS_FILE_UNSET+=HTTP_GUNZIP_FILTER OPTIONS_FILE_UNSET+=HTTP_IMAGE_FILTER OPTIONS_FILE_UNSET+=HTTP_MP4 OPTIONS_FILE_UNSET+=HTTP_PERL OPTIONS_FILE_UNSET+=HTTP_RANDOM_INDEX OPTIONS_FILE_UNSET+=HTTP_REALIP OPTIONS_FILE_UNSET+=HTTP_REWRITE OPTIONS_FILE_UNSET+=HTTP_SECURE_LINK OPTIONS_FILE_UNSET+=HTTP_SLICE OPTIONS_FILE_SET+=HTTP_SSL OPTIONS_FILE_UNSET+=HTTP_STATUS OPTIONS_FILE_UNSET+=HTTP_SUB OPTIONS_FILE_UNSET+=HTTP_XSLT OPTIONS_FILE_UNSET+=MAIL OPTIONS_FILE_UNSET+=MAIL_IMAP OPTIONS_FILE_UNSET+=MAIL_POP3 OPTIONS_FILE_UNSET+=MAIL_SMTP OPTIONS_FILE_UNSET+=MAIL_SSL OPTIONS_FILE_SET+=HTTPV2 OPTIONS_FILE_UNSET+=NJS OPTIONS_FILE_UNSET+=STREAM OPTIONS_FILE_UNSET+=STREAM_SSL OPTIONS_FILE_UNSET+=STREAM_SSL_PREREAD OPTIONS_FILE_UNSET+=THREADS OPTIONS_FILE_UNSET+=WWW OPTIONS_FILE_UNSET+=AJP OPTIONS_FILE_UNSET+=AWS_AUTH OPTIONS_FILE_UNSET+=CACHE_PURGE OPTIONS_FILE_UNSET+=CLOJURE OPTIONS_FILE_UNSET+=CT OPTIONS_FILE_UNSET+=ECHO OPTIONS_FILE_UNSET+=FASTDFS OPTIONS_FILE_UNSET+=HEADERS_MORE OPTIONS_FILE_UNSET+=HTTP_ACCEPT_LANGUAGE OPTIONS_FILE_UNSET+=HTTP_AUTH_DIGEST OPTIONS_FILE_UNSET+=HTTP_AUTH_KRB5 OPTIONS_FILE_UNSET+=HTTP_AUTH_LDAP OPTIONS_FILE_UNSET+=HTTP_AUTH_PAM OPTIONS_FILE_UNSET+=HTTP_DAV_EXT OPTIONS_FILE_UNSET+=HTTP_EVAL OPTIONS_FILE_UNSET+=HTTP_FANCYINDEX OPTIONS_FILE_UNSET+=HTTP_FOOTER OPTIONS_FILE_UNSET+=HTTP_GEOIP2 OPTIONS_FILE_UNSET+=HTTP_JSON_STATUS OPTIONS_FILE_UNSET+=HTTP_MOGILEFS OPTIONS_FILE_UNSET+=HTTP_MP4_H264 OPTIONS_FILE_UNSET+=HTTP_NOTICE OPTIONS_FILE_UNSET+=HTTP_PUSH OPTIONS_FILE_UNSET+=HTTP_PUSH_STREAM OPTIONS_FILE_UNSET+=HTTP_REDIS OPTIONS_FILE_UNSET+=HTTP_RESPONSE OPTIONS_FILE_UNSET+=HTTP_SUBS_FILTER OPTIONS_FILE_UNSET+=HTTP_TARANTOOL OPTIONS_FILE_UNSET+=HTTP_UPLOAD OPTIONS_FILE_UNSET+=HTTP_UPLOAD_PROGRESS OPTIONS_FILE_UNSET+=HTTP_UPSTREAM_CHECK OPTIONS_FILE_UNSET+=HTTP_UPSTREAM_FAIR OPTIONS_FILE_UNSET+=HTTP_UPSTREAM_STICKY OPTIONS_FILE_UNSET+=HTTP_VIDEO_THUMBEXTRACTOR OPTIONS_FILE_UNSET+=HTTP_ZIP OPTIONS_FILE_UNSET+=ARRAYVAR OPTIONS_FILE_UNSET+=BROTLI OPTIONS_FILE_UNSET+=DRIZZLE OPTIONS_FILE_UNSET+=DYNAMIC_UPSTREAM OPTIONS_FILE_UNSET+=ENCRYPTSESSION OPTIONS_FILE_UNSET+=FORMINPUT OPTIONS_FILE_UNSET+=GRIDFS OPTIONS_FILE_UNSET+=ICONV OPTIONS_FILE_UNSET+=LET OPTIONS_FILE_UNSET+=LUA OPTIONS_FILE_UNSET+=MEMC OPTIONS_FILE_UNSET+=MODSECURITY OPTIONS_FILE_UNSET+=NAXSI OPTIONS_FILE_UNSET+=PASSENGER OPTIONS_FILE_UNSET+=POSTGRES OPTIONS_FILE_UNSET+=RDS_CSV OPTIONS_FILE_UNSET+=RDS_JSON OPTIONS_FILE_UNSET+=REDIS2 OPTIONS_FILE_UNSET+=RTMP OPTIONS_FILE_UNSET+=SET_MISC OPTIONS_FILE_UNSET+=SFLOW OPTIONS_FILE_UNSET+=SHIBBOLETH OPTIONS_FILE_UNSET+=SLOWFS_CACHE OPTIONS_FILE_UNSET+=SMALL_LIGHT OPTIONS_FILE_UNSET+=SRCACHE OPTIONS_FILE_UNSET+=X11 OPTIONS_FILE_UNSET+=XSS Anyone has the same problem? -- Jim Ohlstein ___ 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"
www/firefox, Error: garbage following instruction...was: Re: RPI2, www/firefox, error: "NEON support not enabled"
On Fri, May 05, 2017 at 10:01:40PM -0700, bob prohaska wrote: > It appears that using > make CFLAGS='-mcpu=cortex-a7' > is sufficient to get past the NEON not enabled error. > The next problem appears to be /usr/ports/www/firefox/work/firefox-53.0.2/media/openmax_dl/dl/sp/src/armSP_FFT_CToC_FC32_Radix4_ls_unsafe_s.S:335: Error: garbage following instruction -- `vmov Q7.F32,Q0.F32' cc: error: assembler command failed with exit code 1 (use -v to see invocation) gmake[6]: *** [/usr/ports/www/firefox/work/firefox-53.0.2/config/rules.mk:990: armSP_FFT_CToC_FC32_Radix4_ls_unsafe_s.o] Error 1 gmake[5]: *** [/usr/ports/www/firefox/work/firefox-53.0.2/config/recurse.mk:71: media/openmax_dl/dl/target] Error 2 Is this worth a bug report, or is firefox too far over the horizon for freebsd-arm? Thanks for reading, and any guidance. bob prohaska ___ 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"
old laptop and Xorg problem
i installed all ports from scratch on old thinkpad - 32-bit CPU (i386) and savage driver X compiles fine but Xorg -configure results in [ 9227.526] X.Org X Server 1.18.4 Release Date: 2016-07-19 . . . . [ 9227.529] List of video drivers: [ 9227.529]modesetting [ 9227.529]savage [ 9227.529] (II) LoadModule: "modesetting" [ 9227.529] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so [ 9227.529] (EE) Failed to load /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: /usr/local/lib/xorg/modules/drivers/modesetting_drv.so: Undefined symbol "shadowUpdatePacked" [ 9227.529] (II) UnloadModule: "modesetting" [ 9227.529] (II) Unloading modesetting [ 9227.529] (EE) Failed to load module "modesetting" (loader failed, 7) [ 9227.529] (II) LoadModule: "savage" [ 9227.530] (II) Loading /usr/local/lib/xorg/modules/drivers/savage_drv.so [ 9227.530] (EE) Failed to load /usr/local/lib/xorg/modules/drivers/savage_drv.so: /usr/local/lib/xorg/modules/drivers/savage_drv.so: Undefined symbol "vgaHWddc1SetSpeed" [ 9227.530] (II) UnloadModule: "savage" [ 9227.530] (II) Unloading savage [ 9227.530] (EE) Failed to load module "savage" (loader failed, 7) [ 9227.530] No devices to configure. Configuration failed. why there are missing dependencies and how to fix it? ___ 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"
