Re: failing to install 11.1R on VMWare

2018-04-07 Thread Ion-Mihai Tetcu 

[ combining 2 mails sent yesterday that didn't made it to the list ]

Lol, looking over the one that fails ... RAM is set at 4MB. Which I
think it might be the default on that cluster for some reason.
I'll test now with a sane amount of RAM. Apologies for the noise.

Yep, with 1GB it's OK.
Can't wait for the next week to kill the guy who configured that VM
before handling it over to me.
Sorry again for waisting your time. 


On Fri, 6 Apr 2018 23:44:17 +0300
Ion-Mihai Tetcu <ite...@freebsd.org> wrote:

> On Fri, 6 Apr 2018 11:30:26 -0700 (PDT)
> "Rodney W. Grimes" <freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> 
> > > On Fri, 6 Apr 2018 08:39:27 -0700 (PDT)
> > > "Rodney W. Grimes" <freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > > 
> > > > > On Thu, 5 Apr 2018 22:38:51 -0700 (PDT)
> > > > > "Rodney W. Grimes" <freebsd-...@pdx.rh.cn85.dnsmgr.net> wrote:
> > > > >   
> > > > > > > Hi,
> > > > > > > 
> > > > > > > 
> > > > > > > I'm trying to install FreeBSD on :
> > > > > > > VMWare ESXi, 6.0.0, 5050593
> > > > > > > 
> > > > > > > Guest OS: FreeBSD (64-bit)
> > > > > > > Compatibility: ESXi 6.0 and later (VM version 11)
> > > > > > > 
> > > > > > > For 11.1R I'm getting the boot menu, then:
> > > > > > > /boot/kernel/kernel text=014972f8
> > > > > > > elf64_loadimage: read failed
> > > > > > > can't load file: '/boot/kernel/kernel': input/output error
> > > > > > > ...
> > > > > > > (for 10.4R similar just with a different address).  
> 
>  [ .. ]
> 
> > > I relocated the VM on one of the 6.5.0 hosts (just the VM, not
> > > anything else) and got the same result trying to boot the 10.4R
> > > boot-only ISO). Would it make any diff if I create the VM from
> > > scratch on that host?
> > 
> > Um, moving .vmx files around between versions of vsphere has to be
> > done with a good deal of care, and given your having "issues" to
> > start with I would not add that complexity to this problem.
> > 
> > Create an new empty vm on 6.5.0, and use HW level 8, that is
> > portable accross 5.5 to 6.5.
> > 
> > Also try sticking with ONLY IDE disks and cdrom, that might
> > be causing an issue.   
> 
> OK I created a new machine, almost with defaults (changed the disk to
> IDE and independent-nonpersistent, put the CDROM on the same
> controller) on 6.5.0 with Compatibility set to ESXi 5.0 and later (VM
> version 8) and the installer booted OK, got to the welcome screen.
> I'll play more tomorrow since it's almost midnight and I have to be up
> in 4h. Many thanks for the help.
> 
> 
> Here's the vmx of it:
> >>>  
> .encoding = "UTF-8"
> config.version = "8"
> virtualHW.version = "8"
> nvram = "FREEBSD-test2.nvram"
> pciBridge0.present = "TRUE"
> svga.present = "TRUE"
> pciBridge4.present = "TRUE"
> pciBridge4.virtualDev = "pcieRootPort"
> pciBridge4.functions = "8"
> pciBridge5.present = "TRUE"
> pciBridge5.virtualDev = "pcieRootPort"
> pciBridge5.functions = "8"
> pciBridge6.present = "TRUE"
> pciBridge6.virtualDev = "pcieRootPort"
> pciBridge6.functions = "8"
> pciBridge7.present = "TRUE"
> pciBridge7.virtualDev = "pcieRootPort"
> pciBridge7.functions = "8"
> vmci0.present = "TRUE"
> hpet0.present = "TRUE"
> memSize = "1024"
> sched.cpu.units = "mhz"
> sched.cpu.affinity = "all"
> sched.cpu.latencySensitivity = "normal"
> sched.mem.affinity = "all"
> powerType.powerOff = "default"
> powerType.suspend = "default"
> powerType.reset = "default"
> scsi0.virtualDev = "lsilogic"
> scsi0.present = "TRUE"
> ide0:0.fileName = "FREEBSD-test2.vmdk"
> ide0:0.mode = "independent-nonpersistent"
> sched.ide0:0.shares = "normal"
> sched.ide0:0.throughputCap = "off"
> ide0:0.present = "TRUE"
> ethernet0.virtualDev = "e1000"
> ethernet0.networkName = "VM Network"
> ethernet0.addressType = "vpx"
> ethernet0.generatedAddress = "00:50:56:8d:99:50"
> ethernet0.present = "TRUE"
> ide0:1.deviceType = "cdrom-image

