Jump to content

Support Our Free and Open Source Software


Please support us financially so we may continue to keep our software free and best in class

Donate

devCU

Site Manager
  • Content Count

    1,283
  • Joined

  • Last visited

  • Days Won

    103

Everything posted by devCU

  1. Perl issue after a server upgrade on Bionic (Havent run on my other version test servers yet) when compiling Nginx with OpenSSL option. rm -rf objs/install_perl cc -c -fPIC -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fwrapv -fno-strict-a$ -o objs/src/http/modules/perl/ngx_http_perl_module.o \ src/http/modules/perl/ngx_http_perl_module.c cc -c -fPIC -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -I src/core -I src/e$ -o objs/ngx_http_perl_module_modules.o \ objs/ngx_http_perl_module_modules.c cc -o objs/ngx_http_perl_module.so \ objs/src/http/modules/perl/ngx_http_perl_module.o \ objs/ngx_http_perl_module_modules.o \ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,-E -fstack-protector-strong -L/usr/local/lib -L/usr/local/lib/perl5/5.26.2/x86_64-linux/CORE -lperl -lpthread -lnsl -ldl -lm -lcryp$ -shared /usr/bin/x86_64-linux-gnu-ld: /usr/local/lib/perl5/5.26.2/x86_64-linux/CORE/libperl.a(op.o): relocation R_X86_64_PC32 against symbol `PL_compcv' can not be used when making a shared object;$ /usr/bin/x86_64-linux-gnu-ld: final link failed: Bad value collect2: error: ld returned 1 exit status objs/Makefile:1889: recipe for target 'objs/ngx_http_perl_module.so' failed make[1]: *** [objs/ngx_http_perl_module.so] Error 1 make[1]: Leaving directory '/opt/source/nginx-1.15.2' Makefile:8: recipe for target 'build' failed make: *** [build] Error 2
  2. Perl issue after a server upgrade on Bionic (Havent run on my other version test servers yet) when compiling Nginx with OpenSSL option. rm -rf objs/install_perl cc -c -fPIC -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -fwrapv -fno-strict-a$ -o objs/src/http/modules/perl/ngx_http_perl_module.o \ src/http/modules/perl/ngx_http_perl_module.c cc -c -fPIC -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Werror -g -g -O2 -fstack-protector-strong -Wformat -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -I src/core -I src/e$ -o objs/ngx_http_perl_module_modules.o \ objs/ngx_http_perl_module_modules.c cc -o objs/ngx_http_perl_module.so \ objs/src/http/modules/perl/ngx_http_perl_module.o \ objs/ngx_http_perl_module_modules.o \ -Wl,-Bsymbolic-functions -Wl,-z,relro -Wl,--as-needed -Wl,-E -fstack-protector-strong -L/usr/local/lib -L/usr/local/lib/perl5/5.26.2/x86_64-linux/CORE -lperl -lpthread -lnsl -ldl -lm -lcryp$ -shared /usr/bin/x86_64-linux-gnu-ld: /usr/local/lib/perl5/5.26.2/x86_64-linux/CORE/libperl.a(op.o): relocation R_X86_64_PC32 against symbol `PL_compcv' can not be used when making a shared object;$ /usr/bin/x86_64-linux-gnu-ld: final link failed: Bad value collect2: error: ld returned 1 exit status objs/Makefile:1889: recipe for target 'objs/ngx_http_perl_module.so' failed make[1]: *** [objs/ngx_http_perl_module.so] Error 1 make[1]: Leaving directory '/opt/source/nginx-1.15.2' Makefile:8: recipe for target 'build' failed make: *** [build] Error 2 View full report
  3. Private Club torrents first draft Session markers Re-factor IPS 4.3x compatibility Version update
  4. Private Club torrents first draft Session markers Re-factor IPS 4.3x compatibility Version update View full report
  5. This is actually very cool. IPS made the club app very flexible and I am currently coding in the ability for clubs to have their own private torrents. For example a Dev club can have development software available only to club members. The same with any other club, a very nice feature that is just one aspect that will make this tracker above the rest. Lots of other goodies I am working on but will keep those under wraps until I can figure out if they can work or not
  6. Even though our registration is open to all I have elected to do a double validation rule, email validation and administration validation due to many low life spammers. I check several times a day and am here most of the time so if you do register and validate your email I will have to validate your account as well after running your IP/Email for known abuses. So it may be quick or up to 24 hours in rare cases. As for a person complaining that if this is an open source site than why registration, DUH, fools like that just don't understand what we are up against as far as malicious users and spammers. So its free and open to join but you must be a member to access the entire site and forums. Very simple and logical. Registration Benefits Post new topics and reply to current ones Full access to downloads and betas Access to issue tracker and support areas Updates via email on projects
  7. Was considering this for awhile and now it makes sense. The application is built for privacy and security and programming a public tracker aspect goes 100% against that as well as extends the development time. So I will be removing any access via public tracker for this application. If you want to run a public tracker then better get a good lawyer and a new brain. Case closed. Anyone who wishes to create an plugin/add-on for public tracker be my guest.
  8. New namespace View full report
  9. New namespace View full report
  10. New for rebuilding watermarks View full report
  11. Re-factor IPS 4.3x compatibility Version update
  12. Re-factor IPS 4.3x compatibility Version update View full report
  13. Version update View full report
  14. Version update View full report
  15. Version update View full report
  16. Deprecated >> MemberRestrictions will take over its duties in next release
  17. Deprecated >> MemberRestrictions will take over its duties in next release View full report
×
×
  • Create New...