Re: failing to install 11.1R on VMWare

2018-04-06 Thread Ion-Mihai Tetcu 
On Fri, 6 Apr 2018 11:30:26 -0700 (PDT)
"Rodney W. Grimes"  wrote:

> > On Fri, 6 Apr 2018 08:39:27 -0700 (PDT)
> > "Rodney W. Grimes"  wrote:
> >   
> > > > On Thu, 5 Apr 2018 22:38:51 -0700 (PDT)
> > > > "Rodney W. Grimes"  wrote:
> > > > 
> > > > > > Hi,
> > > > > > 
> > > > > > 
> > > > > > I'm trying to install FreeBSD on :
> > > > > > VMWare ESXi, 6.0.0, 5050593
> > > > > > 
> > > > > > Guest OS: FreeBSD (64-bit)
> > > > > > Compatibility: ESXi 6.0 and later (VM version 11)
> > > > > > 
> > > > > > For 11.1R I'm getting the boot menu, then:
> > > > > > /boot/kernel/kernel text=014972f8
> > > > > > elf64_loadimage: read failed
> > > > > > can't load file: '/boot/kernel/kernel': input/output error
> > > > > > ...
> > > > > > (for 10.4R similar just with a different address).

 [ .. ]

> > I relocated the VM on one of the 6.5.0 hosts (just the VM, not
> > anything else) and got the same result trying to boot the 10.4R
> > boot-only ISO). Would it make any diff if I create the VM from
> > scratch on that host?  
> 
> Um, moving .vmx files around between versions of vsphere has to be
> done with a good deal of care, and given your having "issues" to
> start with I would not add that complexity to this problem.
> 
> Create an new empty vm on 6.5.0, and use HW level 8, that is portable
> accross 5.5 to 6.5.
> 
> Also try sticking with ONLY IDE disks and cdrom, that might
> be causing an issue. 

OK I created a new machine, almost with defaults (changed the disk to
IDE and independent-nonpersistent, put the CDROM on the same
controller) on 6.5.0 with Compatibility set to ESXi 5.0 and later (VM
version 8) and the installer booted OK, got to the welcome screen.
I'll play more tomorrow since it's almost midnight and I have to be up
in 4h. Many thanks for the help.


Here's the vmx of it:
>>>
.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "8"
nvram = "FREEBSD-test2.nvram"
pciBridge0.present = "TRUE"
svga.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
memSize = "1024"
sched.cpu.units = "mhz"
sched.cpu.affinity = "all"
sched.cpu.latencySensitivity = "normal"
sched.mem.affinity = "all"
powerType.powerOff = "default"
powerType.suspend = "default"
powerType.reset = "default"
scsi0.virtualDev = "lsilogic"
scsi0.present = "TRUE"
ide0:0.fileName = "FREEBSD-test2.vmdk"
ide0:0.mode = "independent-nonpersistent"
sched.ide0:0.shares = "normal"
sched.ide0:0.throughputCap = "off"
ide0:0.present = "TRUE"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "VM Network"
ethernet0.addressType = "vpx"
ethernet0.generatedAddress = "00:50:56:8d:99:50"
ethernet0.present = "TRUE"
ide0:1.deviceType = "cdrom-image"
ide0:1.fileName = 
"/vmfs/volumes/59258945-94251612-6fa4-3c4a92e1d6b8/ISO/FreeBSD-11.1-RELEASE-amd64-bootonly.iso"
ide0:1.present = "TRUE"
floppy0.startConnected = "FALSE"
floppy0.clientDevice = "TRUE"
floppy0.fileName = "vmware-null-remote-floppy"
displayName = "FREEBSD-test2"
guestOS = "freebsd-64"
toolScripts.afterPowerOn = "TRUE"
toolScripts.afterResume = "TRUE"
toolScripts.beforeSuspend = "TRUE"
toolScripts.beforePowerOff = "TRUE"
uuid.bios = "42 0d 6c 09 83 cf 81 5d-12 6d a8 de 4d 1a 3a d6"
vc.uuid = "50 0d 05 1e 9d 59 64 6a-c5 a8 b4 1b b4 f6 55 9a"
migrate.hostLog = "FREEBSD-test2-490e49c9.hlog"
sched.cpu.min = "0"
sched.cpu.shares = "normal"
sched.mem.min = "0"
sched.mem.minSize = "0"
sched.mem.shares = "normal"
numa.autosize.vcpu.maxPerVirtualNode = "1"
numa.autosize.cookie = "10001"
sched.swap.derivedName = 
"/vmfs/volumes/59258945-94251612-6fa4-3c4a92e1d6b8/FREEBSD-test2/FREEBSD-test2-6b4fc32b.vswp"
uuid.location = "56 4d af 84 7d ea 6b 51-e6 40 16 dd 81 07 1c 64"
ide0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "16"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
vmci0.id = "1293564630"
hostCPUID.0 = "000d756e65476c65746e49656e69"
hostCPUID.1 = "000306e40020080077bee3ffbfebfbff"
hostCPUID.8001 = "00012c100800"
guestCPUID.0 = "000d756e65476c65746e49656e69"
guestCPUID.1 = "000306e400010800969822030fabfbff"
guestCPUID.8001 = "000128100800"
userCPUID.0 = "000d756e65476c65746e49656e69"
userCPUID.1 = "000306e400010800969822030fabfbff"
userCPUID.8001 = "000128100800"
evcCompatibilityMode = "FALSE"
monitor.phys_bits_used = "40"
vmotion.checkpointFBSize = "4194304"

Re: failing to install 11.1R on VMWare

2018-04-06 Thread Ion-Mihai Tetcu 
On Fri, 6 Apr 2018 08:39:27 -0700 (PDT)
"Rodney W. Grimes"  wrote:

> > On Thu, 5 Apr 2018 22:38:51 -0700 (PDT)
> > "Rodney W. Grimes"  wrote:
> >   
> > > > Hi,
> > > > 
> > > > 
> > > > I'm trying to install FreeBSD on :
> > > > VMWare ESXi, 6.0.0, 5050593
> > > > 
> > > > Guest OS: FreeBSD (64-bit)
> > > > Compatibility: ESXi 6.0 and later (VM version 11)
> > > > 
> > > > For 11.1R I'm getting the boot menu, then:
> > > > /boot/kernel/kernel text=014972f8
> > > > elf64_loadimage: read failed
> > > > can't load file: '/boot/kernel/kernel': input/output error
> > > > ...
> > > > (for 10.4R similar just with a different address).
> > > > 
> > > > SCSI Adapatr for the VM is set to LSI Logic (but I've tried
> > > > with the other available options with the same result).
> > > > 
> > > > VMWare docs list both 10 and 11 as being compatible with this
> > > > version of ESXi.
> > > > Any pointers to get through this will be greatly appreciated, I
> > > > didn't found anything on the net, and I need a sane system to
> > > > play with when I'm getting tired of the ton of Linux distros
> > > > I'm forced to use.
> > > 
> > > Try setting the BIOS emulation to BIOS instead of UEFI.  
> > 
> > The WM is set:
> > Firmware: BIOS.
> > Boot Delay: 0ms
> > Force BIOS setup: No
> > Failed boot recovery: Do not automatically retry after virtual
> > machine fails to find a boot device EFI Secure Boot: Disabled  
> 
> Those all look good from my experience.
> 
> > > And what image are you trying to boot from?
> > > Are you trying to boot from a cd attached via vsphere client? or
> > > is it a file on the server?  
> > 
> > I've uploaded the ISOs on one of the data stores on the server,
> > didn't even tried from the client.  
> 
> Ok, so that is also the same procedure I am trying.
> 
> Now, which .ISO is it?  Maybe you have a broken snapshots.  Lots of
> bootcode work has been going on in -current.  Can you try the 11.1
> release ISO either i386 or amd64?
> 
> I know that installs as I have done that many times.

FreeBSD-11.1-RELEASE-amd64-dvd1.iso
FreeBSD-11.1-RELEASE-amd64-bootonly.iso
Tried this one after 11.1 failed FreeBSD-10.4-RELEASE-amd64-bootonly.iso

I just downloaded the FreeBSD-11.1-RELEASE-amd64-bootonly.iso from the
data store and checked the sha256 against the one on the ftp site and
it's OK, so except if vshpere somehow corrupts files on upload and
fixes them on download I think the image is OK.
 
> > > I usually use a .ISO when working with ESXi and FreeBSD as a
> > > guest.  
> > 
> > I'll try with the vmdk image of the release now.  
> 
> I have NOT ever tried that, so have no data there.
> 
> > > I run these guest on ESXi 5.5 and ESXi 6.5, I do not have any
> > > 6.0.0.  
> > 
> > Hm, I guess I could try on 6.5 as an other cluster with has hosts
> > running VMware ESXi, 6.5.0, 4564106  
> 
> It should just work, I have played with ESXi 6.0.0 at one
> time or another and would have a good recollection if I had issues
> booting any FreeBSD distributions on it.  At present I do not have
> any 6.0.0 running, though I could fix that in a matter of minutes.
 
I relocated the VM on one of the 6.5.0 hosts (just the VM, not anything
else) and got the same result trying to boot the 10.4R boot-only ISO).
Would it make any diff if I create the VM from scratch on that host?


Tnx,

-- 
IOnut Tetcu

 


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: failing to install 11.1R on VMWare

2018-04-06 Thread Ion-Mihai Tetcu 
On Thu, 5 Apr 2018 22:38:51 -0700 (PDT)
"Rodney W. Grimes"  wrote:

> > Hi,
> > 
> > 
> > I'm trying to install FreeBSD on :
> > VMWare ESXi, 6.0.0, 5050593
> > 
> > Guest OS: FreeBSD (64-bit)
> > Compatibility: ESXi 6.0 and later (VM version 11)
> > 
> > For 11.1R I'm getting the boot menu, then:
> > /boot/kernel/kernel text=014972f8
> > elf64_loadimage: read failed
> > can't load file: '/boot/kernel/kernel': input/output error
> > ...
> > (for 10.4R similar just with a different address).
> > 
> > SCSI Adapatr for the VM is set to LSI Logic (but I've tried with the
> > other available options with the same result).
> > 
> > VMWare docs list both 10 and 11 as being compatible with this
> > version of ESXi.
> > Any pointers to get through this will be greatly appreciated, I
> > didn't found anything on the net, and I need a sane system to play
> > with when I'm getting tired of the ton of Linux distros I'm forced
> > to use.  
> 
> Try setting the BIOS emulation to BIOS instead of UEFI.

The WM is set:
Firmware: BIOS.
Boot Delay: 0ms
Force BIOS setup: No
Failed boot recovery: Do not automatically retry after virtual machine fails to 
find a boot device
EFI Secure Boot: Disabled

> And what image are you trying to boot from?
> Are you trying to boot from a cd attached via vsphere client? or
> is it a file on the server?

I've uploaded the ISOs on one of the data stores on the server, didn't
even tried from the client.

> I usually use a .ISO when working with ESXi and FreeBSD as a guest.

I'll try with the vmdk image of the release now.

> I run these guest on ESXi 5.5 and ESXi 6.5, I do not have any 6.0.0.

Hm, I guess I could try on 6.5 as an other cluster with has hosts
running VMware ESXi, 6.5.0, 4564106

-- 
IOnut




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

failing to install 11.1R on VMWare

2018-04-05 Thread Ion-Mihai Tetcu 
Hi,


I'm trying to install FreeBSD on :
VMWare ESXi, 6.0.0, 5050593

Guest OS: FreeBSD (64-bit)
Compatibility: ESXi 6.0 and later (VM version 11)

For 11.1R I'm getting the boot menu, then:
/boot/kernel/kernel text=014972f8
elf64_loadimage: read failed
can't load file: '/boot/kernel/kernel': input/output error
...
(for 10.4R similar just with a different address).

SCSI Adapatr for the VM is set to LSI Logic (but I've tried with the
other available options with the same result).

VMWare docs list both 10 and 11 as being compatible with this version
of ESXi.
Any pointers to get through this will be greatly appreciated, I didn't
found anything on the net, and I need a sane system to play with when
I'm getting tired of the ton of Linux distros I'm forced to use.


Tnx,

-- 
IOnut Tetcu




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: [CFT] pkgng alpha2

2011-12-14 Thread Ion-Mihai Tetcu 
On Tue, 13 Dec 2011 19:56:05 +0200
Andriy Gapon a...@freebsd.org wrote:

 on 13/12/2011 19:22 Julien Laffaye said the following:
  On 12/13/2011 06:16 PM, Andriy Gapon wrote:
  on 30/11/2011 22:32 Julien Laffaye said the following:
  [1] : https://github.com/pkgng/pkgng/issues
  [2] : https://github.com/pkgng/pkgng
  [3] : http://wiki.freebsd.org/pkgng
  [4] : http://people.freebsd.org/~bapt/pkgng-bsdcan2011.pdf
  [5] :
  http://wiki.freebsd.org/201110DevSummit/Ports?action=AttachFiledo=gettarget=pkgng-devsummit.pdf
 
 
  [6] :
  http://wiki.freebsd.org/201110DevSummit?action=AttachFiledo=gettarget=pkgng-devsummit-track.pdf
 
  Couple of questions/suggestions:
 
  1. Do you plan to have a pkgng port to issue the preview releases
  pkgng? Current pkgng installation/bootstrap procedure is really
  easy, but the port would be even more convenient for prospective
  testers.
  Yes, this is planned. The ports will bootstrap pkgng.
 
 Great!

The current idea is to have everything in ports so that we don't depend
on the base OS for any kind of changes; we'll only have a bootstrap in
base. One more step forward to decoupling ports from src releases.

  2. Is there a public pre-built package repository with
  pkgng-format packages that could be used for testing and getting a
  taste of a packages-only pkgng-managed system?
  Unfortunately, no.
  I think I now have the resources to do that  for the next CFT. But
  it will only be 9.0 amd64 I am afraid.
  We cant build packages for the entire matrix.
 
 I understand.  Those would take an immense amount of compilation time
 and storage space.

Storage and especially storage / propagation to mirrors are the biggest
problems.
After pkgNG goes in, we plan to switch HEAD to it and provide only
pkgNG packages for it; then probably the same for 9-STABLE and further
9 releases, but we'll probably need to provide current style of
pacakges during 9.x life time :(

-- 
IOnut - Un^d^dregistered ;) FreeBSD user
  Intellectual Property is   nowhere near as valuable   as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B


signature.asc
Description: PGP signature

Re: [UPDATE] Re: Update on ports on 10.0

2011-10-28 Thread Ion-Mihai Tetcu 
On Thu, 27 Oct 2011 15:42:00 +0400
Ruslan Mahmatkhanov cvs-...@yandex.ru wrote:

 Erwin Lansing wrote on 27.10.2011 14:21:
  On Fri, Oct 21, 2011 at 12:44:34PM +0300, Ion-Mihai Tetcu wrote:
  What, on the other hand, makes sense is to have the fix that
  should include:
  a) a KNOB (WITH_FBSD10_FIX or similar),
  b) that only is run from bsd.port.mk when OSVERSION100
  c) runs the latest version of the above patch.
  The KNOB's existence allow us to turn on the fix only for broken
  ports, and easily know what these broken ports are -- so we can
  poke maintainers from time to time about upstream fixes, ...
 
 
  Erwin is currently running a build on i386-10 with this and the
  following patches:
  - bsd.port.mk patch from beat (based on ed@, jilles@ and stas@
  patches)
  - python patch from beat
  - python patch from linimon
  - WITH_FBSD10_FIX in:
   - textproc/expat2
   - devel/pcre
   - devel/libtool
   - audio/libogg
  Results by Monday.
 
 
  These patches have now been committed to the tree, notably with
  lang/python27 missing in the above list but was included as well.
  There have been some proposals already and we can now incrementally
  improve the workaround and, more importantly, start fixing
  individual ports.  Please note that the patch tries to balance
  between being a general enough fix to make it easy to get a working
  system running while not just swiping the whole issue under the rug
  and forget about it until the next release cycle.  Make sure to
  send any fixes upstream to the hack can be removed from the ports
  again.
 
  Thanks for all your patience and thanks for all those involved,
  especially beat who sent many patches and improvements.
 
  Erwin
 
 About devel/libtool fix. Why to not update it to 2.4.2 where this was 
 fixed upstream? I mean http://bugs.freebsd.org/162012

We probably need an other set of -exps for that, given how many ports
depends on it, and I don't think we have the time for that before the
release.

-- 
IOnut - Un^d^dregistered ;) FreeBSD user
  Intellectual Property is   nowhere near as valuable   as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org

[UPDATE] Re: Update on ports on 10.0

2011-10-17 Thread Ion-Mihai Tetcu 
On Tue, 11 Oct 2011 08:36:03 +0200
Erwin Lansing er...@freebsd.org wrote:

 Since the release has been pushed back some more since the last mail,
 we do have some time to test a possible fix for the issues we're
 seeing with libtool on FreeBSD 10.0.  However, fixing libtool is only
 part of the problem as hundreds, if not thousands, of ports roll
 their own detection and need to be fixed individually.  We are
 currently running a fixed libtool (ports/161404) to assess how many
 ports are fixed by this patch and how many need to be patches
 manually before deciding how to move forward.  Other options include
 the big find/grep/awk solution that has been posted several times and
 fiddling with uname to go to FreeBSD 9.99 for a while, while ports
 can be fixed.
 
 Hopefully, we can move forward in a day or two, but needless to say
 this needs a lot of testing both on 10.0 and earlier releases so we
 are sure we don't break backwards compatability, especially on 9.0
 that is soon to be released.  For those that cannot wait a few days,
 several patches have been proposed on the lists, of which dougb's
 seems most complete, so I recommend applying one of those locally.
 Please note that these are not tested widely and may break when the
 final fix is committed.
 
 To conclude with some fun facts, only 232 ports break on HEAD
 currently.  Unfortunately, some of these are pretty high profile and
 prevent almost 19.000 other ports from building, leaving only slighty
 more than 3000 ports to build successfully.


Here's a little status update:
We iterated through a few -exp runs (basically for ports/161404 --
committed and ports/161431 -- skv@ any problem with it?). With those two
we can build around 7k packages. The majority of the rest can't be built
because of a few high profile ports that don't package: expat (6581),
curl (975), jpeg(5057), lcms(1080), libiconv(11180), libltdl(1187),
libogg(1947), pcre(5737), python27(5935).

http://pointyhat.freebsd.org/errorlogs/i386-10-latest/

What we'd like to do next is see how many ports we can package after
individually fixing those above. This will require a few other -exps
since undoubtedly we'll find other highly-depended-on ports broken that
weren't tried because of the blockers above.

Depending on this number and how long the whole process will take, we
can decide what solution to adopt. If possible we'd like to avoid the
big hammer of an uname fiddle or find/grep/sed/... (which most probably
won't work for all ports anyway, irrespective of how smart it will be).
If we need to adopt one of these hacks, it will be via some conditional
KNOB in each port Makefile, in order to have an easy way to know which
ports are fixed and which not, and an easy way to turn it off for test
builds without it in the future. Basically we do not want to shove the
dirt under the carpet, were it will rot for years.

YOU can help by sending portmgr@ patches for above ports (or any other
you know is broken) for the next -exp run.
And PLEASE, pretty please once you have a patch that fixes this problem
submit it upstream and bug upstream about it. (committers: please check
this is the case when committing a patch from a PR).

Thanks!


-- 
IOnut


___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org